About this project
MOZAK is a Git-native memory system for long-running research topics and code repositories, aimed at AI-assisted work. Its stated problem is context loss: agents repeat research, forget decisions, rebuild plans, or start work another session already handled. MOZAK keeps the durable parts in Git so every person and agent working from the repository sees the same project state.
What it records, according to the README:
- Improvement plans derived from new papers, tools and completed work, which the user reviews and approves.
- Goals, evidence, decisions, progress and rejected options, retained across sessions.
- Reusable concepts that can be moved between repositories, but only after their assumptions are re-checked in the target project.
Workflow and interface
MOZAK ships as a command-line tool. Installation is a shell script:
curl -fsSL https://raw.githubusercontent.com/pitfa19/mozak/main/scripts/install.sh | bash
mozak setup check "$HOME"
After that, a project is initialized and inspected with `mozak project init .` and `mozak project overview .`, and work is requested from a coding agent in natural language (for example, asking MOZAK to plan the next improvement and show what is ready). Research topics without code are also supported, and a 5-minute quickstart is referenced for that path. The README frames MOZAK as proposing while the user approves, and suggests pairing it with an ambient agent to run the improvement cycle periodically.
Modules
Six modules are named: `scope` (topics and projects), `research` (evidence), `plans` (goals and progress), `meta-kb` (connections between repositories), `improve-lab` (upgrade proposals), and `skill` (lets agents operate MOZAK on the user's behalf).
Reported example
The README describes one case: a reusable publishing concept was moved between two repositories; MOZAK checked five assumptions in the target, found one held, two needed replacement and two were rejected, so the idea transferred without treating both projects as identical. It also states that MOZAK has recorded its own development and produced six improvement proposals, explicitly labelled as a real self-study rather than a controlled comparison. Details of the case and concept model are in `docs/ARCHITECTURE.md`.
Implementation and licensing
MOZAK is written in Rust, presented as a fast, portable, offline binary with no language runtime, where type and memory safety help protect deterministic project state; the README notes Rust is how it ships reliably, not the reason to use it. Documentation links cover quickstart, architecture, commands and install/update under `docs/`. It is MIT licensed, with influences and prior work credited in `ACKNOWLEDGMENTS.md`.
Comments
0 Rating appears after 10 ratings
Sign in to join the discussion.