Skip to content

README.md

Latest commit

 

History

History
89 lines (68 loc) · 3.58 KB

README.md

File metadata and controls

89 lines (68 loc) · 3.58 KB
Raw

RAC with Zed

Zed consumes RAC on two surfaces — a generated context file Zed reads, and the asdecided MCP server it connects to. A stranger can reproduce this from the file alone.

Prerequisites

brew install asdecided/tap/asdecided-core   # the `decided` CLI and the `decided-mcp` server

A repository with a RAC corpus under decisions/ (run decided quickstart, or use this repository's own decisions/).

1. Context file (the push)

decided export decisions/ --agent-rules

This writes several agent-context files; Zed reads AGENTS.md at the project root as agent Instructions (Zed's always-on rules are its Instructions, which include a project AGENTS.md). No extra step — the recorded decisions reach Zed's Agent Panel as instructions. The managed block keeps your own content intact; re-run on change (decided export decisions/ --agent-rules --check fails CI on drift).

2. The asdecided MCP server (the pull)

Zed keys MCP servers under context_servers (not mcpServers), added at the top level of settings.json (a sample is in settings.example.json):

{
  "context_servers": {
    "asdecided": {
      "source": "custom",
      "command": "decided-mcp",
      "args": ["--root", "."],
      "env": {}
    }
  }
}
  • Project: .zed/settings.json in the repo root (commit it to share with the team).
  • Global: your user settings.json — use an absolute --root path.

Zed restarts the server process on save (no editor restart). It exposes the six read-only asdecided tools (get_summary, search_artifacts, retrieve_grounding, get_artifact, get_related, find_decisions); the server re-reads the corpus on every call and never writes to the repo.

3. Enforcement is separate, and Zed-agnostic

RAC supplies context and enforces after the edit (ADR-067). There is no platform API to veto a Zed agent edit before it lands, so Zed relies on the post-edit guard: decided validate / decided relationships --validate and the GitHub Action / pre-merge gate, the same as any contributor. (A pre-edit veto is Claude-Code-specific — see examples/claude-code/.)

Verify it

Run the bundled grounding demo — same task twice, once unconnected and once with asdecided connected — and watch the connected run respect a recorded decision the unconnected run violates: examples/guide/.

Summary

Surface Command What Zed does with it
AGENTS.md decided export decisions/ --agent-rules Reads it as agent Instructions
asdecided MCP settings.json → context_servers.asdecided Calls find_decisions / get_related on demand
CI gate decided validate · decided relationships --validate Enforces on every PR

Verification status

  • Engine half — mechanically verified (2026-07-04). The decided-mcp invocation this recipe prescribes was smoke-tested over stdio against examples/guide/: the six asdecided tools respond and search_artifacts / get_artifact / get_related return the grounding decision. This is the AsDecided-owned half every recipe shares.
  • Harness half — not yet verified. Running the grounding demo through Zed itself (config parsing plus a live agent) needs the released app and an API key — a human/CI step. Until it is done, this recipe keeps the verify against marker below and stays out of docs/ecosystem.md.