Contitext
Project continuity for AI agents.
Keep project state, decisions, checkpoints, and handoffs available across agents, sessions, and machines. Contitext is a small, self-hosted Python service backed by PostgreSQL, with REST and eight MCP tools. No LLM API key or embedding service is required.
An agent finishes a session by recording what changed and what comes next. Another agent explicitly selects the same project, reads that context, and continues from the recorded handoff.
v0.7.0 adds project discovery and creation directly in agent chats. Initialize your own projects, manage access, connect agents, and preserve context across sessions. Companion integrations and broader memory features are on the roadmap.
Installation options
Both options run the same Contitext implementation and expose the same eight MCP tools. Neither requires a private repository or a paid service.
| Option | Requirements | Operation |
|---|---|---|
| Python package | Standard CPython 3.11–3.14 and your PostgreSQL 16+ database | Install contitext==0.7.0 from PyPI; run native stdio MCP and optionally REST |
| Docker Compose | Docker with Compose, Git, and Python 3.11–3.14 for bootstrap | Build the pinned release; Compose runs Contitext and PostgreSQL together |
Use the installation guide
for either path. Python installation does not require Docker. The database is
required in both cases; Contitext is not a standalone in-memory or SQLite store.
A native MCP client can launch contitext mcp directly without a REST process.
Docker Compose quick start
Requires Docker with Compose, Git, and standard CPython 3.11–3.14.
git clone --branch v0.7.0 --depth 1 https://github.com/jessysw/contitext.git
cd contitext
python3 scripts/bootstrap.py
docker compose up --build -d --wait
curl --fail http://127.0.0.1:18791/health/ready
docker compose exec -T app python -m contitext.demo
The bootstrap script creates fresh local credentials in a private .env, seeds a
demo project, and preserves existing configuration. The demo writes synthetic
events to that project and demonstrates two agents handing work over through
the real HTTP API. Its final output includes:
{
"agent_b_resumed": "demo",
"next_action": "Implement and test the first endpoint.",
"idempotent_retry": "passed"
}
The API listens on localhost. PostgreSQL has no published host port. Data persists
in a Compose volume; docker compose down stops the service and preserves it.
See installation for Python-package setup, administration,
backup, and remote access.
For a real project, use python3 scripts/bootstrap.py --project research --name "Research"
and skip the synthetic demo. The self-hosting workflow
covers project creation, access management, client setup, and backup recovery.
These commands are included in both the PyPI package and the Compose release.
Connect an MCP client
The MCP Registry identifier is io.github.jessysw/contitext. The
Registry setup guide
explains the PyPI/stdio installation and required database configuration.
After the quick start, add this server to a client that supports stdio MCP. Replace the directory with your own absolute checkout path:
{
"mcpServers": {
"contitext": {
"command": "docker",
"args": ["compose", "--project-directory", "/absolute/path/to/contitext", "exec", "-T", "app", "contitext", "mcp"]
}
}
}
Client configuration formats differ. The same command can be used by any stdio MCP client. Load the agent protocol into the client's instruction mechanism and restart its MCP session. This release does not automatically modify your agent settings. The MCP server runs locally inside the existing app container and shares its database.
| Tool | Purpose |
|---|---|
project_bind |
Explicitly select a project for a caller's conversation scope |
project_current |
Read that scope's current project |
context_get |
Get a bounded project overview, checkpoint, questions, decisions, and handoff |
context_record |
Append a note, decision, question, or checkpoint with provenance |
context_handoff |
Record completed work, current work, blockers, and the next action |
context_search |
Search project events using PostgreSQL full-text search |
No project is inferred from the working directory or repository name. Each caller uses a stable conversation scope and explicitly selects a project. Project ACLs are enforced on the server. API contracts and limits describe what the server enforces and what the agent protocol requires.
Commands
Terminal commands use the contitext executable:
contitext --help
contitext --version
contitext init --project research --name "Research"
contitext project list
contitext doctor
contitext migrate
contitext admin seed
contitext serve --host 127.0.0.1 --port 18791
contitext mcp
Use the agent adapter installer to configure your clients with backups and a shared protocol. After installation, use these chat instructions in a conversation with the agent:
!! contitext list
!! contitext create my-project --name "My Project"
!! contitext use my-project
!! contitext status
!! contitext search publishing
!! contitext checkpoint Documented the publishing workflow.
!! contitext is the canonical chat prefix. !! ctx is a shortcut, and
!! context remains a legacy alias. These are agent instructions, not terminal
subcommands. The terminal CLI currently runs and administers the service; it does
not implement chat actions such as use, status, or search, and it does not
set a global default project. See the command reference for
CLI options, compatibility entry points, and conversation scope behavior.
What it includes
- Private initialization, project and permission administration, diagnostics, and portable native/Docker/SSH MCP client configuration.
- Project discovery filtered by caller access, and atomic creation owned by the authenticated caller without an owner UUID or implicit conversation switch.
- Atomic validation that every event or handoff write matches the caller's conversation binding.
- A durable, append-only event store with caller identity and source provenance.
- Reader, writer, and owner project ACLs shared by REST and MCP.
- Idempotent retries; conflicting reuse of an event key is rejected.
- PostgreSQL full-text retrieval with pagination, without an embedding dependency.
- Optional Markdown projection for local inspection and note-taking tools.
- Synthetic tests for isolation, concurrency, restart recovery, projection, and real MCP stdio calls.
Use Contitext when you need explicit project continuity across tools and machines. It does not automatically capture every conversation, consolidate memories, build a knowledge graph, or decide which facts are true. A project handoff is the latest handoff for the whole project, not a task scheduler or a conflict-resolution system.
Development
See CONTRIBUTING.md for the isolated PostgreSQL test setup. See SECURITY.md for trust boundaries and vulnerability reporting. Repository: jessysw/contitext.
License
Metadata
Release files for contitext 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| contitext-0.7.0.tar.gz | 92.2 kB | With provenance | Details for contitext-0.7.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| contitext-0.7.0-py3-none-any.whl | Python 3 | none | any | Details for contitext-0.7.0-py3-none-any.whl |
Total release size: 134.8 kB
Release files / contitext-0.7.0.tar.gz
| Download URL | contitext-0.7.0.tar.gz |
|---|---|
| Size | 92.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b817f3d77b8e6f3da11b2a2342bcb827a6a7d2f05154850a40fbbd07ad53c441
|
|
BLAKE2b-256 checksum How to use checksums |
4c93d12c006baec3d7590ff4baf1a62a98364875dce2016136c1f3b86b3e9e4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 18, 2026.
Transparency logRelease files / contitext-0.7.0-py3-none-any.whl
| Download URL | contitext-0.7.0-py3-none-any.whl |
|---|---|
| Size | 42.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
932b7d42b7122579c442dcc81c25ba46c7ceb9474165d4d8310ef4c5b19e1a00
|
|
BLAKE2b-256 checksum How to use checksums |
e67961c7175f5b210bd52ce298ecb6bec386dec31d40e73e665517eac77d3f88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 18, 2026.
Transparency logSecurity for contitext 0.7.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.
Attestation for contitext-0.7.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 Nov 18, 2026.
Transparency logA 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.