statecraft.
Catalog/aicortex

022-client-adapters

Client adapters: one capability matrix, four install paths, zero client code in the core

Lifecycle approvedImplementation pendingVerification unknownQualification unknown

Connecting is one URL, and everything a client needs beyond that is generated rather than written by hand. This spec owns the capability matrix: which clients support remote MCP, which support OAuth against it, and what each offers for automatic capture, which is the only place they genuinely differ. It ships per-client configuration snippets and the hook or notification payloads that turn a session into captured memories, and a route that serves the correct snippet for a client so setup is a copy rather than a document to follow.

Read the full pinned specification ↗

Relationships

depends on

Claimed units

  • establishes
    {
  "kind": "file",
  "path": "clients/README.md"
}
  • establishes
    {
  "kind": "file",
  "path": "clients/matrix.toml"
}
  • establishes
    {
  "kind": "file",
  "path": "clients/claude-code/"
}
  • establishes
    {
  "kind": "file",
  "path": "clients/codex/"
}
  • establishes
    {
  "kind": "file",
  "path": "clients/cursor/"
}
  • establishes
    {
  "kind": "file",
  "path": "clients/antigravity/"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/aicortex-api/src/clients.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/aicortex-api/tests/clients.rs"
}
  • extends
    {
  "nature": "additive",
  "spec": "020-http-api-and-scopes",
  "unit": {
    "kind": "file",
    "path": "crates/aicortex-api/src/router.rs"
  }
}

Source headings

  1. 022: Client adapters
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 4. Functional requirements
  6. 5. Acceptance criteria
  7. 6. Out of scope
  8. 7. Resolved decisions
  9. Verification

Frozen anchors

No frozen anchors declared.