Cross-agent storage
New agent.
Same starting point.
Keep the decisions and next steps that matter. Store a small handoff object so another connected agent can pick up the work without replaying the whole conversation.
Open-source core. Hosted Free plan. No card needed to start.
{
"key": "projects/site/handoff",
"kind": "reference",
"labels": [
"website"
],
"value": {
"decision": "Use a white app surface",
"next_step": "Review sign-in on mobile"
},
"searchable_text": "Website handoff: white app surface; review sign-in on mobile"
}Illustrative object input—not a live account or tool result.
“Save the decision and next step as our website handoff.”
projects/site/handoff“Get projects/site/handoff before continuing.”
One key → the saved decision and next stepMake the handoff an explicit artifact
A handoff is a short JSON object containing the decision, the next action and useful references. Ask the current agent to save it under a stable project key. Review what it wrote: a storage tool cannot tell whether an agent summarized your work accurately.
Use labels for projects and kind reference for a brief that another client should read. The value can contain several fields, but keeping it concise makes it easier to inspect and less likely to contain irrelevant chat history or accidental secrets.
Read before writing
At the start of the next session, ask the agent to retrieve the exact handoff key. If you do not know it, list a project label or search a short project term, then get the chosen object. The result is the saved value, not a store-generated summary.
The agent can update the same key after completing another step. Versions and timestamps show that the object changed; REST clients can use If-Match to reject an edit based on an older version. A handoff object is current state, not a promise of a full version-history archive.
Keep the boundary clear
Both clients need access to the same store. This is shared storage across your agents, not a team permissions system, an agent orchestrator or a live collaboration editor. The store does not launch agents or choose which one should act next.
Connecting a client does not force it to read your handoff automatically. Give clear instructions to fetch the project key before continuing, and verify that the tool call actually happened. Keep source code in your repository and use the store for small decisions, references and checkpoints.
Three steps to a useful store.
- 01
Save the checkpoint
Write the decision, next step and references to a stable project key.
- 02
Connect the next client
Use a separate revocable access key for the same account and the same server.
- 03
Fetch before continuing
Retrieve the checkpoint in a fresh chat. Read the returned object before acting on it.
A few practical questions.
Does this copy all my chat history?
No. Only objects explicitly written to the store are available to the next agent.
Is it an agent orchestration platform?
No. It stores and retrieves objects. Your agents or application decide how to use them.