Summary
launch_session truncates a multi-word prompt to its first whitespace-delimited token.
Repro
Call launch_session({ project, prompt }) with a long / multi-line prompt, e.g. one beginning:
"Help me build a conference talk. This is for a 3-part symposium..."
The newly launched session receives only Help — the first token. Everything after the first space/newline is dropped.
Expected
The entire prompt string should reach the new session verbatim, regardless of spaces, newlines, or quotes.
Likely cause
The prompt is being passed to the Claude Code CLI as an unquoted shell argument, so the shell word-splits it and only argv token 1 survives. Newlines and embedded quotes would make the breakage worse.
Fix direction
Quote/escape the prompt when building the launch command, or pass it via stdin / a temp file / env var rather than as a bare CLI arg.
Workaround (current)
Write the context to a file in the target project and pass a short, single-token-safe prompt pointing at it (e.g. Read TALK_BRIEF.md in the project root and follow it.).
Impact
Context handoffs from the control plane silently fail — the seeded session starts with almost no context, and the operator only finds out by manually inspecting the new session.
Related: #9 (launch verification + early interjection would have surfaced this immediately).
Summary
launch_sessiontruncates a multi-wordpromptto its first whitespace-delimited token.Repro
Call
launch_session({ project, prompt })with a long / multi-line prompt, e.g. one beginning:The newly launched session receives only
Help— the first token. Everything after the first space/newline is dropped.Expected
The entire
promptstring should reach the new session verbatim, regardless of spaces, newlines, or quotes.Likely cause
The
promptis being passed to the Claude Code CLI as an unquoted shell argument, so the shell word-splits it and onlyargvtoken 1 survives. Newlines and embedded quotes would make the breakage worse.Fix direction
Quote/escape the prompt when building the launch command, or pass it via stdin / a temp file / env var rather than as a bare CLI arg.
Workaround (current)
Write the context to a file in the target project and pass a short, single-token-safe prompt pointing at it (e.g.
Read TALK_BRIEF.md in the project root and follow it.).Impact
Context handoffs from the control plane silently fail — the seeded session starts with almost no context, and the operator only finds out by manually inspecting the new session.
Related: #9 (launch verification + early interjection would have surfaced this immediately).