Expected Behavior
I should be able to say “read this file” while the file is open in VS Code, without needing to use @path-to-file to manually add it as context.
Actual Behavior
The CLI has no awareness of the currently opened file, and some tool calls through the /ide integration show failure or error messages:
DIAGNOSTICS [{"filePaths":[]}]
└ Error: Could not connect to IDE extension. Make sure the Command Code extension is
installed and active.
Command Code Version
v0.25.6
Operating System
Windows
Terminal/IDE
vscode
Shell
git bash > zsh
Additional context
Before v0.25.2, running /ide in my environment would open 2 VS Code instances. Opening those VS Code instances had no effect on the integration between the command-code CLI and VS Code. Reloading the developer window also did not help.
As of v0.25.6, it no longer opens any new VS Code instances. However, the IDE integration still fails.
Expected Behavior
I should be able to say “read this file” while the file is open in VS Code, without needing to use
@path-to-fileto manually add it as context.Actual Behavior
The CLI has no awareness of the currently opened file, and some tool calls through the
/ideintegration show failure or error messages:Command Code Version
v0.25.6
Operating System
Windows
Terminal/IDE
vscode
Shell
git bash > zsh
Additional context
Before v0.25.2, running
/idein my environment would open 2 VS Code instances. Opening those VS Code instances had no effect on the integration between the command-code CLI and VS Code. Reloading the developer window also did not help.As of v0.25.6, it no longer opens any new VS Code instances. However, the IDE integration still fails.