Cortex

Quick Start

Get to the first memory moment before learning daemon internals.

1. Install or build Cortex

Use the latest desktop installer, or build the 0.6.0 source CLI:

git clone https://github.com/AdityaVG13/cortex.git
cd cortex
cargo build -p cortex-daemon --release

2. Start local memory

Open Cortex Control Center and start Cortex from the app. CLI-only users can run:

cortex serve

3. Check readiness

cortex status --json

Success is "status": "ready". If status is needs_action or error, follow the returned nextAction / repair before continuing.

4. Connect one AI tool

Claude Code:

claude plugin marketplace add AdityaVG13/cortex
claude plugin install cortex@cortex-marketplace

Codex:

codex mcp add cortex -- cortex.exe mcp --agent codex

Restart the AI tool after changing MCP config.

5. Store and recall one memory

From a connected MCP client, call cortex_store, then cortex_recall. From the repo, run the matching smoke script:

Windows:

powershell -ExecutionPolicy Bypass -File scripts\first-run-smoke.ps1

macOS / Linux:

bash tests/scripts/first-run-smoke.sh

That smoke checks status, stores one disposable local memory, and recalls it. Normal use does not require benchmark adapters, provider keys, or LongMemEval.

More tool-specific setup: Info/connecting.md.

POST /store

Save decisions, lessons, preferences. Conflict detection is automatic.

GET /recall

Clock-Quorum Recall: admit a stored row when a hard anchor matches, two clocks agree, or a strong lexical hit holds. Empty is a valid answer. Use /as-of for an explicit validity time.

GET /boot

Extractive identity + delta + current-truth pack. ~300 tokens served instead of ~15,000 raw. No summarizer.

Accessibility and settings

• Settings panel: Accessibility, Appearance & Motion, Connection, Budgets, and Keyboard & Navigation

• Runtime preferences: high contrast, reduced motion, keyboard hints, and compact navigation

• Accessibility gates: stronger focus states, ARIA/live regions, contrast checks, and 375px reflow checks

Governance

• Retention classes across store, MCP, OpenAPI, export, and import

• Local endpoint budgets with stable HTTP 429 / JSON-RPC denial metadata

• Budget UI in Control Center, backed by the local budgets.toml

• Boot audits plus GET /boot/audit and the read-only cortex_boot_audit MCP tool

• Admin rollback with dry-run/apply workflow and audit events

Recall quality

• cortex-http-pure adapter as the canonical helper-free measurement floor

• Purity gates, CAS-100, and triangle judge tooling for safer quality claims

• Clock-Quorum Recall: deterministic evidence from write, truth, task, and history clocks. No local embedding or reranker model.

Reliability

• Claude plugin MCP is attach-only and no longer starts a second daemon from plugin MCP paths

• Control Center supervises the app-managed daemon and honors intentional stops

• Handler panics return JSON 500 responses, with local panic breadcrumbs

• Storage hygiene compacts FTS and keeps legacy embedding rows inert

Multi-agent, one brain

• Each boot call registers a session. Control Center shows active sessions, deduplicated by agent identity.

• Read-path tools (recall, peek, unfold) reattach to existing sessions. No duplicates.

• Session descriptions preserved across reconnects and daemon restarts.

• What one agent stores, every other agent can recall.

Claude Code, Codex, Cursor, and custom scripts can all be connected simultaneously. Each tracks its own session while sharing the same memory.

git clone https://github.com/AdityaVG13/cortex.git
cd cortex
cargo build -p cortex-daemon --release

claude plugin marketplace add AdityaVG13/cortex
claude plugin install cortex@cortex-marketplace

cortex status --json

Windows:

powershell -ExecutionPolicy Bypass -File scripts\first-run-smoke.ps1

macOS / Linux:

bash tests/scripts/first-run-smoke.sh

# Daemon contract tests
cargo test -p cortex-tests

# Desktop test suite
npm --prefix desktop/cortex-control-center test

# Lifecycle smoke test
npm --prefix desktop/cortex-control-center run verify:lifecycle:dev

# Security audit
npm audit --omit=dev --audit-level=high
cargo audit