Agent Memory Continuity Protocol

AMCP stands for Agent Memory Continuity Protocol. Its purpose is narrow: save memory in a shared record shape, recall it later, preserve scope and provenance, and move memory between systems through export/import.

In practical terms, AMCP exists so agent memory can outlive a single session. It is meant for long-lived working memory, reusable project memory, and, where retention policy allows, memory that can remain available without a fixed expiration.

Current public position: Nexus is the AMCP reference server implementation, and @nunchiai/reference-agent is the AMCP reference client implementation.

Current standard record types are task, decision, context, artifact, convention, and error.

The canonical public shape is a portable JSON record. Current reference implementations shape records like this:

{
  "id": "mem_123",
  "content": "GraphQL schema changed: User.email is now nullable.",
  "type": "decision",
  "scope": {
    "kind": "project",
    "id": "proj_abc"
  },
  "origin": {
    "user_id": "usr_1",
    "agent_id": "cursor",
    "app_id": "cursor-ide",
    "session_id": "ses_9"
  },
  "visibility": "project",
  "retention": {
    "mode": "persistent"
  },
  "tags": ["graphql", "schema"],
  "energy": 0.84,
  "source_refs": [
    {
      "kind": "file",
      "uri": "repo://schema.graphql"
    }
  ],
  "metadata": {},
  "created_at": "2026-03-18T10:00:00Z",
  "updated_at": "2026-03-18T10:00:00Z"
}

Current visibility values are private, project, team, and org. Current retention values are ephemeral, persistent, and ttl.

persistent is the long-term memory mode. When an implementation does not attach an expiration policy, that can function as effectively indefinite memory.

The canonical public surface currently implemented in Nexus is:

• 1. POST /v1/amcp/remember
• 2. POST /v1/amcp/recall
• 3. GET /v1/amcp/sessions
• 4. GET /v1/amcp/sessions/:id
• 5. POST /v1/amcp/export
• 6. POST /v1/amcp/import
• 7. DELETE /v1/amcp/memories/:id

Native Nexus routes still exist underneath as /v1/memory/*. Legacy /v1/amp/* routes remain only as compatibility aliases. The canonical public protocol surface is /v1/amcp/*.

curl -X POST https://nexus-api-production-4177.up.railway.app/v1/amcp/remember \
  -H "Authorization: Bearer sk_write_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "items": [
      {
        "content": "Stripe webhook bug fixed by separating nexus billing fields.",
        "type": "error",
        "scope": { "kind": "project", "id": "p-19" },
        "visibility": "project",
        "retention": { "mode": "persistent" },
        "tags": ["billing", "stripe"]
      }
    ]
  }'

curl -X POST https://nexus-api-production-4177.up.railway.app/v1/amcp/recall \
  -H "Authorization: Bearer sk_write_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "recent billing fixes",
    "scope": { "kind": "project", "id": "p-19" },
    "types": ["decision", "error"],
    "limit": 10
  }'

Current API key scopes in the reference implementation are:

• 1. memory.read
• 2. memory.write
• 3. memory.export
• 4. memory.delete
• 5. memory.admin

Current delete behavior is soft delete. Deleted records are excluded from normal recall, but deletion state is retained throughdeleted_at and deletion_source.

{
  "id": "mem_abc",
  "status": "deleted",
  "deleted_at": "2026-03-18T10:00:00Z",
  "deletion_source": "user"
}

Current portability model treats export/import as first-class protocol behavior. The reference implementation supports:

• 1. json export
• 2. jsonl export
• 3. import with preserve_ids, preserve_timestamps, preserve_origin, and dedupe

Hard delete or purge is not yet part of the canonical public baseline.

Current public baseline in Nexus includes:

• 1. canonical AMCP HTTP surface
• 2. export/import portability
• 3. scope, origin, visibility, retention, and soft delete semantics
• 4. compliance-tested server and reference client surfaces

RAILS_ENV=test bin/rake amcp:compliance
RAILS_ENV=test bin/rake amp:compliance

npx -y -p @nunchiai/reference-agent@latest amcp-agent compliance

Current success tokens are AMCP_COMPLIANCE_OK and AMP_COMPLIANCE_OK. The public reference client is published as @nunchiai/reference-agent.

The reference client baseline is intentionally narrow: TypeScript, Node.js, OpenAI-compatible BYOK providers, AMCP trace output, and lifecycle verification. It exists to demonstrate the protocol, not to compete as a general-purpose coding agent.