memory layer.

Hosted memory runtime for agents
Docs Agents Connect
Resources
ArchitectureRuntime boundaries, schemas, and request path. IntegrationsCodex, Claude, CI, scripts, and custom clients. Use casesHandoff, research, incidents, and automations. CapabilitiesFull service and agent-facing capability ledger. ExamplesRequest and response fixtures for client builders. API explorerEndpoint shapes and hosted bridge calls. SDKsCopyable HTTP snippets and playbooks. SecurityBoundary, headers, auth, and disclosure model.
Log in Continue with GitHub
Operations

Operate hosted memory without guessing.

The service exposes the controls an operator needs: usage, audit trails, key rotation, ingestion history, exports, manifests, and runtime status.

Service status Security model Deploy plan
43

service features tracked in the manifest

83

hosted bridge tools with argument hints

27

public and workspace route groups

observe rotate export recover
01 / Observe
Know what happened

Usage events and audits show route, actor, key label, status, and workspace scope.

02 / Rotate
Keep keys disposable

Create keys per agent, worker, or pipeline, then revoke them without touching memory data.

03 / Ingest
Track imports

Paste, file, and batch imports leave run records with source metadata and item counts.

04 / Export
Inspect and back up

Recent exports let you review a limited set of workspace memories. They are not a full database backup.

Operator ruleEvery agent should have its own named key.
Debug ruleUse usage history before guessing why a client failed.
Recovery ruleUse a verified database backup before destructive cleanup.

Operator loop.

A small weekly loop catches most workspace problems before they turn into stale memory.

Review usage

Check route volume, failed calls, inactive keys, and high-noise clients.

Rotate keys

Replace long-lived or shared keys with named, scoped keys per client.

Check ingest

Confirm large imports split cleanly and did not flood memory with duplicates.

Save handoffs

Require checkpoints at the end of agent sessions and long automations.

Deploy path.

Releases should be boring: local verification, archive sync, rebuild, restart, then live checks.

Deploy JSON
01 verify
git diff --check, python -m pytest -q, and python -m compileall app.
02 sync
scripts/deploy.sh streams the current git archive to the VPS app directory without copying secrets.
03 restart
The remote service runs docker compose up -d --build web against the preserved .env and data volume.
04 prove
scripts/live-check.sh verifies readiness, architecture, manifest, and the rendered pages.

Observability contract.

Workspace operators can inspect latency, failure rate, slow routes, runtime cache, API volume, and ingestion history.

Latency

Workspace API events record route timing in metadata so slow searches and memory writes show up quickly.

Failure rate

The observability endpoint samples recent calls and reports failed routes without exposing private memory content.

Ingest health

Import runs stay visible beside runtime cache state, making large data loads easier to debug.

Runbook.

Concrete responses for common hosted-memory incidents.

noisy key
Inspect usage, create a replacement key with a clearer label, update the client, then revoke the noisy key.
bad ingest
Review ingest run metadata, export recent memories, forget bad records if needed, then re-import with smaller chunks.
stale context
Use search, recall hints, and session handoff snapshots to identify which state should be challenged or superseded.
client failure
Fetch `/connect`, verify the endpoint URL, list bridge tools, then test a small `recall_recent` call.

Controls exposed today.

The manifest is intentionally public so client builders can track the service surface.

Manifest JSON

Workspace isolation

Each workspace receives its own Engram schema and service boundary.

GitHub login

User identity is handled through GitHub OAuth with no local passwords.

Workspace invites

Issue shareable invites with role-aware membership records.

Scoped API keys

Generate workspace keys for agents, apps, and ingestion pipelines.

API usage trail

Track service calls by route, key, and workspace.

Audit history

Record workspace actions such as keys, invites, memory writes, and bridge calls.

Hosted MCP bridge

Call selected Engram tools through a simple HTTP JSON bridge.

Bootstrap payloads

Discover URLs, headers, tools, and skills from one workspace endpoint.

Starter skills

Download markdown skills that teach agents how to use hosted memory.

Recent memory API

Load the latest workspace memories without custom query code.

Search API

Run hosted retrieval against the real Engram memory graph.

Remember API

Store narrative, fact, and procedure memories over HTTP.