Practical overview
When it fits
Use Continuum when coding-agent conversations need persistent shared project knowledge or when parallel agent work benefits from dispatch records and reserved-path tracking.
Who it is for
- Developers using MCP-speaking coding-agent clients across multiple chats.
- Teams that want to preserve project lessons and conventions between agent sessions.
- People coordinating parallel coding tasks and tracking dispatch status or reserved paths.
Documented uses
- Store project lessons so coding agents can retrieve them across conversations.
- Search for relevant knowledge and fetch the full lesson when needed.
- Record agent dispatches and inspect their status, branches and reserved paths.
- Create a handoff prompt for a fresh agent working in an isolated Git worktree.
- Browse projects, agents, workflow instructions and knowledge in a web panel.
Requirements & limits
The repository documents local Docker Compose and bare-metal development setups. Bare-metal startup requires Node 22.12.0 or later and pnpm 10.33 or later; the Compose path skips these host prerequisites.
- The default embedding model runs in-process; configuring an external HTTP embedder is an alternative.
- Fundamental lessons are loaded for every dispatch, while situational lessons are retrieved by semantic search.
- The registry tracks reserved paths and dispatch state to surface possible collisions between parallel agents.
- Dispatch produces a prompt for a fresh agent; the README describes a human copying it into that agent.
- The web panel is for browsing project information, while MCP clients drive the orchestration workflow.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start Continuum with Docker Compose
Launch the documented development stack, including the MCP API and web panel.
Before you start
- Docker Compose
- The Continuum repository
Steps
From the repository, run the command below.
docker compose -f docker-compose.dev.yml upUse the API at
http://localhost:6685and its Swagger documentation at/docs.Open the web panel at
http://localhost:6680.
Expected outcome
The development stack starts with the API, web panel and SQLite browser; the in-process embedder is used by default.
Guide limitations
- This is the documented development Compose setup, not a production deployment recipe.
- The optional TEI embedder profile requires an HF_TOKEN.
Run the development stack on the host
Install dependencies and start the API and web panel using the documented bare-metal commands.
Before you start
- Node 22.12.0 or later
- pnpm 10.33 or later
- The Continuum repository
Steps
Run
pnpm installfrom the repository.Run
pnpm devto start the API and web panel in watch mode.Open the API at
http://localhost:7776and the panel athttp://localhost:7777.
Expected outcome
The development API and web panel run locally; the development SQLite database is stored at `./.local-data/orchestrator.db`.
Guide limitations
- These instructions describe development startup, not production deployment.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Continuum — pouyahasanamreji | Store project lessons so coding agents can retrieve them across conversations. | CLI, Self-hosted, Server | The repository documents local Docker Compose and bare-metal development setups. Bare-metal startup requires Node 22.12.0 or later and pnpm 10.33 or later; the Compose path skips these host prerequisites. |
| Haft | Record the problem a project is solving and the options considered. | CLI, Self-hosted | |
| Contextatlas | Index a repository and find relevant implementation details using a natural-language question. | CLI, Server | The project is open source under the MIT license. Its documented requirements include Node.js 20 or later and embedding and reranking API credentials and settings. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- pouyahasanamreji/continuum · Official homepage title · retained in its source language

