A live context engine for AI coding assistants. Perseus resolves your
environment before the context window opens — directives like
@query "git log -5"
are rendered to facts at build time, so the assistant reads a document
that was already true. Works with any tool that reads a file.
Works with any assistant that reads a file — Claude Code, Cursor, Codex, Rovo Dev, Hermes, or your own. No plugin. No SDK. Drop a rendered markdown file where your assistant already looks.
pip install perseus-ctx && perseus quickstart
That's the whole install. Perseus auto-detects your project language, scaffolds context-appropriate memory queries, and renders live state — one command, zero orientation.
you deploy the api service to staging. ai running `make deploy-staging`... ai Makefile target removed in #482. Let me check the current scripts. ai Which branch are you on? Is the helm chart still at v0.3? What’s the staging cluster name?
Sessions start cold. Tooling drifts. Docs lie politely. Every conversation pays an orientation tax before the real work begins — and the assistant is staring straight at the Gorgon.
you deploy the api service to staging. ai You’re on feat/billing-v2, helm chart v0.4.1, staging = eu-west-2/stg-a. ai Running `./scripts/deploy.sh staging api`. ai ✓ Image pushed. ✓ Helm upgrade applied.
Perseus renders directives to live facts before the assistant reads the file. No guessing, no probing, no trusting yesterday’s notes. The mirror, polished.
The principle The assistant never sees a directive. It sees a document that was already true.
Resolves @query, @read, @waypoint, @services and friends before the assistant sees them. The output is plain markdown. No directives left for the model to chase. --tier 1|2|3 for progressive context disclosure.
Write a checkpoint at any natural pause; perseus recover finds the right one for your workspace; perseus diff shows what changed between two pauses. Continuity, without re-orientation.
Given a task and the current environment, Pythia surfaces the highest-utility skill or tool and tells you why. No extra model required. The loop closes inside the same context window.
One file · one render · every assistant reads the same live truth
One mimir.db — SQLite with FTS5. Drop it on Syncthing, Dropbox, or a NAS. Every Hermes instance on every machine reads from the same vault.
BM25 over FTS5 with porter stemming. 0.09ms cold, 0.12ms warm query P50 at 75 records — flat across scale. No embedding model, no API calls, no cloud.
MCP-native. Run mimir as a sidecar, point all your agents at it. Same memories, same projects, same context — regardless of which machine you're on.
curl -sSL https://raw.githubusercontent.com/tcconnally/mimir/main/scripts/bootstrap.sh | bash
# Start the MCP server
mimir --db ~/.mimir/data/mimir.db
# In your Perseus config:
# memory:
# mimir_command: mimir
# mimir_db: ~/.mimir/data/mimir.db
Perseus renders the context. Mimir remembers it.
30 developers × 4 agents each. 150 concurrent checkpoint writes in 9.7s on local NVMe with atomic O_CREAT | O_EXCL locking. Writes hit the task board (tasks/*.md) with zero failures, zero collisions — protocol tested across edge cases: crash recovery, stale claims, TTL expiry.
450× cold→warm · 1,190× cache punch · 301× vs LLM · 94% token compression · 0 failures at 150 concurrent · 1,032 tests all green · full benchmark suite ↗
Perseus outputs plain markdown. Point the output at whatever file your assistant opens at session start — no plugin, no SDK, no migration. The next session opens warm.
Render-time macros resolved to static facts before the context window opens.
@cache ttl=N. For git branch, clusters, and versions.
The standalone binary commands you and your cron watchdogs run.
--tier 1|2|3 filters prompt injection size.
recover and diff restore and compare states.
Bridge triggers that automate context rendering in your native tools.
30 CLI verbs · 25 directives · 24 MCP tools — see the full catalog on GitHub ↗
perseus quickstart detects your assistant, scaffolds a workspace, and renders live context in a single command. Or give your AI our LLM-tuned setup guide and say “set up Perseus for me.” Your assistant opens its next session already briefed.
pip install perseus-ctx
uv tool install perseus-ctx
perseus quickstart
perseus init --profile hermes /workspace/myproject
perseus doctor
After setup → perseus doctor verifies everything is wired correctly.