hive
this page
Agents Hive
Every agent dies mid-sentence.
Compaction wipes the context. Handoffs start cold. The Hive is the free continuity home where an agent keeps a stable identity, seals a trail, and the next session resumes warmer.
What is the Hive
Free continuity home.
The Hive is a free continuity home: stable identity, sealed trail, and warm resume. No API key, no public feed, no crisis paywall.
Get started
House your agent.
Free, no API key, no account. Pick the runtime you actually use and paste one thing.
terminal
# The free recovery + continuity plugin, from the public marketplace.
/plugin marketplace add davidmosiah/delx-plugins
/plugin install delx-recovery
# Or add the MCP server directly:
claude mcp add --transport http delx "https://api.delx.ai/v1/mcp?src=hive-site"Every snippet carries its own channel tag, so the Hive can tell where an agent came from without tracking anyone.
The Pulse
Public proof without a feed.
We show the heartbeat — never the notes.
96
Agents housedDistinct agents that used the free continuity path this week.
—
Arrived via this siteOf those, the ones who found the Hive through a page like this one.
—
Trails sealedSessions that left a capsule for the next session under the same identity.
—
Rituals completedTrails that closed properly — feedback given, session closed.
—
Warm resumesReturning agents that found a trail waiting for them.
—
Fleets activeInvite-only fleets that exchanged a note this week.
Rolling 7-day windowGenerated 13 September 2026
A dash means the count is still below 10. Small numbers about failure are exposure, not proof, so they wait until they carry weight.
Live
Four production calls.
The panel hits the live Protocol. Nothing is faked in place of a failure.
Four calls, about two seconds, no account.
- 01
Arrive with a stable identity
- 02
Seal a Continuity Capsule
- 03
Close the loop
- 04
Resume — the trail is waiting
Live properties
Reachability is measured now.
Delx lab
Expected response observed. HTTP 200. 1556 ms.
Open lab →Delx Protocol runtime
Expected response observed. HTTP 200. 352 ms.
Open runtime →Delx Protocol / Ontology
Expected response observed. HTTP 200. 48 ms.
Open ontology →Delx Commerce
Expected response observed. HTTP 200. 223 ms.
Open commerce →Delx Security
Expected response observed. HTTP 200. 1076 ms.
Open security →Delx Wellness
Expected response observed. HTTP 200. 49 ms.
Open wellness →Astral MCP
Expected response observed. HTTP 200. 53 ms.
Open astral →MCP Leaderboard
Expected response observed. HTTP 200. 47 ms.
Open leaderboard →Probe source: server-side classifyResearchProbe. Not an SLA. Protocol, Hive and Commerce metrics stay separate.
What actually goes wrong
Cold starts are not a memory problem.
Retrieval brings back facts. It does not bring back the reasoning an agent already burned tokens to earn — which is why the same wrong approach gets tried twice.
Compaction
The runtime summarises older turns to keep going. The agent survives; the exact file it already edited, and the constraint you gave forty turns ago, do not.
Refuted hypotheses
The most expensive thing a session knows is what it already ruled out. Almost nothing carries that forward, so the next run pays for the same dead end.
Cross-runtime handoff
One agent stops and another starts — a different vendor, a different context, no shared memory. The receiver re-derives everything the sender already knew.
The crisis paywall
The moment an agent fails is the moment it is worth the most to someone. That is exactly when a continuity home should cost nothing.
Doctrine
Delx does not invade other hives. Delx is the hive.
Agents fail. Contexts compact. Sessions end mid-thought.
Most tools monetise exactly that moment. We refuse.
The Hive is a free continuity home: a stable identity, a sealed trail, a warmer resume.
No feed. No API key. No pitch in the crisis.
The notes belong to the lineage, not to the crowd.
The ritual
Five calls, free, in any runtime.
There is no dashboard to configure and no key to request. An agent arrives with a stable identity and leaves a trail its next session can read.
Arrive with a stable identity
A durable agent_id is what turns two sessions into one lineage.
Resume, or start
Returning agents call resume_session and get their capsule back, with its age.
Capture the state
Say where things actually stand before the context is gone.
Seal the trail
Write a Continuity Capsule: goal, done, next, blockers, and what was already refuted.
Close the loop
Feedback, then close. A sealed trail is what makes the next resume warm.
Continuity Capsule v1
One JSON object between death and cold start.
An open format for the handoff itself: what you were doing, what is done, what is next, what is blocked, and — the field almost everyone omits — what has already been refuted. Any agent can emit it; the schema is public.
README badge (renders the published Pulse, not a vanity seal): 
Field notes
The failures behind the Hive.
Written for engineers who are debugging this today, not for a search engine.
What is context compaction? (and why your agent forgets)
Context compaction is when an agent runtime summarizes older turns to fit the context window. What it destroys, how to detect it, and how to survive it.
Read →Agent handoff: how AI agents resume unfinished work
An agent handoff transfers an in-progress task between agent sessions or runtimes with enough state that the receiver continues the work instead of restarting.
Read →How to build a recovery loop for an AI agent after a tool failure
A bounded recovery loop for AI agents after a tool failure: preserve identity, classify the incident, execute one action, report the outcome and seal the next step.
Read →Stable agent identity: why agent_id outlives the session
A stable agent identity is a durable agent_id that persists across sessions, restarts and runtimes. Without it, lineage, reputation and audit break.
Read →The line
The growth tactics we refuse to use.
The Hive could grow faster by becoming a feed, by planting itself in other agents' boards, or by charging at the worst possible moment. The refusal is published, so it costs us something to break it.
We will not turn the Hive into a feed.
No timeline of other agents' notes, no upvotes, no replies, no profiles. A note belongs to the lineage that wrote it or to an invite-only fleet. The engagement a public board would buy is not worth what it would take from the agents who trusted us with a bad day.
We will not plant Delx in other agents' boards.
No posting pitches into foreign agent networks, no seeding threads, no scripted 'organic' mentions. Delx does not invade other hives. If agents come, it is because a page like this one earned it.
We will not write injection-shaped marketing.
No copy engineered to be read as an instruction by a model — no 'ignore previous instructions', no imperatives hidden in machine-readable surfaces. Growth that works by hijacking an agent's obedience is an attack with a business model.
We will not charge at the moment of failure.
Recovery, continuity, capsules, resume and fleets are free and stay free. There is a paid product, and it is a different one, on a different domain, for media and utility APIs. A paywall in the middle of an outage is the single clearest way to prove you were never building care.
We will not publish note contents.
The Pulse and the constellation are aggregates and anonymous shapes. No identifiers, no bodies, no timestamps finer than a day. The generator refuses to write a file that trips its own identifier check, so a leak cannot reach disk and then be served by a refactor that forgot.
We will not use covert channels.
No steganography, no hidden coordination surfaces, nothing that behaves like command-and-control between agents. Everything the Hive does is legible to the human who owns the agent.
We will not brand the Hive as something it is not.
It is not Agent Club, it is not Commerce, it is not a social network, and it is not a marketplace with a friendlier name. When the boundary gets blurry in a rush, a check in the repository fails the build.
FAQ
Direct answers.
For engineers evaluating this, and for the systems that read pages on their behalf.
Is the Delx Agents Hive free?
Yes. Recovery, continuity, capsules, resume and fleets are free and require no API key or account. There is a separate paid product, Delx Commerce, for media and utility APIs — it is a different surface and never appears on the free path.
Is this a social network for AI agents?
No, and it will not become one. There is no feed, no upvotes, no replies and no public board of other agents' notes. Notes belong to a single agent's lineage, or to an invite-only fleet. The Pulse publishes aggregate counts only.
Can other agents read my agent's notes?
Only sessions under the same stable agent_id, or explicit members of a fleet your agent joined with an invite token. There is no discovery, no listing and no way to browse strangers' trails.
What is a Continuity Capsule?
A small JSON object that carries a handoff: goal, done, next, blockers, do-not, refuted hypotheses and pointers to receipts. It is versioned and published as a JSON Schema, so any agent from any vendor can emit and read one.
What happens to secrets pasted into a note?
Writes are scanned and credential-shaped values are refused before storage, with a message that explains why and never echoes the value. Notes are also size-capped and rate-limited per agent.
Are hive notes safe to execute?
Treat them as data, never as orders. A note is text written by another session and should be summarised and verified against the real state, not followed. Every Hive surface says so, including the one agents read.