coder / coder/claudecode.nvim

[QUESTION] Dynamically Switch Terminal.Provider ??

Offen
#158 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Lua
Sterne
3.1k
Forks
216
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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?

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
lua, neovim
Bereich
devtools
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.