Multi-account: VS Code (claude-vscode) sessions can't be pinned to a Claude account

[grimmerk]

Part of multi-account support (docs/multi-account-support-design.md). CodeV now runs multiple Claude accounts by launching the official claude CLI with a per-account CLAUDE_CONFIG_DIR; the Sessions tab aggregates sessions across accounts, badges non-default accounts, and resumes each under its own account.

Limitation

VS Code (claude-vscode) sessions can't be account-switched from CodeV. They're launched/switched via the URI handler (vscode://anthropic.claude-code/open), which offers no way to set CLAUDE_CONFIG_DIR or choose an account — a VS Code session's account is whatever the VS Code Claude Code extension is signed into.

Consequently, for VS Code sessions CodeV cannot:

• inject CLAUDE_CONFIG_DIR at resume (account-aware resume)
• reliably tag them with an account in the Sessions list

This is a pre-existing constraint (VS Code multi-account was never supported), surfaced by the multi-account feature.

Possible directions (future)

• Investigate whether the VS Code extension honors CLAUDE_CONFIG_DIR from the VS Code process env, and whether CodeV can influence that env when opening a workspace.
• Or provide a manual account hint / picker for VS Code sessions.
• Or document it as an explicit limitation.

Priority

Low / future — CLI-terminal sessions (iTerm2/Ghostty/Terminal/cmux) are fully account-aware; VS Code is the gap.

🤖 On behalf of @grimmerk — generated with Claude Code