Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
79 commits
Select commit Hold shift + click to select a range
da5c45c
Fix duplicate numeric-ID bypass and refuse oversized discussion merges
pitfa19 Oct 20, 2026
31257b2
Add brief and plan-focused context reads across CLI and MCP
pitfa19 Oct 20, 2026
b58b9df
fix(core): guard write races and reserve inventory extensions
pitfa19 Oct 20, 2026
e18c891
Merge branch 'hermes/p0-storage' into hermes/vnext
pitfa19 Oct 20, 2026
f4ac49e
Merge branch 'hermes/context-brief' into hermes/vnext
pitfa19 Oct 20, 2026
7a79278
Add legacy SPEC banner, reads and network docs, P0 verification
pitfa19 Oct 20, 2026
7f61e53
core: add flagged read-set rebase for stale appends (concurrency.rebase)
pitfa19 Oct 20, 2026
62c6166
core: owner annotations sidecar with annotate route, deadlines from p…
pitfa19 Oct 20, 2026
a8b5638
test: V-race process tests for rebase (A0 replay, kill -9 writers, P0…
pitfa19 Oct 20, 2026
0b4a771
cli, mcp, plugin: graph, ready, plans sort by deadline, owner annotat…
pitfa19 Oct 20, 2026
6029902
Docs and skill for owner annotations, sidecar token in graph output, …
pitfa19 Oct 20, 2026
5f69f88
docs: describe the experimental concurrency.rebase setting and record…
pitfa19 Oct 20, 2026
312c106
Merge branch 'hermes/s4-annotations' into hermes/vnext
pitfa19 Oct 20, 2026
34555cf
Merge branch 'hermes/s1b-rebase' into hermes/vnext
pitfa19 Oct 20, 2026
2c8f476
Fix tests and plugin paths under a symlinked or slash-ended TMPDIR
pitfa19 Oct 20, 2026
352967e
S1c: a late supporting observation keeps an owner-accepted outcome done
pitfa19 Oct 20, 2026
6ec870d
docs: add a relative link checker with a test, and a script that repr…
pitfa19 Oct 20, 2026
fbfeb63
plugin: disclose the repo visibility check, the parent-folder invento…
pitfa19 Oct 20, 2026
97b9e06
core, cli: owner.json records host; owner recover route clears a lock…
pitfa19 Oct 20, 2026
3b94984
core: mozak.md that differs only by CRLF or trailing whitespace is cu…
pitfa19 Oct 20, 2026
1d3ce6a
Remove the old uppercase demo files from the repo; nothing links to them
pitfa19 Oct 20, 2026
4daae77
README: plain problem statement, real example, why not X, when not to…
pitfa19 Oct 20, 2026
991934c
CHANGELOG: 0.5.0 unreleased entry for the vnext line; add a DRAFT of …
pitfa19 Oct 20, 2026
c2a5837
docs: Obsidian community plugin submission checklist with status and …
pitfa19 Oct 20, 2026
bdc2cc7
Fix bridge-conflict after a revise with content keys out of schema order
pitfa19 Oct 20, 2026
1af899f
Read concurrency.rebase from the one mozak-settings.json next to the …
pitfa19 Oct 20, 2026
9bea130
docs: record launch-docs verification (full suite, installer suite, l…
pitfa19 Oct 20, 2026
a1174d9
core, cli: owner route plan prune --rejected; the receipt is the prun…
pitfa19 Oct 20, 2026
e09841c
Lead failed MCP results with a one-line reason and the issues
pitfa19 Oct 20, 2026
57a14b4
core, cli: check --history N reports commits that changed mozak.json …
pitfa19 Oct 20, 2026
f306300
core: remote reads mark remoteFreshness and skip the network for ten …
pitfa19 Oct 20, 2026
1b943e4
docs: record S1c and gap fix check results
pitfa19 Oct 20, 2026
3cf51ce
core, cli: sync of local scopes in a git repo: fetch outside the lock…
pitfa19 Oct 20, 2026
80e63ed
core: counts-only usage log per operation in .mozak-cache/usage and a…
pitfa19 Oct 20, 2026
c9b661e
test: V-race 9 clears locks of killed writers with the recover route …
pitfa19 Oct 20, 2026
35a2c78
core: reads inside a write skip the git ignore diagnostics; docs for …
pitfa19 Oct 21, 2026
e8658e5
docs: record S2 verification results
pitfa19 Oct 21, 2026
416ad37
Merge branch 'hermes/s1c-gaps' into hermes/vnext
pitfa19 Oct 21, 2026
3b8fe0d
Merge branch 'hermes/s2-hygiene' into hermes/vnext
pitfa19 Oct 21, 2026
e6d7dd2
Merge branch 'hermes/launch-docs' into hermes/vnext
pitfa19 Oct 21, 2026
02a966c
eval: S0b retrieval harness, synthetic 50-note fixture from a truth t…
pitfa19 Oct 21, 2026
458c526
eval: S7a cold-start runner, transcript token metric and paired Wilco…
pitfa19 Oct 21, 2026
ad8b5f6
core, cli: locator resolution, cited-note staleness in check, plans-m…
pitfa19 Oct 21, 2026
789e436
core, cli, mcp: similar report with template filter and labels; V-dup…
pitfa19 Oct 21, 2026
519c00a
docs, scripts: plans index, locators and similar docs; V-latency veri…
pitfa19 Oct 21, 2026
00f37ab
Merge branch 'hermes/s6-index' into hermes/vnext
pitfa19 Oct 21, 2026
7c82b1d
Merge branch 'hermes/s0b-eval' into hermes/vnext
pitfa19 Oct 21, 2026
561e198
scripts: count-loc.mjs counts non-blank lines of packages/*/src
pitfa19 Oct 21, 2026
5d09169
core: remove dead format-1 modules (parse, check, graph, stale, trans…
pitfa19 Oct 21, 2026
506b601
core: pure tend report helpers (surfaces, size budgets, 30-event wind…
pitfa19 Oct 21, 2026
e984cd9
skills: mozak-tend proposal (monthly report, surfaces, size budgets, …
pitfa19 Oct 21, 2026
97044f9
core: one realOrSelf and isWithin helper in paths.ts replaces five lo…
pitfa19 Oct 21, 2026
b842e4c
docs: S8 tend verification status
pitfa19 Oct 21, 2026
467ea5c
core: ten error messages now name the next step (stale-input, operati…
pitfa19 Oct 21, 2026
61dd05b
tsconfig: turn on noUnusedLocals, noUnusedParameters, noImplicitRetur…
pitfa19 Oct 21, 2026
a20efe3
scripts: typecheck, lint (typecheck plus Markdown link check) and loc…
pitfa19 Oct 21, 2026
27c52ee
docs: audit-2026-10.md (removed code with line counts, changes, what …
pitfa19 Oct 21, 2026
de4e346
docs: CI change is a proposal file because the branch token may not p…
pitfa19 Oct 21, 2026
313d31e
Merge branch 'hermes/audit' into hermes/vnext
pitfa19 Oct 21, 2026
e1b5190
Merge branch 'hermes/tend' into hermes/vnext
pitfa19 Oct 21, 2026
32f670b
ci: add typecheck and link check step (owner applies docs/ci-workflow…
pitfa19 Oct 21, 2026
82454b6
obsidian: sync button also fast-forwards vault repos (sync --local)
pitfa19 Oct 21, 2026
c9f96b1
Bound brief context with prioritized plans and omission counts
pitfa19 Oct 21, 2026
0472071
Fix cold-start context injection and token accounting
pitfa19 Oct 21, 2026
94d773d
Merge bounded context brief
pitfa19 Oct 21, 2026
6d005c6
Merge validated cold-start harness
pitfa19 Oct 21, 2026
04c43b4
Validate eval read results and use a lightweight demo still
pitfa19 Oct 21, 2026
f70c10a
Integrate main 0.4.4 without enabling experimental rebase
pitfa19 Oct 21, 2026
20af497
Preserve current main 0.4.5 fixes in vnext integration
pitfa19 Oct 21, 2026
7ac0291
Merge hermes/vnext-rebase-0.4.4 into release/0.5.0
pitfa19 Oct 31, 2026
e14052d
Remove the eval harness and the tend experiment from the release
pitfa19 Oct 31, 2026
6554496
Make the counts-only usage log opt-in
pitfa19 Oct 31, 2026
d684fda
Turn owner annotations off by default
pitfa19 Oct 31, 2026
59505af
Pin concurrency.rebase off by default with a write-route test
pitfa19 Oct 31, 2026
5c91f76
Delete the format-1 modules from core
pitfa19 Nov 1, 2026
e5dc7bb
Add the Focus tab: a starred-plans list in the inventory, CLI, MCP an…
pitfa19 Nov 1, 2026
28610de
Docs for 0.5.0: README, release notes, submission checklist, no agent…
pitfa19 Nov 1, 2026
9c26892
Version 0.5.0
pitfa19 Nov 1, 2026
de31afd
Record the 0.5.0 verification; old-client check turns annotations on
pitfa19 Nov 1, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,8 @@ jobs:
run: npm ci --ignore-scripts
- name: Build
run: npm run build
- name: Typecheck and Markdown link check
run: npm run lint
- name: Core, CLI and fresh MCP regression suite
run: npm test
- name: Standalone installation and failure-path checks
Expand Down
7 changes: 7 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -9,3 +9,10 @@ scratch
/MOZAK.json
/MOZAK.md
/.mozak-write-lock
# Old generated demos with the uppercase name. scripts/record-demo-video.mjs and
# scripts/record-agent-chat-video.mjs write them; regenerate them before scripts/package-demo-kit.mjs.
# The README demo lives on the readme-assets release instead.
/docs/assets/mozak-demo.gif
/docs/assets/mozak-demo.mp4
/docs/assets/mozak-agent-chat.gif
/docs/assets/mozak-agent-chat.mp4
37 changes: 28 additions & 9 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,23 +4,42 @@ User-visible changes, newest first. Releases are git tags `vX.Y.Z` on `main`; `m

## Unreleased

## 0.4.8 (not yet tagged)
## 0.5.0 (not yet tagged)

0.5.0 includes the fixes prepared as 0.4.8, which was never tagged.

**Upgrade every machine before you star a plan.** mozak before 0.5.0 refuses an inventory that has a `focus` list (`unknown key "focus"`).

### Added
- **Focus tab.** The Obsidian sidebar tabs are Open, Focus and Done; the All tab is gone and rejected plans show in no tab (`mozak plans --include-rejected` still lists them). A star on every plan row adds the plan to the scope's `focus` list in `mozak-inventory.json` or takes it out. The sidebar opens on Focus when it has plans, else Open, and remembers the last tab. `mozak focus list [--scope ID]` reads the lists, `mozak focus add|remove --scope ID --plan ID` (owner) changes them, and MCP has a read-only `mozak_focus`. Focus is a sidebar marker only: it is not plan state, `mozak.json` and `mozak.md` never change, and agents cannot write it. A starred id that is no longer a plan is a `check` warning (`focus-unknown-plan`). See [docs/installation.md](docs/installation.md#6a-focus-list).
- **Owner annotations, off by default.** Cross-plan refs (needs, informs, supersedes) and deadlines in a `mozak.annotations.json` sidecar, written only through the owner route `mozak annotate`, read by `mozak graph`, `mozak ready`, `mozak plans --sort deadline` (MCP `mozak_plan_graph`, `mozak_ready`) and the sidebar. Turn them on per scope with `scopes.<id>.annotations: true` in the `mozak-settings.json` next to the inventory. A scope without it behaves like 0.4.7: the sidecar is never read and `mozak.md` does not change. See [docs/annotations.md](docs/annotations.md).
- **Plans index, locators and similar plans.** `mozak plans-md` (owner) writes a `plans.md` with plan titles and states at each notes repo root. `mozak locators` shows where each source and evidence locator points. `check` lists cited notes that changed after they were cited. `mozak similar` (MCP `mozak_similar`) reports duplicate, overlapping and superseding plans across scopes. See [docs/plans-index.md](docs/plans-index.md).
- **Store hygiene.** The lock owner record names its host, and the owner route `mozak recover` clears a write lock left by another host or a dead local process (`check` reports `write-lock-stuck`). `mozak plan prune --rejected` (owner) removes listed rejected plans; refs to them resolve as pruned and the id cannot be proposed again. `mozak check --history N` reports hand edits to `mozak.json`. `mozak sync --local` fast-forwards git repos that hold local scopes, under the scope locks, and never pushes; the sidebar sync button does the same.
- **Experimental read-set rebase, off by default.** With `concurrency.rebase: true` in `mozak-settings.json` (top level or per scope), a stale `observe`, `save-discussion` or new-id `propose` commits onto the fresh state when nothing it read has changed. Decisions, `revise`, `complete` and `attach-spec` keep the exact snapshot check.
- **Counts-only usage log, opt-in.** With `MOZAK_USAGE_LOG=on` or `"usageLog": true` in `mozak-settings.json`, each call appends one line of counts and codes (never plan text) to `.mozak-cache/usage/` next to the inventory. Off by default.
- `npm run typecheck`, `npm run lint` (typecheck plus a relative-link check, also run in CI) and `npm run loc`. `scripts/readme-example.mjs` reproduces the README example on a throwaway scope.

### Fixed
- `propose` refuses an exact copy of a non-completed plan as `duplicate-plan-candidate` even when the plan ids carry different numbers. Before, such a copy was let through.
- A merge whose combined discussion would exceed 32 questions is refused as `merge-capacity` at propose and at approval. Before, the extra questions were silently cut.
- Writes hash `mozak.json` and `mozak.md` again right before each rename and stop with `graph-changed-during-write` when another editor changed them, keeping that edit. This covers `plan delete` too. It narrows the race with editors that ignore the write lock, it does not close it.
- `propose` refuses an exact copy of a non-completed plan as `duplicate-plan-candidate` even when the plan ids carry different numbers.
- A merge whose combined discussion would exceed 32 questions is refused as `merge-capacity` at propose and at approval, instead of silently cutting questions.
- Writes hash `mozak.json` and `mozak.md` again right before each rename and stop with `graph-changed-during-write` when another editor changed them (also for `plan delete`). It narrows the race with editors that ignore the write lock, it does not close it.
- `init` and projection repair add ignore lines for the write lock and temp files, and `check` reports `lock-not-ignored` and `lock-in-git`.
- A late supporting observation no longer drops an owner-accepted outcome from `done` to `evidence` in the roadmap, `mozak.md` and `needs` checks. Only a new challenge reopens it. `plan complete` still needs an owner acceptance bound to the exact current evidence.
- A late supporting observation no longer drops an owner-accepted outcome from `done` to `evidence`. Only a new challenge reopens it. `plan complete` still needs an owner acceptance bound to the exact current evidence.
- A `mozak.md` that differs only by CRLF line endings or trailing whitespace counts as current.
- The Obsidian plugin opens plans inside a vault that was opened through a symlink.
- The test suite passes with the default macOS `TMPDIR` and with `TMPDIR=/tmp` (scratch paths behind a symlink).
- The test suite passes with the default macOS `TMPDIR` and with `TMPDIR=/tmp`.

### Changed
- An inventory may carry a reserved `x` object at the top or in a scope entry. This client ignores it and `check` reports `inventory-x-ignored`, so a future setting does not break older clients.
- A failed MCP tool call now starts with a one-line `reason` and the `issues`, before the rest of the result. A failed `observe` echoes its `unsavedRequest` last, in the CLI JSON too. Hosts that cut long tool output still show why the call failed.
- Removed the unused format-1 modules from `@mozak/core` (`parse`, `check`, `graph`, `stale`, `translate`, `init`, `write`, `plan`) and their exports. No CLI, MCP or plugin route used them, and format-1 routes still refuse with `unsupported-legacy-operation`. See [docs/audit-2026-10.md](docs/audit-2026-10.md).
- Common error messages end with the next step (`stale-input`, `scope-not-found`, `plan-not-found`, `operation-conflict`, `busy` and others). Codes and exit codes are unchanged.
- A failed MCP tool call starts with a one-line `reason` and the `issues`, before the rest of the result.
- Local and vault-plans scope reads never fetch. Remote reads mark `remoteFreshness` and skip the network for 10 minutes after a failed fetch.
- An inventory may carry a reserved `x` object at the top or in a scope entry. This client ignores it and `check` reports `inventory-x-ignored`.
- The compiler runs with `noUnusedLocals`, `noUnusedParameters`, `noImplicitReturns`, `noFallthroughCasesInSwitch` and `noImplicitOverride`.

### Docs
- README: new "Reads and the network" section on what reads of a repo-mode GitHub scope may fetch, cache and push, and the background release check.
- README rewritten around the problem mozak solves, with a real example and the install line. New section "Reads and the network".
- The plugin README and disclosures say what the plugin writes: a stale `mozak.md` it regenerates, and the `focus` lists through the star. It never writes plan state.
- The installed skill no longer names one host's scheduler, and its examples say "the owner".

## 0.4.7 (2026-10-29)
Expand Down
63 changes: 59 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,54 @@ You work in ideas and plans, not code. Several agents share one plan without ove
[![Node 24.11+](https://img.shields.io/badge/node-24.11%2B-339933?style=flat-square)](docs/installation.md)
[![Platforms](https://img.shields.io/badge/platforms-Linux%20%7C%20macOS-blue?style=flat-square)](docs/installation.md)

[What it is](#what-it-is) · [See it run](#see-it-run) · [Install](#install) · [How it works](#how-it-works) · [Obsidian](#see-everything-in-obsidian) · [Safety](#safety) · [Tested](#what-is-tested-and-what-is-not) · [Docs](docs/installation.md)
[What it is](#the-problem) · [Example](#a-short-example) · [See it run](#see-it-run) · [Install](#install) · [How it works](#how-it-works) · [Obsidian](#see-everything-in-obsidian) · [Safety](#safety) · [Tested](#what-is-tested-and-what-is-not) · [Docs](docs/installation.md)

</div>

---

## The problem

Coding agents forget the plan between sessions, so you explain the project again. When several agents work at once, one can overwrite what another just wrote. And an agent can start building before you agreed on what to build.

mozak fixes this with plain files:

- **Every agent reads the same plan.** `mozak.json` holds it and `mozak.md` is a readable copy. You never explain the project twice.
- **Agents propose, you decide.** Agreeing on *what* to do and agreeing to *start building* are two separate yeses.
- **Stale writes are refused.** An agent that writes from an old copy gets `stale-input` and must reread. Nothing is overwritten.
- **One view across all your projects.** The Obsidian plugin shows every project's plans and progress in one sidebar, with a Focus tab for the plans you starred.

No cloud, no account, no background service.

```bash
npm install -g mozak && mozak doctor --fix
```

## A short example

Two agents read the same plan, then both propose at once. The first write lands. The second is refused because its copy is now old, so it cannot overwrite the first. This is real output: `node scripts/readme-example.mjs` reproduces it on a throwaway scope after `npm run build`.

```text
$ mozak plan propose --scope my-app --request a.json # agent A proposes
status: ok
committed: true
(exit 0)

$ mozak plan propose --scope my-app --request b.json # agent B proposes from the same, now old, snapshot
status: stale-input
committed: false
stale-input: snapshot changed; reread before submitting a new operation: take the new snapshot from context as expected and use a new operationId
(exit 3)

$ mozak plans --scope my-app # what is in the plan now
awaiting (1)
- Add dark mode [dark-mode]
review: direction approval
outcome: The app has a dark theme
```

The plan is now waiting for your yes. Agent B rereads and proposes again from the new snapshot.

## See it run

<div align="center">
Expand Down Expand Up @@ -123,7 +165,7 @@ A project with `root` is a local folder. A project with `remote` is a GitHub rep

## See everything in Obsidian

The Obsidian plugin in [`packages/obsidian`](packages/obsidian) shows every project from your inventory in the sidebar, notes and GitHub repos alike. Filter by **All**, **Open** or **Done**. Open plans show a small progress strip, one segment per outcome. Click a plan to open its section in the scope's `mozak.md`, which reads like a note: purpose, a roadmap of the outcomes with the current stop, a status table and the full plan text. The sidebar is for reading and navigating. You approve plans in your agent chat, not in Obsidian. The plugin never approves or changes a plan. It may regenerate a stale `mozak.md`, the same as `mozak render`.
The Obsidian plugin in [`packages/obsidian`](packages/obsidian) shows every project from your inventory in the sidebar, notes and GitHub repos alike. Tabs: **Open**, **Focus** (plans you starred) and **Done**. Open plans show a small progress strip, one segment per outcome. Click a plan to open its section in the scope's `mozak.md`, which reads like a note: purpose, a roadmap of the outcomes with the current stop, a status table and the full plan text. The sidebar is for reading and navigating. You approve plans in your agent chat, not in Obsidian. The plugin never approves or changes a plan and never writes plan state. It may regenerate a stale `mozak.md`, the same as `mozak render`, and the star on a plan row edits that scope's `focus` list in `mozak-inventory.json` (the same as `mozak focus add|remove`).

Install it from Obsidian: **Settings, Community plugins, Browse**, search for **mozak**, then Install and Enable ([directory page](https://community.obsidian.md/plugins/mozak)). From a source checkout you can also run:

Expand All @@ -133,7 +175,7 @@ node scripts/install-obsidian-plugin.mjs /path/to/your/vault --build

The plugin finds `mozak-inventory.json` by searching upward from the vault folder, or you can set its path in the plugin settings. Each GitHub project shows a globe or lock badge for a public or private repo.

**Plugin disclosures (desktop-only, `isDesktopOnly: true`):** When your `mozak-inventory.json` lists scopes outside the current vault, the plugin reads their `mozak.json`, `mozak.md`, `README.md` and `AGENTS.md` files from those configured paths and watches them when **Auto-refresh** is enabled. It never scans folders not listed in your inventory and never approves or changes a plan (it may regenerate a stale `mozak.md` projection when there are no unmerged hand edits). For remote GitHub scopes (`"remote": "github:owner/repo"` without vault-hosted `"plans"`), clicking **Sync remote scopes** or enabling **Repo sync interval (seconds)** runs your local `git` with your existing git login on the hidden `.mozak-cache` copy: `git fetch`, then a reset of that copy to the fetched commit. If an earlier mozak write left a plan commit unpushed (for example after a network failure), the sync first commits and pushes that pending `mozak.json` / `mozak.md` change. Set the sync interval to `0` to turn background git activity off. The sync also asks the public GitHub API, without a login and at most once a day per repo, whether each remote repo is public. The update notice only reads a cache file the CLI writes. The plugin never installs or updates itself, and has no telemetry. See [`packages/obsidian/README.md`](packages/obsidian/README.md#disclosures-obsidian-community-plugin-policy) for the full disclosure list.
**Plugin disclosures (desktop-only, `isDesktopOnly: true`):** When your `mozak-inventory.json` lists scopes outside the current vault, the plugin reads their `mozak.json`, `mozak.md`, `mozak.annotations.json` (when present and annotations are on for that scope), `README.md` and `AGENTS.md` files from those configured paths and watches them when **Auto-refresh** is enabled. It never scans folders not listed in your inventory and never approves or changes a plan (it may regenerate a stale `mozak.md` projection when there are no unmerged hand edits, and the star toggle edits the `focus` lists in `mozak-inventory.json`). For remote GitHub scopes (`"remote": "github:owner/repo"` without vault-hosted `"plans"`), clicking **Sync vaults and repos** or enabling **Repo sync interval (seconds)** runs your local `git` with your existing git login on the hidden `.mozak-cache` copy: `git fetch`, then a reset of that copy to the fetched commit. If an earlier mozak write left a plan commit unpushed (for example after a network failure), the sync first commits and pushes that pending `mozak.json` / `mozak.md` change. The button also fast-forwards local vault repositories under scope locks, without pushing or merging diverged histories. That local-vault step is not run by the background timer. Set the sync interval to `0` to turn background git activity off. The sync also asks the public GitHub API, without a login and at most once a day per repo, whether each remote repo is public. The update notice only reads a cache file the CLI writes. The plugin never installs or updates itself, and has no telemetry. See [`packages/obsidian/README.md`](packages/obsidian/README.md#disclosures-obsidian-community-plugin-policy) for the full disclosure list.

## Under the hood

Expand All @@ -157,6 +199,8 @@ The agent writes plain `mozak.json` and `mozak.md` files in your project folder.
| Run the guided planning conversation | the installed skill at `PREFIX/skills/mozak/SKILL.md` |
| Rename a project (owner) | `mozak scope retitle` |
| Delete plans so they no longer exist (owner) | `mozak plan delete --plans A,B` |
| Star or unstar a plan for the Focus tab (owner) | `mozak focus add\|remove --scope ID --plan ID`, or the star in the sidebar |
| Clear a write lock left by a dead process or another host (owner) | `mozak recover` |
| Move pre-0.4 `MOZAK.json` / `MOZAK.md` to lowercase (owner) | `mozak rename-files --all` |

Every scope command needs an explicit `--config`. Only the maintenance commands (`upgrade`, `doctor`) run without one.
Expand All @@ -175,7 +219,7 @@ Local and vault-plans scopes are read from disk. A GitHub scope whose plans live

## What is tested and what is not

**Tested.** 539 unit and integration tests plus 74 installer tests, run in CI on Ubuntu and macOS with Node 24.11 and 26 on every push to `main` and every pull request. They cover:
**Tested.** 630 unit and integration tests plus 74 installer tests, run in CI on Ubuntu and macOS with Node 24.11 and 26 on every push to `main` and every pull request. They cover:

- stale writes refused, including two real CLI processes writing at once
- a write killed mid-way recovering without losing data
Expand All @@ -194,6 +238,17 @@ The Obsidian plugin passed Obsidian's automated community review. Its build and
- **Real GitHub.** Tests use local bare repos. Real GitHub was checked by hand.
- **Unsupported setups.** Windows, network filesystems and diverged remote branches.

## New in 0.5

- **Focus tab.** Star a plan in the Obsidian sidebar to put it in Focus. `mozak focus list` shows the stars, and agents can read them but never change them. See [docs/installation.md](docs/installation.md#6a-focus-list).
- **Shorter reads.** `mozak context --brief` gives one short summary per plan, `mozak context --plan ID` the full state of one plan.
- **Owner annotations, off by default.** Links between plans (needs, informs, supersedes) and deadlines, read by `mozak graph`, `mozak ready` and `mozak plans --sort deadline`. Turn them on per scope. See [docs/annotations.md](docs/annotations.md).
- **Plans index and similar plans.** `mozak plans-md`, `mozak locators` and `mozak similar`. See [docs/plans-index.md](docs/plans-index.md). They help you navigate, they make no search-quality claim.
- **Store hygiene.** `mozak recover` clears a stuck write lock, `mozak plan prune --rejected` removes rejected plans, `mozak check --history N` finds hand edits, `mozak sync --local` fast-forwards your vaults.
- **Off unless you turn them on:** the experimental `concurrency.rebase` for parallel agents, and a counts-only usage log (`MOZAK_USAGE_LOG=on` or `"usageLog": true` in `mozak-settings.json`).

The full list is in [CHANGELOG.md](CHANGELOG.md).

## Platforms

Linux and macOS, Node 24.11 or newer.
Expand Down
Loading
Loading