Manual context handoff between AI clients
The ritual of retelling one AI client what another already understood becomes optional when context moves into a shared layer.
Disappearing action
- Human ritual: Copy architecture notes, task state, constraints, and decisions between Claude, Codex, Cursor, chat, and docs.
- Old cost: Repeated context switching, stale memory, contradictory assumptions, and lost provenance.
- Replacement pattern: Governed shared context layer that multiple AI clients can read with explicit provenance and access rules.
- Where the old interface still wins: Manual handoff is still safer when context contains sensitive data, unclear ownership, or unreviewed agent memories.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | unabyss.comsource | primary receipt | source_urls |
This interface is not dead. It is no longer mandatory.
The old ritual survives because it is inspectable: a human sees exactly what was copied. The replacement needs the same property, otherwise shared context simply becomes a larger hidden prompt.