Docs

Workflow preview, end to end.

Munin is still pre-beta. The public crate is not live yet, so this page shows the workflow shape rather than a public install path.

01Private beta access

Munin is not installable from crates.io yet. We are keeping the public install path hidden until the crate exists and the release flow actually works.

Public install is pending. Join the beta list for first access, release notes, and the crates.io launch.

02Initialise a workspace

Install Munin, then run the memory ingest command when you want to refresh the local compiler from prior sessions.

$ cargo install munin-memory
$ munin memory-os ingest --format text
ok  imported local Claude/Codex sessions into Memory OS
ok  refreshed compiled memory surfaces

03Start a session with a brief

Pipe the brief straight into your agent's system prompt. Every agent gets the same startup context.

$ munin resume --format prompt
<startup_memory_brief>
project:         sitesorted
open_loops:      3 (P0: Stripe idempotency)
next_question:   Which retry window matches the refund SLA?
first_verify:    pnpm test -- src/billing/retry.spec.ts
</startup_memory_brief>

04Inspect a next-step suggestion

When the agent asks "what should I do next", Munin shows a ranked suggestion with evidence.

$ munin nudge
#1 (confidence 0.82)
  Land retry-window fix before Thursday freeze.
  evidence: 4 past sessions, 2 corrections, 1 ticket
  expected effect: closes P0 open loop, unblocks merge

05Run proactivity

Use proactivity when you want the agent to suggest the first fix before a new session starts.

$ munin proactivity schedule-install --scope sitesorted-business
ok  installed morning proactivity runner

$ munin proactivity status --scope sitesorted-business
auto_spawn:     true
pending_jobs:   1
first_fix:      refresh replay proof before cutover

06Confirm a pattern as a rule

Memory items start observe-only. Once you confirm the pattern holds, promote it. Munin attaches the evidence and enforces it via a pre-edit hook.

$ munin promote "integration tests use real Postgres"
ok  promoted to rule (freshness 0.94, stability 0.91)
ok  attached 7 supporting sessions
ok  registered pre-edit hook on test files

07Run a repeated-mistakes report

Per-agent corrections, redirect statistics, and behaviour-change recommendations. Read what each agent gets wrong most often.

$ munin friction --agent codex
redirects:   24 in last 30 days (41% on import style)
top issue:   rewrites prettier config-compliant imports
suggest:     per-agent directive enforcing repo prettier

That's the whole tour.