Request
When launching a claude command, automatically forward the CodeShellManager session name as Claude's --name argument so the conversation is named the same in Claude's own session list.
Why
Today the session name only lives inside CodeShellManager. If you later open the same conversation outside the app (e.g. via claude --resume from a normal shell, or browse ~/.claude/projects/), the conversation is anonymous and you can't tell which CodeShellManager tab it came from.
Suggested behaviour
- For sessions where
ClaudeSessionService.IsClaudeCommand(Command) is true and Args doesn't already contain --name, append --name "<ShellSession.Name>" to the launch args.
- Renaming the session in CodeShellManager could either: (a) just affect future launches, or (b) push the new name to Claude on next restart. (a) is simplest; (b) is nicer.
Open question
Verify that Claude actually accepts --name as a launch flag and that it survives --resume. If not, we might need a different mechanism (env var, pre-launch hook, etc.).
Request
When launching a
claudecommand, automatically forward the CodeShellManager session name as Claude's--nameargument so the conversation is named the same in Claude's own session list.Why
Today the session name only lives inside CodeShellManager. If you later open the same conversation outside the app (e.g. via
claude --resumefrom a normal shell, or browse~/.claude/projects/), the conversation is anonymous and you can't tell which CodeShellManager tab it came from.Suggested behaviour
ClaudeSessionService.IsClaudeCommand(Command)is true andArgsdoesn't already contain--name, append--name "<ShellSession.Name>"to the launch args.Open question
Verify that Claude actually accepts
--nameas a launch flag and that it survives--resume. If not, we might need a different mechanism (env var, pre-launch hook, etc.).