Skip to content

Contitext 0.6.0

Choose a tag to compare

@jessysw jessysw released this 17 Nov 23:27
· 4 commits to main since this release
bf72028

Contitext 0.6.0 makes the project continuity service independently usable through two installation paths: a native Python package with PostgreSQL, or the public Docker Compose stack.

New operator workflow

  • Initialize a private configuration with your own project, fresh credentials, and an owner identity.
  • Create and inspect projects, provision principals, and grant or revoke project access from the CLI.
  • Run read-only diagnostics and generate native, Docker, or SSH MCP client configuration.
  • Use native stdio MCP directly, without starting REST.
  • Follow complete English installation, administration, client setup, backup/recovery, and migration guides.

Integrity and recovery

Event and handoff writes now require a matching persisted conversation binding, checked atomically with insertion. Compose startup no longer reapplies seed grants to an established database. Explicit legacy Markdown marker support prevents duplication during recovery replay while preserving curated content.

Upgrade notes

There is no database schema change, and the six MCP tool schemas remain unchanged. Unbound or mismatched writes now return HTTP 409 / an MCP tool error. Bind explicitly before writing or retrying after switching projects. Token changes still require process restarts; ACL changes do not. Existing deployments are not migrated automatically.

Installation

Native: python -m pip install contitext==0.6.0 in a virtual environment, with PostgreSQL 16+.

Docker Compose: clone the v0.6.0 tag and follow the installation guide.

Validated with 86 tests on Python 3.11–3.14, a Python 3.14 dependency-floor job, installed-wheel and real Compose/MCP acceptance, and isolated database/Markdown recovery rehearsals.

License: Apache-2.0. MCP Registry name: io.github.jessysw/contitext.