Perseus

What you get Live context before the first turn — render verified workspace facts instead of making an assistant rediscover them. One source, any assistant — write .perseus/context.md once and render to .hermes.md, AGENTS.md, CLAUDE.md, .cursorrules, or another assistant context file. Local-first by default — the core renderer reads your workspace locally; no account or hosted service is required. MCP-native when you need it — expose the same live context as a stdio or SSE MCP server, with shell-executing tools opt-in. Context, memory, and session terms Perseus resolves and shapes the active working context; Perseus Vault owns durable-memory persistence and recall.

Active working context is the current, task-relevant workspace state — files, services, tasks, and other facts that can change. Perseus resolves and shapes it at render time before the assistant sees it. Durable memory is information intended to survive session boundaries. Perseus Vault owns its persistence and recall. Recalled memory is the subset of durable memory returned for a query and shaped into the rendered context. The public @memory directive remains the compatibility API name for Vault-backed recall; existing MCP compatibility names remain unchanged. Session history is Perseus's recent checkpoint and session-digest record. @waypoint and @session expose it; it is distinct from durable memory. An explicit capture may persist a checkpoint in Perseus Vault as durable memory.