Drew Butler.
← Projects

mimir

active · TypeScript · MIT

Local work state, with the next action derived from the facts.

View on GitHubChangelogReleases
terminal shell 
mimir overview     # current direction and active work
mimir next         # ready tasks, in rank order
mimir list         # the live work queue
Surfaces
CLI · MCP · HTTP · console
Store
Norn-managed Markdown
Scope
Single operator

Mimir keeps projects, tasks, dependencies, decisions, and work products in a Norn-managed, git-backed Markdown vault. The CLI, MCP server, HTTP API, and operator console share the same work model.

Why it exists

Long-running work needs a reliable answer to what is active, what is blocked, and what comes next. Mimir gives those questions a structured model while keeping the underlying records inspectable as Markdown.

What it does

  • Organizes projects, initiatives, phases, and tasks.
  • Derives queues, status rollups, and blockers when queried.
  • Preserves work products as Artifacts and temporary context as Scratchpads.
  • Tracks new ideas and cross-project requests as Seeds.
  • Gives agents session context and operators a console across projects.

Store facts, derive the view

Markdown is the system of record. Norn owns validated access to the vault. Mimir derives what is ready, awaiting, or stale from the stored facts, so there is no second project-status record to synchronize.