Cal keeps the context, continuity, and decision loop. Codex works as a focused executor in its own thread. Questions return through the same visible Strand in the Cal UI for parallel sessions, then the work resumes where it stopped.
Cal owns the brain: context, memory, orchestration, and continuity.Codex owns the run: focused execution inside a swappable worker thread.
One task, one visible Strand, one continuous executor thread
1
User
Gives Cal a task in natural language.
2
Cal orchestrates
Prepares the relevant context
Writes the task note
Delegates the run
3
Codex Strand
The visible Cal UI for the delegated task and its complete timeline.
WorkingPending feedbackReady
Background execution loopThe Strand stays visible while execution, analysis, and continuation happen behind it.
4
Codex executes
Works in its own durable thread.
Reads, builds, tests, and reports
Can be resumed after feedback
5
Cal analyzes
Reads the full Codex response, not a truncated preview.
Open questions?
No open questions
Task completed
Ready · Summary posted
Cal closes the loop and updates the visible Strand.
Open questions remain
Pending feedback
Attention · Needs input
Cal drafts answers
Cal notifies the user
Feedback policy
/ask-meDefault. Wait for user approval.
/dont-ask-meAnswer autonomously, capped at 3 cycles.
Summary to User
The same Strand holds the task, feedback exchange, resumed work, and final result.
The loop is the product
Delegation is not complete when another model returns text. It is complete when questions are recognized, answers are prepared, attention is requested only when needed, and execution can continue in the same thread.
The executor is swappable
Codex is the executor shown here. Cal remains the brain and orchestrator, so another capable worker can occupy the same boundary without changing who owns context and continuity.