Skip to main content

Continuum logo

Continuum

Continuum is an open remote state and memory backend for AI coding agents. It gives agents a shared source of truth for project state, serialized work locks, and durable episodic memory without forcing every agent to reread the whole repository on every prompt.

The ambition is an open protocol and reference implementation for the whole developer ecosystem: Claude Code, Codex, local agents, CI agents, IDE agents, and future MCP-compatible tools. The closest infrastructure precedent is OpenTofu/Terraform remote state: a small authoritative state file, backend-provided locking, and protections against stale writes.

What It Provides

State and concurrency

  • state.json API for semantic project summaries, branches, dependency maps, and known bugs.
  • Lock API for preventing concurrent agents from clobbering the same project.
  • lineage and serial checks to reject stale state pushes.

Memory intelligence

  • Hybrid memory retrieval that fuses keyword (BM25) and vector similarity via reciprocal rank fusion, with a zero-dependency default embedder and optional sentence-transformers/OpenAI adapters.
  • Extraction and consolidation that distills raw logs into compact summaries and deduplicates near-identical episodes (ADD / UPDATE / SKIP).
  • Temporal validity so a superseded fact is invalidated rather than duplicated, preserving the timeline of what was true when.
  • A lightweight knowledge graph for entity and relationship (multi-hop) recall, with temporal edges.
  • Automatic redaction of secrets and PII before any memory is persisted.
  • Observability metrics (recall hit-rate, estimated tokens saved) and a recall@k evaluation harness.
  • A prompt-cache-aware context assembler that orders content most-stable-first for maximum provider cache reuse.
  • A procedural-memory template library for repeated Terraform/AWS/Databricks workflows.

Storage

  • Local filesystem backend with a SQLite memory index and usage dashboard for development.
  • AWS backend shape for S3 state/memory objects and DynamoDB lock rows, with optional at-rest payload encryption.
  • Postgres + pgvector backend and an embedding-aware wrapper that wires any vector store to the pluggable embedder.
  • Pluggable backend strategy so S3 Vectors is optional, not required.

Open-Source Principles

  • Vendor-neutral core protocol.
  • Storage adapters instead of hard-coded infrastructure.
  • Public design notes for schema, locking, and compatibility changes.
  • Small, inspectable state objects that can be pulled, reviewed, backed up, and migrated.
  • Maintainer governance that can grow into a broader community model.

Install

pip install cloudtantrix-continuum

This installs two executables:

  • continuum — the local workflow CLI (init, task-start, task-finish, search, dashboard, and more).
  • continuum-mcp — the stdio MCP server for Claude Code, Cursor, Copilot/VS Code, Codex, and other MCP clients.

Or run either without installing, via uv:

uvx --from cloudtantrix-continuum continuum init
uvx --from cloudtantrix-continuum continuum-mcp

Zero-Config Setup for Claude Code

One command configures a project end to end — no further manual steps:

continuum init --agent claude --write-agent-config

This writes everything Claude Code needs and wires it to run automatically every session:

  • .mcp.json — registers the continuum-mcp server (absolute executable path, so it works without an activated venv), merged non-destructively with any MCP servers you already have.
  • CLAUDE.md — memory-usage instructions loaded each session.
  • .claude/settings.json hooks — a SessionStart hook injects a compact memory context (project summary + recent memories) at the start of every session, and a Stop hook prevents a session from ending while a Continuum lock is still held, so learnings are always stored and locks released.

To register Continuum once for all your projects instead:

continuum install-claude-global --write

continuum --help documents the full workflow, token-savings tooling, and dashboard access.

Run as a Service

For an always-on backend that starts at boot and restarts automatically on failure:

continuum serve --host 0.0.0.0 --port 8000   # HTTP API + remote MCP, foreground
continuum install-service --write             # systemd user service (Restart=always)

Run Locally

Try the dependency-free local workflow first:

./install-local.sh

This one-command bootstrap discovers a usable Python 3.10+ interpreter, runs local init, configures Codex globally when codex is installed, and verifies the MCP server. Use ./install-local.sh --skip-codex-global if you do not want it to write ~/.codex/config.toml.

The lower-level checkout commands remain available:

./scripts/continuum.py init
./scripts/continuum.py identify
./scripts/continuum.py demo --reset
./scripts/continuum.py index-local
./scripts/continuum.py search-local "S3 Vectors adapter" --mode hybrid
./scripts/continuum.py dashboard --port 8765

A typical task cycle, with consolidation, redaction, and graph relations:

# Acquire a lock and surface relevant memory
./scripts/continuum.py task-start "Diagnose the Databricks job failure" --agent codex

# Finish: extract a summary from a raw log, record a relationship, release the lock.
# Secrets and PII are redacted automatically before anything is stored.
./scripts/continuum.py task-finish --lock-id "$LOCK_ID" \
  --raw-log-file run.log \
  --relation "job:etl-nightly:runs-on:cluster:prod-shared" \
  --path jobs/etl_nightly.py

# Replace a stale memory; the old one is invalidated, not duplicated
./scripts/continuum.py task-finish --lock-id "$LOCK_ID" \
  --summary "Cluster count is now seven" --supersedes "$OLD_EPISODE_ID"

Inspect relationships, recall quality, and savings:

./scripts/continuum.py graph-neighbors --type job --name etl-nightly --depth 2
./scripts/continuum.py graph-stats
./scripts/continuum.py metrics
./scripts/continuum.py eval-recall --cases cases.json --k 5 --mode hybrid

Seed reusable safe processes, assemble cache-friendly context, and emit schemas:

