Installation & setup

Runtime continuity for AI-assisted development—Contorium VSIX plus MCP for Codex, Claude Code, and agents.

Install the extension

IDE extensions

MCP / agent runtime

  1. Install from a store or VSIX Use the links above, or build with npm run vsix from source (Extensions → Install from VSIX…).
  2. Open your project Contorium begins scanning workspace activity—edits, focus, and Git events—into .contora/.
  3. Set your focus (optional) Tell Contorium what you are working on; memory builders rank files and summaries around that intent.
  4. Work normally Memory updates continuously. Export context for agents or restore sessions when you return.

Connect via MCP (Codex & Claude Code)

Portable entry bin/contorium-mcp-launch.cjs works alongside the extension—install the VSIX first so .contora/state.json is populated.

Codex setup Claude Code Build MCP docs/MCP.md

Cursor Agent MCP — detailed docs coming soon on the MCP page.

Build from source

Clone the repository, install dependencies, and compile the extension.

git clone https://github.com/ContoriumLabs/contorium.git
cd contorium
npm install
npm run compile

Press F5 in VS Code to launch Extension Development Host. Package a VSIX with npm run vsix for manual install (Extensions → Install from VSIX…).

Optional: BYOK

Contorium is local-first. For semantic analysis you can optionally provide your own API keys (OpenAI, Claude, Gemini, DeepSeek)—stored in the editor secret store, not settings JSON.

  • No hidden cloud memory
  • Workspace-owned .contora/ data
  • Keys never committed to the repo

Verify it works

  • Check that .contora/state.json appears after editing files
  • Set a focus and confirm ranked files update in memory
  • Export context via sidebar (exportFormat: markdown, json, cursor, claude, openai)—or call MCP get_workspace_context
  • Restart the IDE and use session restore to pick up where you left off

Ready to give your agents memory?

Install extension Codex MCP