You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Listen to and steer running workers. Workers now run with --input-format stream-json, and the wrapper keeps their stdin open (launcher/steer.py).
Every INBOX_POLL_S (5 s), and with each heartbeat answer, the wrapper writes the worker's new messages into its stdin as one framed user line with priority: "next". The worker reads it at its next step instead of after its next tool batch. The wrapper then acks the messages with the hooks' key, so the hooks do not show them again.
A lead message wavecoord:{"action": ...} is a steer action: interrupt (a control_requestinterrupt, then the note as the next turn), model (set_model) or stop. From any other sender it stays plain text.
After a result, new messages get one more turn, at most 3 per run. Otherwise the wrapper closes stdin and the run ends.
New lead commands: wavecoord hint <task> <text> and wavecoord steer <task> interrupt|model <m>|stop [--note].
Progress and stuck notices. The wrapper keeps a digest of the stream: turns, tokens, the last tool calls and text, edited files, failing commands, and the session state (CLAUDE_CODE_EMIT_SESSION_STATE_EVENTS=1). It posts a progress notice every PROGRESS_S (300 s), with the context use from a get_context_usage control request. It posts a stuck notice, once per reason, for:
loop: the same tool call 3 times in a row
failing: the same command failed 3 times
waiting: requires_action
budget: 75% of turns or tokens used
quiet: no output for QUIET_S
Inbox relay for sessions that wavecoord did not launch. A worker session that a person started (WAVECOORD_TASK set, no launcher) gets its messages through its Claude Code inbox socket (CLAUDE_CODE_MESSAGING_SOCKET).
SessionStart starts wavecoord inbox-relay, which pushes the framed messages with the session's token and acks them only after the socket took them. The hooks skip the pushed ids.
The socket's line format is not documented by Claude Code. It was taken from Claude Code 2.1.302 (hooks.md, "Claude Code facts"). A failed push leaves the message to the hooks.
steerer subagent and auto_steer./wavecoord:triage handles progress and stuck lines. With auto_steer: "draft" (the default), the steerer drafts a hint and the user decides. With "hints", triage sends plain-text hints itself, at most one per attempt every 10 minutes. Interrupts, model switches and stops always need the user. auto_steer is lead config: a task PR that changes it fails the merge check (config_change).
New constants INBOX_POLL_S, PROGRESS_S, QUIET_S (contract section 5).
scripts/smoke-live.py: a live check with a real claude (hint, steer, listen and relay; this host and --ssh hosts). A manual release check, never in CI (CONTRIBUTING.md).
Fixed
wavecoord tokens provision --out into a new directory failed (the quick start's ~/.wavecoord/hosts/local.token on a fresh machine), after it had already added the token to the tokens file. It now creates the directory (mode 700) first.
A worker launched from inside a Claude session inherited that session's inbox. The launcher now also removes CLAUDE_CODE_MESSAGING_SOCKET and CLAUDE_CODE_MESSAGING_TOKEN from the worker's environment.
Also in this release: 0.1.5 (not released separately)
Fixed
--continue resumed a session that does not exist. Each run of an attempt got a fresh session id in task.json. A --continue run passes only --resume <id>, and Claude Code keeps writing into the transcript of the resumed id (only --fork-session makes a new one), so the fresh id of a resumed run never had a transcript. The next --continue resumed that id: claude printed No conversation found with session ID: <id>, the result was error_during_execution with 0 turns, and every later --continue of the attempt failed the same way (seen with Claude Code 2.1.302 on Linux, after a --continue --spec run). Now:
The launcher resumes the attempt's lineage: the session whose transcript the last run wrote (transcript_session), then the first run's id, then the ids of the earlier runs in prev-*/, oldest first. So an attempt left by 0.1.4 resumes its first run's session again.
The wrapper checks that the transcript file exists ($CLAUDE_CONFIG_DIR or ~/.claude, projects/<encoded worktree path>/<id>.jsonl, with the provider's environment) before it resumes. It never passes --session-id together with --resume.
When no transcript exists, or claude says No conversation found, the wrapper starts a fresh session in the same worktree, one time. The prompt is a short note with the branch's commits since the base, the first run's full prompt and the continue prompt. session_fallback in the result, status.json and task.json records the reason. The next --continue resumes the fresh session.
A --continue run with --spec keeps the same lineage. The result, the report request and status.json give the session id of the transcript.
The fake claude keeps transcripts in a fake ~/.claude/projects layout (FAKE_CLAUDE_TRANSCRIPTS=1, on in the launcher and e2e tests), refuses --session-id with --resume, and fails a --resume of an unknown id as Claude Code does. New tests: two --continue runs (the second with the spec prompt) resume the first id, recovery of a 0.1.4 attempt dir, the fallback without a transcript, and the fallback after No conversation found.
dispatch --wave checked wip_cap against the same count for each task. The dry run printed wip 3/6 for all four tasks of a wave, because decide counted only the attempts in the snapshot. Now each task that the wave placed counts for the next one (wip 3/6, 4/6, ...), in a dry run too, and a wave stops at the cap. New assertions in test_wip_cap_and_wave.