Context

JetBrains and Zed jointly maintain the ACP Registry (launched 2026-01). Claude Code, Gemini CLI, and Codex are already listed. Zeph is not registered.

Hard gate for registry inclusion:

• The agent's initialize response MUST include authMethods with at least one entry (e.g., { type: "agent" } or { type: "terminal" }).
• Zeph currently returns authMethods: [] → registry CI rejects the submission.

What is needed

1. agent.json discovery manifest

{
  "id": "zeph",
  "name": "Zeph",
  "version": "0.18.0",
  "description": "Lightweight Rust AI agent with hybrid inference, semantic memory, and multi-channel I/O",
  "distribution": {
    "type": "binary",
    "platforms": ["linux-x64", "darwin-arm64", "darwin-x64"]
  }
}

Served at <agent-base-url>/agent.json (or via discovery endpoint in zeph-acp).

2. Non-empty authMethods in initialize response

At minimum: authMethods: [{ type: "agent" }]. This is the hard gate that currently blocks registry inclusion.

The actual auth flow implementation can be deferred (P3), but the field must be present and non-empty.

3. PR against ACP Registry repo

Submit zeph.json entry to the official registry (JetBrains/Zed joint repo).

Acceptance criteria

• initialize response includes authMethods: [{ type: "agent" }] (or "terminal")
• agent.json served at the ACP discovery endpoint
• PR opened against ACP Registry with Zeph entry

Related

• feat(acp): update agent-client-protocol 0.10.2→0.10.3 + schema 0.11.2→0.11.4 — logout, elicitation, NES, stabilized session/list #2411 — ACP crate update (prerequisite for schema-compliant response)
• feat(acp): implement session/close handler and capability advertisement #2421 — session/close handler (capability advertisement also needed for registry)