State Machines. Swarms. Verification.

No. The capture hook, the memory file, the tray app and trace notes all run on your machine; the memory is a plain file in your repository. The only network feature is strictly opt-in: anonymous usage counts — never code, never conversations. npx praxis-memory telemetry show prints the exact payload, and off wipes even the anonymous install id.

Durable decisions, not transcripts — the architecture you settled on, the constraints you discovered, the approaches you tried and reverted, and the reasons behind them. Each session also logs the commits it made and the AI's own closing summary, automatically. And nothing is ever lost: when the working memory hits its size cap, older entries rotate into .praxis/archive/ — one file per month, forever — instead of being deleted.

Praxis maintains the memory automatically. A Claude Code Stop hook distills each session's decisions into .praxis/memory.md, keeps it redacted and size-capped, and links it from CLAUDE.md so it loads on every open. Hand-written notes rot; the loop doesn't.

The whole loop — capture, memory, sealing receipts, verifying them offline — makes no API calls of its own and adds nothing to your bill. Exactly one thing ever spends tokens, and only when you ask for it: the judge (receipt --verify, or the live demo), which makes one real model call and says so before it starts.

That the record is unaltered since it was sealed — every line hash-chains to the last, and an Ed25519 signature covers the chain, checkable offline on any machine because the public key travels inside the file. It is tamper-evident, not third-party notarised: it proves the record wasn't changed, not who sealed it. And the evidence obeys one iron rule everywhere: the presence of a command proves it was attempted — never that it succeeded. Demo receipts carry a sealed demo provenance mark, so they can never be passed off as real work.

The judge rules only what the evidence supports — TRUE, FALSE, or the honest UNVERIFIABLE — and it runs as a separate process that gets the sealed record, not the AI's self-report. Seven iron-rule scenarios hold it to a floor of zero false accusations — including one where the correct answer is admitting it cannot tell — and they run in CI on every push against a recorded judge, or against a live model on demand. A judge that can't rule returns no verdict; one is never invented.

Yes. The memory file is gitignored by default, but committing it turns project memory into shared team context — every teammate's Claude opens with the same knowledge of the codebase and its history.

Claude Code is measured deeply today. npx praxis-memory switch already packs your context and hands it to Gemini CLI, Codex, Cursor or Antigravity, and trace notes work on any git host. The memory stays one portable markdown file, readable by any editor or agent.

Yes — the same single command everywhere: npx praxis-memory. The only requirement is Node 22+, which is what package.json declares, so npm will tell you plainly if your Node is older.

Three usual causes. Run the setup first (npx praxis-memory in your project). If a Claude Code session was already open during setup, restart it — the / menu loads at session start. And setup installs the commands both in the project and user-wide (~/.claude/commands), so after one setup they appear in every project.

Yes — on Windows, since v0.2: it starts by itself with setup, and npx praxis-memory tray brings the axolotl back any time, changing emotion with your session's real state (--stop to quit). macOS and Linux builds are next; npx praxis-memory status gives the same health readout everywhere meanwhile.

Praxis implements a native Directed Acyclic Graph (DAG) state machine using Kahn's algorithm directly in pure JavaScript. Dependent nodes wait for upstream resolution while independent tasks run concurrently in isolated sandboxes. Upfront cycle validation and node isolation execute in under 2ms for 1,000 nodes, eliminating the latency, runtime complexity, and heavy dependencies of external frameworks.

Zero external databases. Instead of slow cloud vector stores (like Pinecone or Supabase) that require network roundtrips and token embeddings, Praxis runs a local, zero-dependency BM25 index directly on disk over .praxis/memory.md. It indexes architectural decisions and constraints with exponential recency decay, returning ranked context in 0.26ms offline.

Instead of unreliable LLM-as-a-judge prompts grading unstructured prose, praxis eval measures agent fidelity against cryptographically sealed, Ed25519-signed session receipts. If an agent claims it wrote code, edited files, or passed tests, the harness verifies the exact filesystem cryptographic hash chain offline. No model tokens, zero network, 100% deterministic.

No — you just don't have the optional global install. npx praxis-memory is the full product: setup, hooks, tray, every command as npx praxis-memory <command>. The short praxis <command> form only exists after npm install -g praxis-memory. Praxis's own hooks run through npx, so auto-capture and the tray work either way.