Agent Memory

Agent Memory gives SCHEMABOUND sessions an isolated, auditable memory store. Each session accumulates its own history of observations, tool calls, and decisions — scoped so that one session never reads or contaminates another, and past context can always be retrieved exactly as it was recorded.

What It Provides

Per-session isolation — memory written during one session is never visible to another
Chronological history — entries are ordered and retrievable in the sequence they were recorded
Reproducibility — prior agent observations, tool call results, and decisions remain accessible across the full lifetime of a session
Prompt augmentation — session memory can be injected automatically into prompt hooks so agents carry prior context without the caller managing it manually

REST API

Sessions

GET /api/agent-sessions

Returns the list of all active sessions.

Response

{
  "data": [
    {
      "id": "abc-123",
      "created_at": "2026-04-19T10:00:00Z",
      "last_seen_at": "2026-04-19T10:42:00Z"
    }
  ]
}

Memory Entries

GET /api/agent-memory/:session_id

Returns all memory entries for a session in chronological order.

Response

{
  "data": [
    {
      "entry_type": "tool_call",
      "content": "{ \"tool\": \"query\", \"result\": \"...\" }",
      "created_at": "2026-04-19T10:05:00Z"
    }
  ]
}

POST /api/agent-memory/:session_id
Content-Type: application/json

{
  "entry_type": "observation",
  "content": "User confirmed the report looked correct."
}

Appends a new entry to the session’s memory store.

All responses follow the { data: ... } envelope used by the rest of the SCHEMABOUND API.

Prompt Hook Augmentation

When a prompt hook resolve request includes a session_id, SCHEMABOUND automatically fetches the session’s memory entries and makes them available as {{memory_context}} inside the hook template. The caller does not need to retrieve or serialize prior context manually.

POST /api/prompt-hooks/:id/resolve
Content-Type: application/json

{
  "session_id": "abc-123",
  "context": { "user_id": "alice", "organization_id": "acme" }
}

The resolved template receives {{memory_context}} alongside the standard context variables before rendering.

Frontend

The Agent Memory dashboard provides:

Session list — all active sessions with timestamps
Memory detail — selecting a session shows its entries in order, with entry type and content

Keyboard shortcuts