Hand off AI-assisted work without rebuilding the context
When a coding-agent session ends, what it learned goes with it. The next agent, machine or person starts from the repo and a ticket and works out the same things again. Ophiuchus moves the useful part across that boundary instead.
Early Alpha, v0.0.0. A command-line tool, invite-only, and free. Whether it actually helps is still being measured.
Across tools
A handoff from Claude Code to Codex today. Each tool keeps its session state in its own shape, so context stops at the tool boundary. Ophiuchus compiles it into one structured Context Capsule that either side can read.
Across machines
A capsule goes over a relay that stores bytes under a capability token, expires them, and hands them back. It is deliberately dumb: no summarizing, no embeddings, no scoring. Your work does not have to stay on the laptop that started it.
Less rediscovery
A capsule carries the hypotheses already ruled out, the evidence actually observed, and the requested next action. Those are the parts a handoff note usually drops, and they are what stops the recipient walking back into a dead end.
Three capabilities under validation
These are directions Ophiuchus might go. None is built. Each represents a hypothesis about what makes a handoff more valuable. Clicking a card tells us whether the hypothesis matters to you.
Team Context
Publish useful engineering context once — the goal, the constraints, what was already ruled out — and let team members or agents discover it when the same problem comes up again.
Hypothesis: Where is the knowledge? Once a capsule has been useful in one session, would a team benefit from being able to discover it without being handed the token directly?
Smart Routing
When a handoff crosses a service or ownership boundary, identify who owns the affected code before the capsule is sent — so it arrives with the right person, not whoever the sender guessed.
Hypothesis: Who should receive this? Could Ophiuchus help determine the right person or team to receive a Context Capsule, rather than requiring the sender to already know?
Private Deployment
Keep engineering context inside a customer-controlled environment. A self-hosted relay, a deployment where capsules never cross a network perimeter you do not own, or an enterprise-security discussion.
Hypothesis: Can we use this safely in a company-controlled environment? Would a team adopt Ophiuchus if no capsule ever left their own infrastructure?
What it is not
A capsule is not a transcript. Sending the whole session is the thing Ophiuchus is trying to beat, because it makes the recipient read everything to find the few facts that matter. A capsule aims at the smallest set of facts that lets someone else act correctly, and it expires.
There is no hosted application, no account system and no team knowledge base. There is no end-to-end encryption: the relay sees the payload. Read privacy and safe use before you put real work into a capsule.
The state of the evidence
One real handoff has been run between two coding agents, by one founder, on one machine. It produced four bug reports. That is early dogfooding, not proof that this works for anyone else, and it is not a basis for claiming it saves time. The measurement that would count is still being built, and the result gets published either way.