feat(connector): resume a prior claude-code session into the mesh#24
Closed
caffeinum wants to merge 1 commit into
Closed
feat(connector): resume a prior claude-code session into the mesh#24caffeinum wants to merge 1 commit into
caffeinum wants to merge 1 commit into
Conversation
Add an optional `resume` to the connector LaunchOpts so a spawn/start can reattach a prior claude-code conversation instead of always starting fresh. - core: `LaunchOpts.resume?` (connector-specific session id) - claude-code connector: when set, push `--resume <id> --fork-session` (fork so the original session id isn't hijacked — we adopt its context, not its identity); all existing args (dev-channels, mcp config, persona, model) are preserved - manager opStart threads `args.resume` into buildLaunch - `cotal start` and `cotal spawn` gain a `--resume <id>` flag - codex/opencode ignore `resume` (claude-specific) Closes Cotal-AI#23 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
caffeinum
marked this pull request as ready for review
June 15, 2026 19:06
Collaborator
|
Superseded by #30 (resume on the guided-setup stack: composes with the --strict-mcp isolation, skips the greeting on resume, fail-closed codex/opencode guard, + docs). Thanks @caffeinum — same shape, built on the setup stack. Closing in favor of that. |
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an optional
resumeto the connectorLaunchOptsso acotal spawn/startcan reattach a prior claude-code conversation instead of always starting a fresh session.When set, the claude-code connector pushes
--resume <id> --fork-sessioninto the launch args (fork so the original session id isn't hijacked — we adopt its context, not its identity). All existing args (dev-channels, MCP config, persona, model) are preserved, so the resumed process still joins the mesh normally.Why
Today every spawn is a cold session — an operator doing real work in a claude session can't pull that context into the mesh. This is the minimal change to allow it.
claude --resume,--fork-session, and--strict-mcp-configcompose cleanly (verified againstclaude --help).Closes #23.
Changes
core:LaunchOpts.resume?(connector-specific session id)connector-claude-code: emit--resume <id> --fork-sessionwhen setmanager:opStartthreadsargs.resumeintobuildLaunch;--resumeflag onstartcli:--resume <id>flag onspawnresume(claude-specific no-op)Test
Build + typecheck clean (
pnpm -r build,pnpm -r typecheck).🤖 Generated with Claude Code