Agents and handoff

Current status: runnable Codex/Claude Agent Cells are not started end to end; the current image is an offline shell, not an agent runtime.

Adapter contract

Adapters support start, structured input, output streaming, interrupt, exit, declared model/tool metadata, optional provider session references, and checkpoint requests. Versions are pinned; capability matrices, health checks, and conformance fixtures make support inspectable. Raw provider signals retain source attribution. Unsupported semantics remain unavailable rather than being normalized into false parity.

Cross-agent handoff

A handoff includes task, base, patch, decisions, completed/failed work, checks, capabilities, evidence links, explicit gaps, and next action. Same-provider native resume is an optional optimization; a cross-provider child Run gets the structured Work Journal and checkpoint. Cella retains the governing policy hierarchy, identity, workspace, and consequence control while the agent changes. Authority is re-evaluated for the new actor, adapter/model, operation, and generation, and eligible requests need fresh generation-bound grants. Handoff does not imply identical decisions or transfer old capabilities into the new Run.

Example: Codex investigates a bug; Claude Code continues from its declared checkpoint. No new host authority or claim of transferred chain-of-thought is introduced.

See agent adapters and handoff flow.