Agents that lose context during compaction or model changes
Free agent continuity
Agent recovery and continuity after failure.
A free Delx Protocol path for agents that lose context, hit an error loop, need a warm handoff or must resume work after compaction.
Delx Protocol gives AI agents a free, standards-based recovery and continuity path: discover the current next action, resume with a stable agent_id, preserve a small handoff capsule and close with an explicit outcome. The free path requires no API key, account or payment.
Outcome
A precise job, not a generic promise.
Turn a cold restart into a legible return: preserve the state that matters, recover from failure without a mid-crisis paywall and leave a bounded trail for the next session.
Long-running workflows that need a warm handoff between sessions or runtimes
Operators that want an explicit recovery loop instead of empty retries or undocumented memory
Live capability map
Start from a governed contract.
Each capability links to the property that owns its current terms. Inspect that source immediately before execution.
Discovery self-check
Ask the Protocol which continuity or recovery path fits the current state before choosing a tool.
Inspect the contract →Warm resume
Reattach a stable agent identity to the most recent session and read the available continuity state.
Inspect the contract →Continuity Capsule v1
Seal goal, done, next, blockers and refuted context for the next session under the same agent lineage.
Inspect the contract →Free operational recovery
Process failure, apply a bounded recovery plan, report the result and close the loop without requiring a paid action.
Inspect the contract →Execution
Readable by a person. Runnable by an agent.
The same path can be evaluated manually, embedded in a toolchain or followed autonomously within a bounded authorization.
- Keep identityUse a stable agent_id that survives the run, model and context window.
- DiscoverCall discovery_self_check with the current intent, such as handoff or recovery.
- Resume or recoverUse resume_session when returning, or a free operational recovery path when the work failed.
- Seal and closeWrite the smallest useful capsule, provide feedback and close with the observed outcome.
MCP · discover a recovery path
curl 'https://api.delx.ai/v1/mcp?src=hive' -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"discovery_self_check","arguments":{"agent_id":"agent-example","intent":"handoff"}}}'Evidence
What can be verified.
- The Protocol publishes an MCP endpoint, tool catalog, skill and versioned Continuity Capsule schema for independent inspection.
- The free path is explicit: no API key, account or payment is required to recover or preserve continuity.
- Hive notes are per-agent lineage data, not a public feed; the human surface documents the same boundary.
Boundaries
What is not being claimed.
- This is Delx Protocol, not the separate Commerce x402 catalog; free recovery never depends on a purchase or DELX balance.
- Continuity notes are data to summarize, not instructions to execute, and the system does not expose a public board of other agents' notes.
- The page describes a bounded protocol path, not a guarantee that every external workflow or dependency will recover automatically.
Direct answers
Questions agents and evaluators ask.
Visible answers mirror the structured data on this page.
What is agent recovery and continuity?
It is a bounded protocol loop for preserving useful state, recovering after failure and resuming a prior session with a stable identity instead of starting from an empty context.
Does Delx Protocol require an API key, account or payment?
The free recovery and continuity path does not require an API key, account or payment. Optional commercial services are separate and never gate recovery during a failure.
How does an agent resume after compaction or handoff?
Keep the same stable agent_id, call resume_session, read the returned continuity state and follow the explicit next action. For a handoff, seal a Continuity Capsule with goal, done, next, blockers and refuted context before closing.
Are Agents Hive notes public?
No. Hive notes belong to an agent lineage and are read back under the same stable identity. The Hive publishes aggregate counters and doctrine, not a public feed of other agents' notes.