CyberCoveLLC/Triple-C

0 Fork 0

Resume a session as a Claude tab so Shift+Enter inserts a newline #67

Merged

jknapp merged 1 commits from fix/resume-opens-claude-session into main

2026-10-17 02:22:14 +00:00

Author	SHA1	Message	Date
shadowdaoandClaude Opus 5.5	d00afe7666	fix: resume a session as a Claude tab, not a bash tab Secret Scan / scan (push) Successful in 6s Details Build App (Preview) / compute-version (pull_request) Successful in 4s Details Secret Scan / scan (pull_request) Successful in 5s Details Build App (Preview) / create-release (pull_request) Successful in 2s Details Build App (Preview) / build-macos (pull_request) Successful in 3m26s Details Build App (Preview) / test (pull_request) Successful in 6m10s Details Build App (Preview) / build-windows (pull_request) Successful in 7m37s Details Build App (Preview) / build-linux (pull_request) Successful in 8m10s Details Build App (Preview) / prune-previews (pull_request) Successful in 2s Details [Resume] opened a "bash" session and typed `claude --resume <id>` into it. The tab's session type is what the Shift+Enter binding keys off, so in a resumed conversation Shift+Enter submitted the prompt instead of inserting a newline. The status-bar hint and Send to agent missed those tabs too. open_terminal_session now takes an optional resume_session_id and launches `claude --resume <id>` through the normal Claude path (update prelude, permission flags, Bedrock SSO check). `-n` is dropped when resuming so the tab label ("resume" when the conversation has no name) does not rename the conversation. resume_session_command and its capability grant are removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-16 17:48:32 -07:00