./scripts/continuum.py templates                 # list built-in procedural templates
./scripts/continuum.py install-template --all     # seed them as procedural memory
./scripts/continuum.py context "Diagnose the failure" --format anthropic
./scripts/continuum.py schemas --write docs/schemas

Local data is written under .remote-state/ by default.

Memory Intelligence

Continuum keeps run-start context small and retrieves detail only when relevant.

  • Hybrid retrieval. Recall fuses full-text (SQLite FTS5 / BM25) and vector cosine similarity with reciprocal rank fusion, so a memory surfaces if either signal ranks it highly. The default embedder is deterministic and dependency-free; sentence-transformers and OpenAI adapters are optional and loaded lazily, never required by the core.
  • Consolidation. Raw logs are distilled into compact, high-signal summaries. New memories are compared against existing ones and either added, used to supersede a near-duplicate, or skipped, which keeps recall both cheaper and more accurate over time.
  • Temporal validity. Memories and graph edges carry valid_at/invalid_at. Superseding a memory invalidates it (and the relationships it asserted) rather than deleting history, and invalidated entries are excluded from recall.
  • Knowledge graph. A dependency-free SQLite graph stores entities and relationships (modules, accounts, jobs, clusters, files) for multi-hop recall.
  • Redaction. A configurable rule set removes secrets, keys, tokens, private keys, emails, account IDs, and similar values before persistence. It is on by default.
  • Observability and evaluation. Recall and store events are recorded so metrics can report recall hit-rate and estimated tokens saved, and eval-recall measures recall@k against labelled cases.

Bind an agent during init:

./scripts/continuum.py init --agent codex --write-agent-config --dashboard

Configure Codex once for all repos:

./scripts/continuum.py install-codex-global --write

Generate AWS/S3 Vectors configuration without storing secrets:

./scripts/continuum.py init --backend aws --vector-backend s3vectors

Run the API server:

python -m venv .venv
. .venv/bin/activate
pip install -e ".[dev]"
uvicorn continuum.server.main:app --reload

Key Endpoints

  • GET /health
  • GET /projects/{project_id}/state
  • PUT /projects/{project_id}/state
  • POST /projects/{project_id}/locks
  • DELETE /projects/{project_id}/locks/{lock_id}
  • POST /projects/{project_id}/episodes
  • GET /projects/{project_id}/memories/search?q=...
  • GET /mcp and POST /mcp — remote MCP transport (JSON-RPC over HTTP)

Remote MCP for Fleets

Agents can connect over stdio locally or over HTTP for hosted/team setups. The POST /mcp endpoint speaks the same MCP protocol and tool set as the stdio server, so behavior is identical across transports. Point an agent at a running server:

# Local stdio (Claude Code, Cursor, Copilot/VS Code, generic MCP, Codex)
./scripts/continuum.py install-agent cursor --write

# Remote HTTP endpoint for a shared deployment
./scripts/continuum.py install-agent claude --remote-url https://memory.example.com/mcp --write

install-agent writes the correct config location per client (.mcp.json for Claude Code and generic MCP, .cursor/mcp.json for Cursor, .vscode/mcp.json for Copilot/VS Code, and ~/.codex/config.toml for Codex).

State writes increment serial. If the submitted lineage or serial does not match the current remote state, the API returns 409 Conflict. Use ?force=true only for manual recovery workflows after pulling and backing up the current state.

AWS Mode

Set these environment variables:

BACKEND_DRIVER=aws
AWS_REGION=us-east-1
STATE_BUCKET=my-agent-state-bucket
LOCK_TABLE=my-agent-locks

The AWS adapter stores state and memory payloads in S3 and uses DynamoDB conditional writes with TTL fields for lock acquisition.

Backend Portability

The project should run locally, on AWS, on S3-compatible object stores, on Azure, on GCP, or on Postgres. S3 Vectors is an optional vector adapter. Users who do not have it can use local keyword search, pgvector, Azure AI Search, OpenSearch, Qdrant, LanceDB, Milvus, Weaviate, or another adapter behind the same memory search contract.

Project Docs

Metadata

Release files for cloudtantrix-continuum 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cloudtantrix-continuum 0.3.0
File Size Uploaded Provenance Actions
cloudtantrix_continuum-0.3.0.tar.gz 71.3 kB With provenance Details for cloudtantrix_continuum-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cloudtantrix-continuum 0.3.0
File Interpreter ABI Platform Actions
cloudtantrix_continuum-0.3.0-py3-none-any.whl Python 3 none any Details for cloudtantrix_continuum-0.3.0-py3-none-any.whl

Total release size: 143.4 kB

Release files / cloudtantrix_continuum-0.3.0.tar.gz

Download URL cloudtantrix_continuum-0.3.0.tar.gz
Size 71.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d42aafe7ed119069d9e2b6a26e4185043bcfa21fb342eb1f6fbae3516659ceff
BLAKE2b-256 checksum
How to use checksums
6b5cad96ec8a77dcc50aa90348280dd489e65a5571aef66a619408a922237c1b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

Release files / cloudtantrix_continuum-0.3.0-py3-none-any.whl

Download URL cloudtantrix_continuum-0.3.0-py3-none-any.whl
Size 72.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cec3213c38016083abdc957272307ac7dc1d15fd572781ac9b312e35fd351932
BLAKE2b-256 checksum
How to use checksums
4d3fb20882a063922b882ba1d22a407833ab4803cf254fc1bd2c399acd396fce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

Security for cloudtantrix-continuum 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for cloudtantrix_continuum-0.3.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page