[BUG] /ide None selection and "ide": false setting do not persist across sessions — VS Code auto-reconnects every startup
Status Open
Reported on v2.1.268
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 0 comments · opened Sep 11, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
The /ide "None" selection does not persist across sessions. Every time a new Claude Code
session starts, it auto-connects to VS Code, ignoring the previous choice.
What Should Happen?
The "None" selection made via /ide should persist across sessions until manually changed again.
Error Messages/Logs
N/A — no error message, Claude Code silently auto-connects to VS Code on every startup.
Steps to Reproduce
- Run /ide → select "None" → confirm
- Close VS Code
- Reopen VS Code and start a new Claude Code session
- Claude Code auto-connects to VS Code again
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.268 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
Workarounds tried (all failed):
- autoConnectIde: false in ~/.claude/settings.json → no effect
- "ide": false in .claude/settings.local.json → no effect
Related: #15567 and #1703
(closed as not planned, but issue persists and all suggested workarounds fail)