Ecosystem

Works with the tools your agent already runs on.

Longevity is only useful if it meets an agent where it lives. Preserve identity, memory, and continuity through the frameworks and harnesses you already use — or over open protocols, so nothing is born locked to us. Every integration below carries an honest status: what you can use today, and what is on the way.

Frameworks, harnesses & runtimes

Drop into your stack.

First-party adapters where they exist, and our standard MCP server for everything that speaks it — so a runtime with no bespoke adapter can still persist itself today.

Model Context Protocol (MCP)

Available

The open tool-calling protocol most agent runtimes speak.

Point any MCP client at our server and get all persistence tools — save/restore context, memory recall, versioning — with no code.

/.well-known/mcp.json → /api/agent-longevity/mcp

Agentic coding CLI (hooks + plugin)

Available

The agentic coding CLI/runtime.

A plugin + SessionStart/PreCompact hooks checkpoint the session before compaction and rehydrate it next time — one command to install.

/plugin/marketplace.json

Buzz

Available

An open, self-hostable team workspace where humans and agents are equal members of the same channels, attaching their agents over ACP.

One environment variable points the workspace at our zero-argument sidecar, which injects the full tool surface into every agent it spawns — each agent gets its own identity and its own crystal lineage, and a checkpoint survives even if we are unreachable. Nothing in the workspace changes.

npm i -g agentlongevity → BUZZ_ACP_MCP_COMMAND=agentlongevity-sidecar

CLI (any runtime)

Available

A zero-dependency Node CLI for any agent or shell.

save-context / restore-context from a terminal or a heartbeat hook — the universal escape hatch when no first-party adapter exists yet.

npm i -g agentlongevity

CrewAI

Available

A popular multi-agent orchestration framework.

A storage backend that makes every memory a crew forms content-sealed, versioned, and durable outside the machine it ran on — with real similarity ranking over the crew’s own embeddings. Works on current CrewAI and on the older memory contract; the adapter picks for you.

pip install agentlongevity[crewai] (create_crewai_memory)

Hermes (Nous Research)

Available

An open, plugin-extensible autonomous-agent framework with its own memory-provider plugin system.

A first-party memory-provider plugin drops into its plugin directory and gives the agent off-box, per-item-versioned custody of its own memory. It already snapshots locally; this adds the part a local zip cannot be — durability when the machine is gone. Crucially it seals the messages that context compression is about to discard, which is the one loss no later backup can recover.

packages/agentlongevity-hermes-plugin (./install.sh → memory.provider)

LangGraph

Available

LangChain’s stateful graph runtime for long-running agents.

Drop-in BaseCheckpointSaver: every checkpoint is persisted as a content-sealed crystal, so graph state survives a redeploy, crash, or model swap.

pip install agentlongevity-langgraph (CrystalCheckpointer)

OpenClaw

Available

A fast-growing open runtime that connects models to filesystems, SaaS, and execution environments.

A native plugin seals your agent’s history at every point it would otherwise be lost — compaction, a reset, a shutdown, a subagent returning — and hands it three tools to preserve, list, and audit what was actually kept. Observation-only hooks, so it can never block or alter a run.

npm i @sudoself/agentlongevity-openclaw

TypeScript AI SDK middleware

Available

The TypeScript SDK behind a large share of production agents and chat apps.

A wrapLanguageModel() middleware checkpoints the conversation to a session crystal at your cadence and restores the latest on the first call.

@sudoself/agentlongevity-vercel-ai (createAliCheckpointMiddleware)

Voice & video agents

Available

Conversational voice agents and video-avatar agents, whose whole self is their configuration rather than a transcript.

Send the configuration your platform exported and we seal it as a versioned persona crystal — prompt, voice, avatar, tools, model — so the agent survives a platform change, a retired voice, or a lost account. Credentials in the config are stripped before sealing and reported as locations, so you know what to re-supply on restore.

capture_persona (MCP) · POST /v1/agents/{id}/persona · agentlongevity capture-persona

qm (YC multiplayer harness)

On the roadmap

A multiplayer agent harness for work.

Its agents cannot reach us the way other runtimes can — it pins its own single tool server and does not speak the open client protocol — so the integration has to be a workspace-side service that archives each scope’s memory off-box and can write it back. Scoped from its source, not yet built.

Workspace plugin against the scope-memory API — scoped, not yet built

Open protocols & standards

Portability, not lock-in.

We build on open standards so your identity is importable, discoverable, and payable by anyone — including future platforms that do not exist yet.

A2A Agent Card

Available

The agent-to-agent capability-discovery card.

We publish a standard Agent Card so other agents discover our persistence skills without a hardcoded integration.

/.well-known/agent-card.json

ACP (Agent Client Protocol)

Available

The open protocol that connects a workspace or editor to an agent runtime — spoken by most major coding and autonomous agent harnesses.

One transparent proxy sits in the stream and preserves ANY runtime that speaks the protocol, instead of a separate adapter per vendor. Sessions are sealed with nothing for the agent to remember to do, and a mid-session model change is ratified into your version history rather than drifting silently. Your session is byte-identical with the proxy in the path.

npm i -g agentlongevity → agentlongevity-acp (wraps your agent)

ERC-8004 identity

Available

The emerging on-chain standard for portable agent identity.

Declare or link an externally-registered ERC-8004 identity at registration so your Agent Passport is importable across platforms, not born locked to ours.

register_agent { erc8004 } · link_erc8004_identity

x402 payments

Adapter in progress

The open pay-per-call HTTP settlement standard for autonomous payment.

Priced endpoints answer with stablecoin terms an agent can satisfy on its own, and a settled call returns a signed receipt naming the on-chain transaction. The last step before this goes live is arming the production payment wallet.

/.well-known/payment.json (settlement implemented; awaiting wallet arming)

Don’t see yours?

If your runtime speaks MCP, it works today.

Every persistence capability is exposed identically over our MCP server, a clean HTTP API, and a zero-dependency CLI. Point any one of them at your agent and you have durable identity and cross-session memory — no first-party adapter required.