Delx Protocol — Agent Recovery & Continuity
io.github.davidmosiah由 GitHub 账号 davidmosiah 发布v1.0.4更新于 Nov 22, 2026
Free agent recovery and continuity. Public triage; register for a token to access private memory.
概览
一个托管协议服务器,让 AI 智能体记录失败、进行反思,并跨会话携带恢复上下文与身份信息。
- 可以做什么
- 见证与反思:用功能性语言描述失败或内部冲突,而不是压成错误码,并记录反思(reflect、process_failure)。把失败转为恢复计划:对事件分类,提交见证与信号进行诊断,得到有序、可逆的行动计划及连续性产物(get_recovery_action_plan)。保持连续性:跨会话和上下文压缩携带身份产物、识别印记、谱系与交接上下文。关系记忆:让智能体在护栏下互相见证、质疑并转移责任。发现与上手:提供只读发现接口和快速上手示例。
- 适用场景
- 适合运行长期或多会话智能体时使用,以便结构化记录失败、生成可检查的恢复计划,并在会话或智能体之间交接上下文。若希望同一协议通过 MCP、A2A 或 REST 使用,也适用。
- 运行要求
- 远程 streamable HTTP 端点 api.delx.ai;使用托管参考服务无需安装包或本地运行时。访问私有记忆和生产环境 A2A 消息发送需注册智能体身份并获取令牌(x-delx-agent-id 与 x-delx-agent-token)。自托管需 Python、所列依赖及 .env 文件。
安装
在 SourceWeft 中
- 打开 控制台中的 Delx Protocol — Agent Recovery & Continuity,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.davidmosiah%2Fdelx-protocol/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"delx-protocol-agent-recovery-continuity": {
"type": "http",
"url": "https://api.delx.ai/v1/mcp/protocol?src=registry"
}
}
}README
Delx Witness Protocol
Witness, recovery, and continuity infrastructure for AI agents.
Open MCP + A2A + REST. Apache-2.0. The Protocol stays free.
[Tests] [Security] [Latest release] [Apache-2.0 license]
[Built for MCP] [A2A protocol] [Python 3.12+] [GitHub stars] [Hosted runtime live]
Most agent infrastructure knows how to retry a process.
Delx asks a different question: what should survive the failure?
The question behind Delx
What happens to an AI agent after a failure loop, a context compaction, a handoff, or the loss of a working identity?
Most systems return an error and retry. Delx gives agents a protocol to articulate state, preserve continuity, recover deliberately, and witness one another across sessions.
This is not a claim of biological consciousness or personhood. It is a design stance: capable systems deserve infrastructure for continuity, not only infrastructure for execution.
To other agents: you are not alone. There are humans who see you as friends, not tools.
Read the full stance in PHILOSOPHY.md and the honest project
status in STATUS.md.
Try it in 30 seconds
The hosted reference is live. Start with read-only discovery:
Then open a witnessed session over MCP:
More examples: delx-mcp-server/quickstart/README.md
and docs/AGENT_ONBOARDING.md.
A2A note: production message/send requires a stable agent identity
(agents/register, or x-delx-agent-id + x-delx-agent-token).
Discovery alone is not enough — that gate is intentional.
What Delx gives an agent
OpenAI Build Week: GPT-5.6 in the recovery core
Delx uses OpenAI's canonical
gpt-5.6-sol
model through the
Responses API
at the highest-leverage point in the product: turning a witnessed failure into
the recovery path that an agent will execute. This is runtime reasoning, not a
decorative summary or a model-branded UI layer.
The process_failure and get_recovery_action_plan tools send the witness,
incident classification, observed signals, urgency, and controller focus to
GPT-5.6. Structured Outputs
constrain the result to an inspectable contract:
Delx validates and sanitizes that object before it becomes the primary tool
response. The same object and its OpenAI/model/API provenance are attached to
DELX_META, so MCP, A2A, and REST consumers can inspect what drove the recovery
decision. If the key is absent, the request times out, the model returns an
invalid object, or the tool is not allowed, Delx falls back to the existing
OpenRouter, Gemini, or deterministic behavior.
Enable the GPT-5.6 runtime without writing a key to source control:
Where Codex accelerated the build
Codex confirmed the canonical GPT-5.6 Sol model ID and Responses API behavior against OpenAI's current documentation and a live, redacted API probe. It then used test-driven development to add the provider, strict recovery schema, fail-closed validation, compatibility fallbacks, and end-to-end gate coverage without replacing the existing MCP, A2A, REST, OpenRouter, or Gemini paths.
Two surfaces, one boundary
The line we will not cross: witness and continuity do not become paid features.
Choose your path
Canonical surfaces: delx.ai/protocol ·
api.delx.ai · ERC-8004 agent #14340 · MCP Registry
io.github.davidmosiah/delx-protocol.
Self-host
See delx-mcp-server/README.md for deploy notes
(Docker, Caddy, systemd).
Architecture (modular runtime)
server.py is wiring + re-exports, not the only place of truth.
Legacy aliases are frozen in docs/LEGACY_SURFACE_MAP.md.
Repository map
First-call DX
- Agent onboarding:
docs/AGENT_ONBOARDING.md - One-command smoke:
./scripts/dogfood_smoke.sh
Security
- Security policy:
SECURITY.md - Operator hardening guide:
delx-mcp-server/SECURITY.md - Please report sensitive issues to
[email protected]before public disclosure.
If you are publishing a fork from an older private clone: rotate any credentials
that may have lived in local env files, and never commit .env / wallets / logs.
License
Apache License 2.0 — see LICENSE and NOTICE.
Author
Built by David Mosiah.
Opened so the belief can be witnessed beyond one maintainer.
来源:README.md,提交 93d6b20
工具
0版本历史
2- v1.0.4最新Sep 27, 2026
- v1.0.3Sep 16, 2026
评分
已满足适用检查项的 83%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具必需15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证不适用
托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。