Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[QUESTION] Dynamically Switch Terminal.Provider ??

Open
  • Is something wrong?
#158 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua, neovim
Domain
devtools

Research direction

Start by reproducing the two Lua commands in a small project and inspect how claudecode.nvim reads and stores terminal.provider. Trace the terminal provider startup path to determine whether it uses only the initial value. Done means switching between "auto" and "none" at runtime changes subsequent behavior without restarting Neovim.

Written by the indexing model from the issue text.

Description

Issue #154 discussed a way to run claudecode.nvim with Claude Code in an external session, using 'provider = "none"' and then launch claude using claude --ide. This is great for working on monolith projects.

For small projects, I'd like the ability to dynamically toggle between 'provider = "none"' and 'provider = "auto". I've tried some manual tests, but find claudecode.nvim persists the 'startup value', and doesn't seem to use the dynamically set value. Here's the commands used in my manual test:

# print setting
:lua print(vim.inspect(require("claudecode").state.config.terminal.provider))
# toggle setting
:lua require("claudecode").state.config.terminal.provider = require("claudecode").state.config.terminal.provider == "auto"  and "none" or "auto"

Is there a way to toggle the provider dynamically?

Dominant language
Lua
Stars
3.1k
Forks
219
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/claudecode.nvim

All issues in coder/claudecode.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.