@gigaflow/gmux 0.15.0 → 0.16.0

package/CHANGELOG.md

@@ -4,6 +4,36 @@ Notable changes, newest first. Versions follow [semver](https://semver.org): whi
 0.x, a **minor** bump means behavior changed in a way you should read about before
 upgrading, and a **patch** is a fix that asks nothing of you.
 
+## 0.16.0
+
+### Cockpit prompt, work report, and an onboarding path that actually lands
+
+The ctrl-g grid now takes plain English at the bottom. Type an intent: a
+question is broadcast to every visible session and answered inline; a layout
+request ("group these by project") is planned, previewed, and applied only on
+confirm. `ctrl-v` writes a per-session HTML work report and shows a `file://`
+link. `gmux organize` is the same planner from the shell (dry-run default,
+`--apply` to run it).
+
+The documented first-run path now works on Oh My Tmux. `gmux tmux install` (and
+the setup wizard's bindings prompt) write to `~/.tmux.conf.local` when the live
+conf sources it, never through Oh My Tmux's git-managed `~/.tmux.conf` symlink.
+A leftover `# >>> gigamanage >>>` block is stripped so ctrl-g opens the cockpit
+instead of `gm overlay`. Vanilla tmux and a dotfiles-repo symlink of
+`~/.tmux.conf` still write through to that file. `gmux doctor` reports both.
+
+**Upgrading from gigamanage / 0.15.0:**
+
+```bash
+npm uninstall -g gigamanage          # if the old `gm` command is still around
+npm install -g @gigaflow/gmux
+gmux setup                           # provider, guardian, tmux bindings
+tmux source-file ~/.tmux.conf
+gmux daemon
+```
+
+The package publishes as `@gigaflow/gmux` (not `@gigaflowai/gmux`).
+
 ## 0.15.0
 
 ### Always-on workspace awareness — daemon, cockpit, memory guardian
@@ -73,8 +103,8 @@ goes from here.
 ### Summaries follow the pane, even after you move panes around
 
 When several panes share a directory and their agents were started fresh
-(`claude --model=…`, no `--resume <id>`), gigamanage had nothing to tell the panes
-apart — no session id on the command line, no `gm run` link — so it handed out the
+(`claude --model=…`, no `--resume <id>`), gmux had nothing to tell the panes
+apart — no session id on the command line, no `gmux run` link — so it handed out the
 newest sessions in the directory in pane-list order. Move a pane, or let a session
 update, and the summaries reshuffled onto the wrong cards.
 
@@ -82,7 +112,7 @@ The overlay now pairs those panes to sessions by **process start order**: within
 directory, the oldest agent process takes the oldest-started session, and so on.
 A process's start time is stable and belongs to the pane's real process, so the
 mapping holds when you move, swap, or join panes. A directory with a single agent
-is unchanged. Exact matches — a `--resume <id>` on the command line, or a `gm run`
+is unchanged. Exact matches — a `--resume <id>` on the command line, or a `gmux run`
 link — still win outright.
 
 ## 0.13.5
@@ -98,7 +128,7 @@ the overlay stayed up. Esc still closes; the ask-box hint now reads `^G/Esc clos
 
 ### Codex summaries work again after an upgrade
 
-A config written by an older `gm` froze the codex command as `codex exec`. When
+A config written by an older `gmux` froze the codex command as `codex exec`. When
 the catalog later gained `--skip-git-repo-check` (so codex can summarize outside a
 trusted git checkout), that flag never reached an existing config: summary
 resolution replayed the stored command verbatim, so every codex summary failed
@@ -106,8 +136,8 @@ with *"Not inside a trusted directory and --skip-git-repo-check was not
 specified"* and the `ctrl-g` overlay stayed stuck on "no summary yet".
 
 A **known** provider now re-derives its argv from the catalog rather than the
-command frozen at setup time — the same self-healing `gm ask` already had. A
-`custom` provider is still run exactly as you wrote it. No re-run of `gm setup`
+command frozen at setup time — the same self-healing `gmux ask` already had. A
+`custom` provider is still run exactly as you wrote it. No re-run of `gmux setup`
 needed; upgrade and codex summaries resume.
 
 ## 0.13.3
@@ -128,9 +158,9 @@ one.
 
 - **Force refresh:** press **ctrl-r** in the `ctrl-g` overlay to regenerate the
   visible panes' summaries now, ignoring the divergence gate. From the shell:
-  `gm summarize <id> --force`, `gm summarize --recent 20 --force`, or
-  `gm summarize --all --force`.
-- **Cross-window fix:** the overlay (and `gm ask --window`) used to resolve only
+  `gmux summarize <id> --force`, `gmux summarize --recent 20 --force`, or
+  `gmux summarize --all --force`.
+- **Cross-window fix:** the overlay (and `gmux ask --window`) used to resolve only
   the current window's panes, so a fresh agent with no session id on its command
   line could grab the session another window's pane already owns — making two
   panes show the same summary. They now resolve every pane in the server and keep
@@ -171,10 +201,10 @@ separate chat" with an integrated box on the overlay itself.
 In the `ctrl-g` overlay, press **`a`** to open a chat that fans out over the agent
 sessions in the current window. Ask high-level orienting questions — "what is each
 one doing?", "what is most urgent?", "which are waiting on me?" — and keep asking;
-it is `gm ask`, scoped to the panes in front of you rather than your whole recent
+it is `gmux ask`, scoped to the panes in front of you rather than your whole recent
 list. Any other key still just closes the overlay.
 
-Also available directly: `gm ask --window <window-id>`.
+Also available directly: `gmux ask --window <window-id>`.
 
 ## 0.10.2
 
@@ -200,7 +230,7 @@ halved.
 A pane running a *fresh* session (no session id on its command line) fell back to
 "newest session in this directory" — which is whatever another pane is actively
 working on, so its summary got copied onto the fresh one, especially across
-windows. Panes are now resolved together: an exact match (a `gm run` link or a
+windows. Panes are now resolved together: an exact match (a `gmux run` link or a
 session id read from the agent's argv) claims its session, and no heuristic pane
 may pick a session another pane already owns.
 
@@ -219,7 +249,7 @@ session:
 - **summary** — new: a paragraph or two that actually reorients you, tracing how
   the work evolved and where it stands.
 
-`ctrl-g` (and `gm show`) render all three — headline, overview, then the
+`ctrl-g` (and `gmux show`) render all three — headline, overview, then the
 drilldown — above the recent/open/next status. The label stays the one-liner;
 the drilldown is one keypress away.
 
@@ -232,24 +262,24 @@ the drilldown is one keypress away.
 
 ## 0.9.0
 
-gigamanage becomes what it was always meant to be: **a background agent that
+gmux becomes what it was always meant to be: **a background agent that
 keeps you up to date on your agents' latest work.**
 
-**Upgrading:** re-run `gm tmux install` (or, on Oh My Tmux, keep the `Alt-g` line
+**Upgrading:** re-run `gmux tmux install` (or, on Oh My Tmux, keep the `Alt-g` line
 in `~/.tmux.conf.local`) and reload. `Alt-g` now toggles a live service rather
 than painting labels once. Nothing else changes.
 
 ### `Alt-g` runs a live label agent
 
-`Alt-g` starts a single, lightweight background service (`gm watch`) that every
+`Alt-g` starts a single, lightweight background service (`gmux watch`) that every
 few seconds resolves every agent pane across all your windows and keeps its
 border label current — the session's headline, where the pane is, with the
 content still visible. A pane whose summary is being regenerated shows
-`gm summaries loading…` until it lands. `Alt-g` again stops it. `ctrl-g` is still
+`gmux summaries loading…` until it lands. `Alt-g` again stops it. `ctrl-g` is still
 the full card when you want the detail; the two share one continuously-maintained
 cache, so the popup opens already current.
 
-You can also drive it directly: `gm watch` starts it, `gm watch --stop` stops it.
+You can also drive it directly: `gmux watch` starts it, `gmux watch --stop` stops it.
 
 ### Summaries refresh when work *diverges*, not on every keystroke
 
@@ -259,8 +289,8 @@ characters, fixed size however long the session grows), and a session is
 re-summarised only when that fingerprint has drifted past a threshold — with a
 safety net: a new tool failure, a flip to ended-mid-task, or a change in the
 files touched always refreshes, so a small-but-important change is never slept
-through. Tune the threshold with `GIGAMANAGE_REFRESH_DISTANCE`; the loop interval
-with `GIGAMANAGE_WATCH_INTERVAL_MS`.
+through. Tune the threshold with `GMUX_REFRESH_DISTANCE`; the loop interval
+with `GMUX_WATCH_INTERVAL_MS`.
 
 ## 0.8.2
 
@@ -283,7 +313,7 @@ rather than wrapped — press `ctrl-g` for the full card when you need it.
 
 ### Resolving a pane skips a needless `lsof`
 
-`gm tmux label` and the `ctrl-g` overlay read each pane's agent process to find
+`gmux tmux label` and the `ctrl-g` overlay read each pane's agent process to find
 its session. When the agent's command line already carries the session id (a
 resumed session — the common case), the id is exact and the process's working
 directory is never needed — but 0.8.0 looked it up anyway (`lsof` on macOS,
@@ -292,7 +322,7 @@ a window of resumed agents no longer pays for a directory lookup per pane.
 
 ## 0.8.0
 
-**Upgrading:** re-run `gm tmux install` to pick up the new `Alt-g` binding, and
+**Upgrading:** re-run `gmux tmux install` to pick up the new `Alt-g` binding, and
 reload with `tmux source-file ~/.tmux.conf`. Everything is additive; nothing you
 rely on changes.
 
@@ -300,11 +330,11 @@ rely on changes.
 
 The overlay used to map a pane to a session by matching the pane's working
 directory — but that's the *shell's* directory, usually `~`, not the agent's, so
-panes resolved to the wrong session or to nothing. gigamanage now reads the pane's
+panes resolved to the wrong session or to nothing. gmux now reads the pane's
 own process: the agent's command line carries the session id verbatim (`codex
 resume <id>`, `claude --resume <id>`), and that id *is* the session. Where there's
 no id on the line (a fresh session), it uses the agent process's real working
-directory instead of the shell's. No `gm run`, no setup — it just reads what's
+directory instead of the shell's. No `gmux run`, no setup — it just reads what's
 already there.
 
 ### A label on every pane's border
@@ -313,7 +343,7 @@ already there.
 headline, right where the pane is — while the pane content stays fully visible. It
 answers "what is each of these agents doing?" without taking over the screen; the
 `ctrl-g` full-card popup is still there when you want the detail. The label is
-stored in a pane-local option gigamanage owns, so a running agent's own title
+stored in a pane-local option gmux owns, so a running agent's own title
 updates can't clobber it.
 
 ### The peek does less work
@@ -330,13 +360,13 @@ made it usable in practice.
 
 ### The `ctrl-g` binding now actually opens the overlay
 
-`gm tmux install` wrote `gm overlay #{window_id}`, but tmux does not expand that
+`gmux tmux install` wrote `gmux overlay #{window_id}`, but tmux does not expand that
 format inside `display-popup -E` — so the shell saw the `#` and treated the rest
-of the line as a comment, and `gm overlay` ran with no window argument. The
+of the line as a comment, and `gmux overlay` ran with no window argument. The
 result was a popup that flashed and vanished. The binding now resolves the window
-id in-shell with `gm overlay "$(tmux display -p "#{window_id}")"`, which works
+id in-shell with `gmux overlay "$(tmux display -p "#{window_id}")"`, which works
 whether or not tmux expands the format. If you installed 0.7.0's binding, re-run
-`gm tmux install` (or, on Oh My Tmux, replace the two lines in
+`gmux tmux install` (or, on Oh My Tmux, replace the two lines in
 `~/.tmux.conf.local`) and reload with `tmux source-file ~/.tmux.conf`.
 
 ### Panes are framed, so cards read as separate
@@ -361,50 +391,50 @@ is what tells them apart.
 ## 0.7.0
 
 **Upgrading:** nothing changes unless you opt in. Everything below is additive and
-gated behind tmux; if you don't run `gm tmux install`, `gm` behaves exactly as it
+gated behind tmux; if you don't run `gmux tmux install`, `gmux` behaves exactly as it
 did in 0.6.1. The overlay needs **tmux 3.2 or newer** (for `display-popup`), which
-`gm doctor` now checks for.
+`gmux doctor` now checks for.
 
 ### Peek at every agent at once, from tmux
 
-Drive your agents in tmux and `gm` can now answer "what's happening in each of
-these panes?" without you switching into any of them. `gm tmux install` writes two
+Drive your agents in tmux and `gmux` can now answer "what's happening in each of
+these panes?" without you switching into any of them. `gmux tmux install` writes two
 key bindings to `~/.tmux.conf`:
 
 - **ctrl-g** peeks — every pane in the current window is overlaid *in place* with
   its summary card (what landed, what's still open, the next step, the `⚠`
   mid-task flag). Cards paint instantly from the cache and refresh in the
   background; any key dismisses the overlay and leaves your panes untouched.
-- **ctrl-shift-g** opens the `gm` picker in a popup, and Enter resumes your choice
+- **ctrl-shift-g** opens the `gmux` picker in a popup, and Enter resumes your choice
   into a new tmux window — history and live panes, one keystroke apart.
 
 The overlay maps a pane to its session by working directory and recency. For an
 exact link — including resumed sessions that share a directory — launch through
-`gm run claude` / `gm run codex resume`: it attaches your terminal as usual and
+`gmux run claude` / `gmux run codex resume`: it attaches your terminal as usual and
 records which pane the session runs in.
 
-`gm doctor` reports whether the overlay is available and, if not, why. tmux joins
+`gmux doctor` reports whether the overlay is available and, if not, why. tmux joins
 ripgrep and fzf as an optional companion; nothing here is required.
 
 ## 0.6.1
 
 ### The chat/summary split is coloured now
 
-The picker's preview pane rendered monochrome — its stdout is a pipe, so gm's
+The picker's preview pane rendered monochrome — its stdout is a pipe, so gmux's
 colour gated itself off, and even the `── ask ──` divider between the session
 card and the chat came out plain. fzf paints the preview with `--ansi`, though,
-so the seam can carry colour: the divider is now **cyan** (gm's own accent) and
-the `you` / `gm` speaker labels light up, while the card stays monochrome.
+so the seam can carry colour: the divider is now **cyan** (gmux's own accent) and
+the `you` / `gmux` speaker labels light up, while the card stays monochrome.
 
 It's an accent, not the message — the divider's glyphs and the speakers' layout
 still carry the structure, so `NO_COLOR` and `TERM=dumb` lose only the colour.
-`gm ls` and `gm show` are unchanged and still pipe clean.
+`gmux ls` and `gmux show` are unchanged and still pipe clean.
 
 ## 0.6.0
 
 **Upgrading:** `ctrl-o` in the picker no longer suspends the list. It opens the
 chat in the preview pane instead, so the session you were reading stays on
-screen. Nothing else changes for you: bare `gm ask`, the `--json` form, and the
+screen. Nothing else changes for you: bare `gmux ask`, the `--json` form, and the
 `fzf < 0.46` and no-fzf fallbacks all behave exactly as before.
 
 ### ctrl-o asks in the pane, not over the list
@@ -440,40 +470,40 @@ REPL, and the no-fzf numbered list keeps its `a` key.
 
 ## 0.5.0
 
-**Upgrading:** the first time you run `gm` in a terminal, it will ask you to
+**Upgrading:** the first time you run `gmux` in a terminal, it will ask you to
 choose a harness before doing any model work. Nothing prompts when the output
-isn't a terminal, and `GIGAMANAGE_SUMMARY_CMD` still overrides everything — so
+isn't a terminal, and `GMUX_SUMMARY_CMD` still overrides everything — so
 scripts, CI and agents are unaffected.
 
-### gm asks who to call, once, instead of assuming
+### gmux asks who to call, once, instead of assuming
 
-The first time you run `gm` in a terminal it asks which harness should do its
+The first time you run `gmux` in a terminal it asks which harness should do its
 model work — Claude Code, Codex, any command that reads a prompt on stdin, or
 nothing at all. Before, it assumed `claude -p` and started spending tokens in the
 background without ever mentioning it.
 
-Your answer lives in `~/.config/gigamanage/config.json`, and `gm setup` changes
-it. Choosing **nothing** is a real answer: `gm ls` and `gm show` still work on
+Your answer lives in `~/.config/gmux/config.json`, and `gmux setup` changes
+it. Choosing **nothing** is a real answer: `gmux ls` and `gmux show` still work on
 hard facts alone, and nothing calls a model.
 
 Nothing prompts unless there's a human at the other end. No TTY, `--json`, or an
-internal command means gm behaves exactly as it did before: autodetect and carry
-on. `GIGAMANAGE_SUMMARY_CMD` still overrides everything, so existing scripts and
+internal command means gmux behaves exactly as it did before: autodetect and carry
+on. `GMUX_SUMMARY_CMD` still overrides everything, so existing scripts and
 CI need no changes.
 
-### gm ask
+### gmux ask
 
-`gm ls` answers "what was I doing?" one row at a time. **`gm ask`** answers the
+`gmux ls` answers "what was I doing?" one row at a time. **`gmux ask`** answers the
 question that spans them:
 
 ```bash
-gm ask "what's still broken?"
-gm ask "what did I already try for the retry?" --json
+gmux ask "what's still broken?"
+gmux ask "what did I already try for the retry?" --json
 ```
 
 It starts from the summaries already on disk, so a question costs one model call
 rather than a scan of your transcripts. When the summaries aren't enough it runs
-`gm grep` against the real thing and reads what you actually said.
+`gmux grep` against the real thing and reads what you actually said.
 
 **In the picker, `ctrl-o`** opens it on the session you're highlighting and drops
 you back in the list, right where you were, when you're done. Without fzf, the
@@ -484,7 +514,7 @@ Not `shift+f`: fzf's query line eats plain letters, so `F` would just type an
 
 ### The picker explains its markers
 
-`gm ls` printed a key for `⚠`, `◐` and `○`. The picker — bare `gm` — rendered the
+`gmux ls` printed a key for `⚠`, `◐` and `○`. The picker — bare `gmux` — rendered the
 same three markers and explained none of them, which put the explanation exactly
 where you needed it least: `ls` is the command you run to read a list, and the
 picker is the one you run to *choose*. `⚠` is the whole point of the tool, and in
@@ -494,7 +524,7 @@ Both picker paths now carry a key: a second header line under fzf, and a line
 above the "install fzf" hint in the numbered fallback.
 
 It is deliberately static — every marker, always, and never a count — while
-`gm ls` keeps its counted one. fzf sets its header once, at spawn; ctrl-r
+`gmux ls` keeps its counted one. fzf sets its header once, at spawn; ctrl-r
 replaces the list and leaves the header alone. Counts there would freeze at open
 and be wrong after the first refresh, which is precisely when they change. A key
 that is stale exactly when it matters is worse than no key at all.
@@ -512,26 +542,26 @@ that need one, without leaving the picker — so it's something you can navigate
 while an agent works alongside you. Without fzf, the numbered list takes `r` for
 the same thing.
 
-Repeated presses are safe. The lock that already stopped five `gm ls` from
+Repeated presses are safe. The lock that already stopped five `gmux ls` from
 starting five summarizers stops this too: a press while a pass is running just
 reloads. Sessions whose summary is already current are never rewritten, so ctrl-r
 on a fresh list costs nothing.
 
-### Bare `gm` summarizes what it shows
+### Bare `gmux` summarizes what it shows
 
-Only `gm ls` kicked off a background pass; the picker never did. It does now,
+Only `gmux ls` kicked off a background pass; the picker never did. It does now,
 over the sessions it is about to offer, and rows being written are marked `◐`
-there as well as in `gm ls`.
+there as well as in `gmux ls`.
 
 ### Fixed: `--no-auto-summarize` never worked
 
-`gm --no-auto-summarize ls` spent tokens anyway. The flag is declared on the root
+`gmux --no-auto-summarize ls` spent tokens anyway. The flag is declared on the root
 command, and commander does not copy root options into a subcommand's own
 options — so the check read `undefined`, compared it against `false`, and
-concluded you wanted summaries. Only `GIGAMANAGE_AUTO_SUMMARIZE=0` actually
+concluded you wanted summaries. Only `GMUX_AUTO_SUMMARIZE=0` actually
 turned them off.
 
-The flag now works, on `gm ls` and in the picker, and it is carried across to the
+The flag now works, on `gmux ls` and in the picker, and it is carried across to the
 process ctrl-r starts.
 
 ### Shorter headlines
@@ -543,19 +573,19 @@ are now one scannable clause, sized to the column they live in.
 The summary cache key covers the prompt as well as the session, so this reaches
 summaries already on disk: they regenerate in the background on first run rather
 than keeping their old headlines forever. That costs a pass of model calls once.
-`GIGAMANAGE_AUTO_SUMMARIZE=0` still opts out of all of it.
+`GMUX_AUTO_SUMMARIZE=0` still opts out of all of it.
 
 ## 0.3.0
 
 ### Summaries keep up with what you actually look at
 
-The background pass used to cover a fixed **10** sessions while `gm ls` displayed
+The background pass used to cover a fixed **10** sessions while `gmux ls` displayed
 **20** — so the bottom half of the default view was permanently marked "no summary
 yet", and the feature looked broken even though it was working exactly as built.
 
-The window now follows the list: `gm ls` keeps 20 summarized, `gm ls -n 50` keeps
+The window now follows the list: `gmux ls` keeps 20 summarized, `gmux ls -n 50` keeps
 all fifty. Summaries are written **8 at a time** in parallel (tune with
-`GIGAMANAGE_SUMMARY_CONCURRENCY`), and a single pass writes at most 50, saying so
+`GMUX_SUMMARY_CONCURRENCY`), and a single pass writes at most 50, saying so
 rather than truncating in silence.
 
 ### You can see it working
@@ -568,7 +598,7 @@ is true on the very run that starts the work.
 
 The worker's stdio is discarded, so a broken provider used to mean summaries
 simply never appeared, with nothing to look at. Failures now land in
-`~/.cache/gigamanage/auto-summarize.log`, and `gm doctor` surfaces the last one.
+`~/.cache/gmux/auto-summarize.log`, and `gmux doctor` surfaces the last one.
 
 **Fixed:** the worker could silently write **zero** summaries. It resolved its
 queue by loading "the N most recent sessions" and filtering — but with sidechains
@@ -585,14 +615,14 @@ installed) wraps as well.
 
 ## 0.2.0
 
-**gigamanage now spends tokens on your behalf unless you tell it not to.** That is a
+**gmux now spends tokens on your behalf unless you tell it not to.** That is a
 change of default behavior, which is why this is a minor bump rather than a patch —
 everything in it already shipped as 0.1.3/0.1.4, but the version number was
 under-selling it.
 
 ### Summaries write themselves
 
-Any `gm` command now checks the 10 most recent sessions and, if any lack a current
+Any `gmux` command now checks the 10 most recent sessions and, if any lack a current
 summary, writes them in a **detached background process**. The foreground command
 never waits on a model: it prints, tells you on stderr what it started, and exits.
 Summaries appear on your next run. Rows still waiting are marked `○`.
@@ -600,36 +630,36 @@ Summaries appear on your next run. Rows still waiting are marked `○`.
 Three things this deliberately does not do:
 
 - **Block.** A summary costs ~8s of model time. Ten of those inline would turn a
-  60ms `gm ls` into a minute of waiting.
-- **Stampede.** A lock in `~/.cache/gigamanage` means five `gm ls` in a row start
+  60ms `gmux ls` into a minute of waiting.
+- **Stampede.** A lock in `~/.cache/gmux` means five `gmux ls` in a row start
   one summarizer, not five.
 - **Loop.** The summarizer *is* `claude -p`, which writes a session of its own.
-  Automated runs and sidechains are excluded from the target set, so gigamanage
+  Automated runs and sidechains are excluded from the target set, so gmux
   cannot summarize its own summarizer forever.
 
 **Turning it off**, because background model calls cost money:
 
 ```bash
-gm --no-auto-summarize ls          # once
-export GIGAMANAGE_AUTO_SUMMARIZE=0 # for good
+gmux --no-auto-summarize ls          # once
+export GMUX_AUTO_SUMMARIZE=0 # for good
 ```
 
 It also stays quiet when no summary provider is installed — a missing `claude`
-never breaks a read command. `gm doctor` reports the current state.
+never breaks a read command. `gmux doctor` reports the current state.
 
-### `gm ls` wraps instead of truncating
+### `gmux ls` wraps instead of truncating
 
 Long descriptions were cut off at 72 characters, so the sessions with the most
 informative summaries were exactly the ones you could not read. They now wrap to the
 terminal, with continuation lines indented under the description column.
 
-Piped output still emits **one line per session**, untruncated, so `gm ls | grep`
+Piped output still emits **one line per session**, untruncated, so `gmux ls | grep`
 behaves. The fzf picker's rows stay single-line, because fzf maps lines back to
 session ids.
 
 ## 0.1.2
 
-- `gm --version` reported a hardcoded `0.1.0` regardless of the installed version.
+- `gmux --version` reported a hardcoded `0.1.0` regardless of the installed version.
   It now reads `package.json`.
 
 ## 0.1.1
@@ -648,7 +678,7 @@ First release.
   the *tail* of each transcript, because a harness's own title is written in the
   first few seconds and never revised.
 - Sessions that ended mid-task are flagged `⚠`.
-- `gm resume` hands off to the right CLI (`claude --resume` / `codex resume`) in the
+- `gmux resume` hands off to the right CLI (`claude --resume` / `codex resume`) in the
   session's original directory.
 - `--json` on every read command, so agents can call it too.
 - Read-only: never writes to a session file.