Context
The unified spawn plan (#8802e3a8) migrates all spawn patterns to use breathe.WriteSyntheticSession() to write a synthetic JSONL session, then claude --resume <id> -- "<trigger>" to launch.
BuildResumeCommand now has a Codex case (codex resume --yolo <sessionID> '<trigger>'), but Codex may not support resuming from Claude Code's JSONL session format. The JSONL files are CC-specific (~/.claude/projects/<dir>/sessions/<id>.jsonl).
What needs investigation
- Does
codex resume <sessionID> read CC's JSONL format, or does it have its own session storage?
- If Codex has its own format, does
WriteSyntheticSession need a Codex-specific writer?
- If Codex can't resume from JSONL at all, the Codex spawn path needs to stay on the old pattern (or a Codex-native equivalent).
Current state
BuildResumeCommand has the Codex case ready (outputs codex resume --yolo <sessionID> '<trigger>')- Worker spawn migration (Task 3 of the unified spawn plan) will use this for Codex-tagged tasks
- If Codex doesn't support JSONL resume, Codex workers will fail at runtime
Scope
This is not blocking the unified spawn plan — Claude Code is the primary runtime and should be migrated first. This issue tracks making Codex work with the new pattern (or keeping a fallback).
Context
The unified spawn plan (#8802e3a8) migrates all spawn patterns to use
breathe.WriteSyntheticSession()to write a synthetic JSONL session, thenclaude --resume <id> -- "<trigger>"to launch.BuildResumeCommandnow has a Codex case (codex resume --yolo <sessionID> '<trigger>'), but Codex may not support resuming from Claude Code's JSONL session format. The JSONL files are CC-specific (~/.claude/projects/<dir>/sessions/<id>.jsonl).What needs investigation
codex resume <sessionID>read CC's JSONL format, or does it have its own session storage?WriteSyntheticSessionneed a Codex-specific writer?Current state
BuildResumeCommandhas the Codex case ready (outputscodex resume --yolo <sessionID> '<trigger>')Scope
This is not blocking the unified spawn plan — Claude Code is the primary runtime and should be migrated first. This issue tracks making Codex work with the new pattern (or keeping a fallback).