hatcheck 0.7.0__tar.gz → 0.7.2__tar.gz

{hatcheck-0.7.0 → hatcheck-0.7.2}/Cargo.lock

@@ -356,7 +356,7 @@ dependencies = [
 
 [[package]]
 name = "hatcheck"
-version = "0.7.0"
+version = "0.7.2"
 dependencies = [
  "base64 0.22.1",
  "chrono",

{hatcheck-0.7.0 → hatcheck-0.7.2}/Cargo.toml

@@ -6,7 +6,7 @@ exclude = ["desktop/src-tauri"]
 resolver = "2"
 
 [workspace.package]
-version = "0.7.0"
+version = "0.7.2"
 edition = "2021"
 license = "MIT"
 rust-version = "1.90"

{hatcheck-0.7.0 → hatcheck-0.7.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hatcheck
-Version: 0.7.0
+Version: 0.7.2
 Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
@@ -29,14 +29,30 @@ Project-URL: Issues, https://github.com/hatcheck/hatcheck/issues
 
 # Hatcheck
 
-Several Claude accounts on one computer, each kept apart: isolated Claude Desktop instances on
-macOS, and Claude Code CLI profiles, with recent sessions, plan usage and resume commands across all
-of them. OpenAI's Codex CLI and Moonshot's Kimi Code CLI get the same treatment, Google's
-Antigravity CLI (`agy`) and Z.ai's ZCode are read beside them, and DeepSeek Harness (`dsh`),
-MiniMax Code (`mcode`), Qwen Code (`qwen`), GitHub Copilot CLI (`copilot`) and OpenCode
-(`opencode`) join as read-only agents. Sessions can be carried between all ten: as a file the
-agent is started on for those without an importer, and through their own importers for copilot
-and opencode.
+Several Claude accounts on one computer, each kept apart: work and personal, a team seat and your
+own plan. On macOS and Windows each gets its own Claude Desktop, with its own login and an icon in
+its own colour; anywhere, each gets its own Claude Code profile, with recent sessions, plan usage
+and resume commands across all of them in one list. OpenAI's Codex CLI and Moonshot's Kimi Code CLI
+get the same treatment, Google's Antigravity CLI (`agy`) and Z.ai's ZCode are read beside them, and
+DeepSeek Harness (`dsh`), MiniMax Code (`mcode`), Qwen Code (`qwen`), GitHub Copilot CLI (`copilot`)
+and OpenCode (`opencode`) join as read-only agents. Sessions can be carried between all ten: as a
+file the agent is started on for those without an importer, and through their own importers for
+copilot and opencode.
+
+Hatcheck never asks for, stores, copies or moves a login, is never between an agent and its model,
+runs nothing in the background, and never switches accounts on its own: see
+[Rules it keeps](#rules-it-keeps).
+
+**Start here:**
+
+- [Two Claude accounts on one Mac](https://hatcheck.dev/two-claude-accounts-on-one-mac): a Claude
+  Desktop per account, in three commands.
+- [Claude Code with two accounts](https://hatcheck.dev/claude-code-two-accounts): a profile per
+  account, and one list of what's in all of them; the same for
+  [Codex](https://hatcheck.dev/codex-two-accounts) and [Kimi Code CLI](https://hatcheck.dev/kimi-code-two-accounts),
+  and [what's left of each plan](https://hatcheck.dev/claude-usage-limits).
+- [Install the CLI](#install): one line on macOS, Linux or Windows. The menu-bar app is
+  [on its way](#the-desktop-app).
 
 *Unofficial: not made by, affiliated with or endorsed by Anthropic, OpenAI, Google, Moonshot AI,
 Z.ai, DeepSeek, MiniMax, Alibaba Cloud, GitHub or the OpenCode project. Claude, Claude Code and
@@ -45,16 +61,16 @@ and Gemini are trademarks of Google LLC; Kimi is Moonshot AI's, ZCode and GLM ar
 Harness is DeepSeek's, MiniMax Code is MiniMax's, Qwen Code is Alibaba Cloud's, GitHub Copilot is
 GitHub's and OpenCode is the OpenCode project's.*
 
-On macOS, `hatcheck desktop` runs **one Claude Desktop per account, side by side**: each with its
-own data folder and login, and a launcher in a colour you pick, which brings the running one
-forward rather than opening it twice.
+On macOS and Windows, `hatcheck desktop` runs **one Claude Desktop per account, side by side**:
+each with its own data folder and login, and a launcher in a colour you pick, which brings the
+running one forward rather than opening it twice.
 
 Running Claude Desktop with its own `--user-data-dir` is
 [Philipp Stracker's approach](https://gist.github.com/stracker-phil/9f84927a556632c7f9cc06663b534f14)
 ([write-up](https://philippstracker.com/multiple-claude-instances/)); hatcheck adds the colours and
 the launchers.
 
-It also has **command-line tools for all seven agents**, for keeping one profile per account:
+It also has **command-line tools for all ten agents**, for keeping one profile per account:
 `cl`, `cx` and `ck` run Claude Code, Codex and Kimi Code CLI with a profile, and `hatcheck` lists
 the recent sessions in all of them, with the command that resumes each one or opens DSH's session
 history, and what's left of each plan. The rest
@@ -72,32 +88,35 @@ knowing which one each session ran on. See [Rules it keeps](#rules-it-keeps).
 
 |                                 | macOS | Linux | Windows |
 |---------------------------------|:-----:|:-----:|:-------:|
-| Claude Desktop instances        |  yes  | [untried](#roadmap): Claude Desktop for Linux is in beta | [planned](#roadmap) |
+| Claude Desktop instances        |  yes  | [untried](#roadmap): Claude Desktop for Linux is in beta |   yes   |
 | Claude Code, Codex, Antigravity CLI, Kimi Code CLI, ZCode, DeepSeek Harness, MiniMax Code, Qwen Code, GitHub Copilot CLI and OpenCode tools |  yes  |  yes  |   yes   |
 
 ---
 
-## Claude Desktop instances (macOS)
+## Claude Desktop instances (macOS and Windows)
 
 `hatcheck desktop` makes them: each instance gets its own data folder, `~/.claude-instances/<name>`,
-and a launcher in `/Applications` with Claude's icon in a colour you pick. The launcher brings a
-running instance's window forward instead of starting a second one on the same folder.
+and a launcher with Claude's icon in a colour you pick: an app in `/Applications` on macOS, a
+shortcut in the Start menu on Windows. The launcher brings a running instance's window forward
+instead of starting a second one on the same folder.
 
 ```bash
-hatcheck desktop new a A --hue 190                # Claude A.app, blue
-hatcheck desktop new b B --hue -10                # Claude B.app, red-orange
-hatcheck desktop open a                           # or open it from Launchpad or the Dock
+hatcheck desktop new a A --hue 190                # Claude A.app, or Claude A in the Start menu: blue
+hatcheck desktop new b B --hue -10                # Claude B, red-orange
+hatcheck desktop open a                           # or open it from Launchpad, the Dock or the Start menu
 hatcheck desktop                                  # the instances, and which are running
 hatcheck desktop remove a                         # its launcher; --data deletes its data folder too
 ```
 
-Sign each one in to its account the first time it opens. The first time a launcher brings a window
-forward, macOS asks whether it may control System Events; allow it, once per launcher. `--hue`
+Sign each one in to its account the first time it opens. On macOS, the first time a launcher brings
+a window forward, macOS asks whether it may control System Events; allow it, once per launcher. On
+Windows, Claude Desktop (the Microsoft Store version) keeps one process per data folder itself, so
+the launcher is a plain shortcut. `--hue`
 turns the icon's colours by that many degrees (about 110 is green, 190 blue, 240 purple) and
-`--saturation` scales them. hatcheck recolours the icon itself, with macOS's `iconutil`, and a
-launcher it can't recolour keeps Claude's own icon. The name `default` makes a launcher for
-Claude's built-in data folder, which is only safe while nothing else runs on that folder, the stock
-Claude icon included. [docs/desktop-instances.md](docs/desktop-instances.md) has the rest: what
+`--saturation` scales them. hatcheck recolours the icon itself, with macOS's `iconutil` or, on
+Windows, from the artwork in Claude's own package, and a launcher it can't recolour keeps Claude's
+own icon. The name `default` makes a launcher for Claude's built-in data folder, which on macOS is
+only safe while nothing else runs on that folder, the stock Claude icon included. [docs/desktop-instances.md](docs/desktop-instances.md) has the rest: what
 the launcher does, and how to copy a login you already have into an instance.
 
 ---
@@ -107,38 +126,34 @@ the launcher does, and how to copy a login you already have into an instance.
 Claude Code (the `claude` CLI) keeps its settings, history and session transcripts in `~/.claude`
 (plus `~/.claude.json`), and its login in the macOS Keychain, or on Linux and Windows in
 `~/.claude/.credentials.json`. Point `CLAUDE_CONFIG_DIR` at another folder and you get a separate
-profile with its own login, so you can keep one per account:
-`~/.claude-a`, `~/.claude-b`, and so on. These are separate from the Desktop instances
-above, though sessions from Desktop's Code tab can be filed in them too (the session list
-hides those unless you pass `--all`). Codex works the same way with `CODEX_HOME`: see
-[`cx`](docs/agents.md#cx-run-codex-with-a-home-per-account). Antigravity CLI keeps everything under
-`~/.gemini/antigravity-cli`, which only `HOME` moves, so hatcheck reads that one folder: see
-[Antigravity CLI](docs/agents.md#antigravity-cli-agy). Kimi Code CLI works like Codex, with
-`KIMI_CODE_HOME` and one home per account (`~/.kimi-code-a`), which [`ck`](docs/agents.md#ck-run-kimi-code-cli-with-a-home-per-account)
-runs it with, and ZCode keeps its sessions in a database under `~/.zcode`, which only `HOME`
-moves: see [Kimi Code CLI](docs/agents.md#kimi-code-cli-kimi) and [ZCode](docs/agents.md#zcode-zcode).
-DeepSeek Harness keeps sessions under `~/.dsh`, moved whole by `DSH_HOME`, so hatcheck reads
-`~/.dsh`, `~/.dsh-NAME` and the variable's folder. DSH's own profiles are plugin stacks, not these
-account homes, and there is no hatcheck DSH launcher: its command is the official `dsh web`, whose
-session history you choose the session in. See [DeepSeek Harness](docs/agents.md#deepseek-harness-dsh).
-MiniMax Code's current data home is `~/.minimax`, selected by `MINIMAX_DATA_DIR`, or by
-`MAVIS_DATA_DIR` when that's unset; `~/.minimax-code` is the installer, not a profile. Hatcheck
-reads its v2 SQLite catalog and canonical JSONL, and sessions resume directly with
-`mcode --session mvs_<id>`. See [MiniMax Code](docs/agents.md#minimax-code-mcode). Qwen Code
-keeps everything under `~/.qwen`, moved whole by `QWEN_HOME`, so hatcheck reads `~/.qwen`,
-`~/.qwen-NAME` and the variable's folder: each project's transcripts, which resume directly with
-`qwen --resume <id>`. See [Qwen Code](docs/agents.md#qwen-code-qwen). GitHub Copilot CLI keeps
-everything under `~/.copilot`, moved whole by `COPILOT_HOME`, so hatcheck reads `~/.copilot`,
-`~/.copilot-NAME` and the variable's folder: each session's events, which resume directly with
-`copilot --resume <id>`. See [GitHub Copilot CLI](docs/agents.md#github-copilot-cli-copilot).
-OpenCode 2 keeps every project's sessions in one database, `~/.local/share/opencode/opencode.db`,
-which hatcheck reads; they resume directly with `opencode --session ses_<id>`. See
-[OpenCode](docs/agents.md#opencode-opencode).
+profile with its own login, so you can keep one per account: `~/.claude-a`, `~/.claude-b`, and so
+on. These are separate from the Desktop instances above, though sessions from Desktop's Code tab
+can be filed in them too (the session list hides those unless you pass `--all`). The other agents
+keep theirs as the table says; [docs/agents.md](docs/agents.md) has each one's folders, what
+hatcheck reads of them, and the version that was checked against.
+
+| Agent | Its folder | A home per account | A session carried to it | Plan usage |
+|---|---|---|---|---|
+| Claude Code | `~/.claude` | `CLAUDE_CONFIG_DIR`, with [`cl`](docs/agents.md#cl-run-claude-code-with-a-profile) | written into the profile | Claude Code's own `/usage` |
+| Codex | `~/.codex` | `CODEX_HOME`, with [`cx`](docs/agents.md#cx-run-codex-with-a-home-per-account) | written into the home | ChatGPT's usage endpoint |
+| [Antigravity CLI](docs/agents.md#antigravity-cli-agy) | `~/.gemini/antigravity-cli` | none: only `HOME` moves it | a file `agy` is started on | agy's own `/usage` |
+| [Kimi Code CLI](docs/agents.md#kimi-code-cli-kimi) | `~/.kimi-code` | `KIMI_CODE_HOME`, with [`ck`](docs/agents.md#ck-run-kimi-code-cli-with-a-home-per-account) | written into the home | Kimi's usage endpoint |
+| [ZCode](docs/agents.md#zcode-zcode) | `~/.zcode`, a database | none: only `HOME` moves it | a file `zcode` is started on | none to read |
+| [DeepSeek Harness](docs/agents.md#deepseek-harness-dsh) | `~/.dsh` | `DSH_HOME` | a prompt to paste into `dsh web` | none to read |
+| [MiniMax Code](docs/agents.md#minimax-code-mcode) | `~/.minimax` | `MINIMAX_DATA_DIR`, or `MAVIS_DATA_DIR` | a file `mcode` is started on | not wired yet |
+| [Qwen Code](docs/agents.md#qwen-code-qwen) | `~/.qwen` | `QWEN_HOME` | a file `qwen` is started on | none to read |
+| [GitHub Copilot CLI](docs/agents.md#github-copilot-cli-copilot) | `~/.copilot` | `COPILOT_HOME` | `copilot sessions import` | none to read |
+| [OpenCode](docs/agents.md#opencode-opencode) | `~/.local/share/opencode`, one database | not yet | `opencode session import` | its providers' own |
+
+Every agent's sessions are listed and shown, and can be carried to any of the others, each in the
+way the table's fourth column says. Claude Code's, Codex's and Kimi Code CLI's also move between
+two homes of the same agent; ZCode's database and DeepSeek Harness's, MiniMax Code's, Qwen
+Code's, Copilot's and OpenCode's stores are only ever read.
 
 ### Install
 
 One binary per platform, with no Python needed. Each of these installs `hatcheck`, `hat`, `cl`,
-`cx`, `ck`, `claude-z` and `claude-k`:
+`cx`, `ck`, `claude-z`, `claude-k`, `claude-m` and `claude-d`:
 
 ```bash
 curl -LsSf https://github.com/hatcheck/hatcheck/releases/latest/download/hatcheck-installer.sh | sh
@@ -155,7 +170,10 @@ powershell -ExecutionPolicy Bypass -c "irm https://github.com/hatcheck/hatcheck/
 ```
 
 The installer scripts put the commands in `~/.local/bin` and add that folder to your `PATH`; set
-`HATCHECK_NO_MODIFY_PATH=1` first to keep your shell's startup files as they are. Each release, made
+`HATCHECK_NO_MODIFY_PATH=1` first to keep your shell's startup files as they are. Completions
+for zsh, bash, fish and PowerShell come from
+[`hatcheck completions`](docs/commands.md#hatcheck-completions-for-zsh-bash-fish-and-powershell):
+`eval "$(hatcheck completions zsh)"` after `compinit`, and the others as that section says. Each release, made
 from a tag such as `v0.2.0`, has them and the binaries for each platform, and PyPI gets the same
 binaries as wheels. The release builds start after 0.1.0, which is the Python version.
 
@@ -171,42 +189,29 @@ Each is documented as it is, with its options and what it prints, in
 
 | Command | What it does |
 |---|---|
-| [`cl a --resume <id>`](docs/agents.md#cl-run-claude-code-with-a-profile) | Claude Code with `~/.claude-a`; `cl -z` and `cl -k` run it on Z.ai or Kimi there |
+| [`cl a --resume <id>`](docs/agents.md#cl-run-claude-code-with-a-profile) | Claude Code with `~/.claude-a`; `cl -z`, `-k`, `-m` and `-D` run it on Z.ai, Kimi, MiniMax or DeepSeek there |
 | [`cx a resume <id>`](docs/agents.md#cx-run-codex-with-a-home-per-account) | Codex with `~/.codex-a` |
 | [`ck a --session <id>`](docs/agents.md#ck-run-kimi-code-cli-with-a-home-per-account) | Kimi Code CLI with `~/.kimi-code-a` |
-| [`hatcheck`](docs/commands.md#hatcheck-what-to-resume) | the sessions active in the last day, in every profile, home and folder, each with its resume or open command and what's left of its plan |
-| [`hatcheck usage`](docs/commands.md#hatcheck-usage-plan-usage-for-every-profile) | what's left of every plan limit, sorted by Fable; DSH, Qwen Code, Copilot and OpenCode homes say why there's no reading, and mcode's quota isn't wired |
+| [`hatcheck`](docs/commands.md#hatcheck-what-to-resume) | the sessions active in the last day in this folder, or every folder with `-A`, each with its resume or open command, what it cost and what's left of its plan; `-d` adds each one's turns and spend by model, `-c` puts the costliest first, and [`config.toml`](docs/commands.md#configtoml-the-lists-defaults-and-what-to-leave-out) sets the defaults and the agents and folders every command leaves out |
+| [`hatcheck usage`](docs/commands.md#hatcheck-usage-plan-usage-for-every-profile) | what's left of every plan limit, sorted by Fable, and, from hatcheck's own readings over time, how fast each is being used up and whether it runs out before it resets; DSH, Qwen Code, Copilot and OpenCode homes say why there's no reading, and mcode's quota isn't wired |
 | [`hatcheck best`](docs/commands.md#hatcheck-best-which-account-to-use-now) | the best account now, with its limits, and the `move` command that carries the newest session started here to it; `--wait` sleeps until one has room |
 | [`hatcheck where SESSION`](docs/commands.md#hatcheck-where-find-a-session) | where a session's files are |
 | [`hatcheck open SESSION`](docs/commands.md#hatcheck-open-resume-a-session-in-a-new-terminal) | resume it in a new terminal, or open DSH's session history in its folder |
 | [`hatcheck resume`](docs/commands.md#hatcheck-resume-carry-on-the-newest-session-here) | carry on the newest session started from this folder, or open DSH's session history, after asking; `hat r` for short |
-| `hatcheck show SESSION` | its conversation, read-only |
+| [`hatcheck show SESSION`](docs/commands.md#hatcheck-show-a-sessions-conversation) | its conversation, read-only; `--markdown` writes it out as a document to keep or share |
+| [`hatcheck search WORDS`](docs/commands.md#hatcheck-search-the-sessions-that-mention-something) | the sessions whose title or conversation has every word, in every profile and home, newest first, with the turns the words are in |
 | [`hatcheck move SESSION PROFILE`](docs/commands.md#hatcheck-move-carry-on-a-session-with-another-profile) | carry it to another profile, or convert it for another agent; `--brief` hands over a brief in place of the whole conversation |
 | [`hatcheck fork SESSION PROFILE`](docs/commands.md#hatcheck-fork-a-session-as-a-new-one-in-another-profile) | bring it in there as a new session, keeping the original |
 | [`hatcheck relocate OLD NEW`](docs/commands.md#hatcheck-relocate-a-project-folder-that-moved) | a moved project folder's sessions, brought along; DSH's, mcode's, qwen's, copilot's and opencode's stay as they are |
 | [`hatcheck bind PROFILE`](docs/commands.md#hatcheck-bind-tie-a-folder-to-a-profile) | tie a folder to a profile, so `cl`, `cx` and `ck` pick it there and the list flags strays |
-| [`hatcheck doctor`](docs/install.md#hatcheck-doctor-every-copy-of-hatcheck-and-the-agents) | every copy of hatcheck and the agents on your `PATH`, which runs, how to remove the rest |
-| [`hatcheck desktop`](#claude-desktop-instances-macos) | Claude Desktop instances on macOS |
+| [`hatcheck profiles [A B]`](docs/commands.md#hatcheck-profiles-what-each-profile-is-set-up-with) | what each profile and home is set up with: skills, agents, commands, plugins, hooks, MCP servers, permissions and settings; with two named, what differs between them |
+| [`hatcheck statusline --install PROFILE`](docs/commands.md#hatcheck-statusline-which-account-a-session-is-on-in-claude-codes-status-line) | a status line for Claude Code with the profile the session runs in and what's left of its plan: `work · Opus 5.5 · 5h 62% ↻2h41m · wk 30% ↻3d2h · ctx 23% · $1.23` |
+| [`hatcheck completions SHELL`](docs/commands.md#hatcheck-completions-for-zsh-bash-fish-and-powershell) | the completions for zsh, bash, fish or PowerShell: subcommands, options, profiles and recent sessions |
+| [`hatcheck doctor`](docs/install.md#hatcheck-doctor-every-copy-of-hatcheck-and-the-agents) | every copy of hatcheck and the agents on your `PATH`, which runs, how to remove the rest, and how long each profile keeps its transcripts |
+| [`hatcheck desktop`](#claude-desktop-instances-macos-and-windows) | Claude Desktop instances on macOS and Windows |
 | [`--json`](docs/commands.md#--json-for-scripts-status-bars-and-apps) | the sessions, plans and results as data, for scripts, status bars and the desktop app |
 
-`hat` is the short name, and a subcommand can be cut to its first letters: `hat m` is `hat move`, `hat r` is `hat resume`.
-[Antigravity CLI](docs/agents.md#antigravity-cli-agy) sessions are listed, shown and converted
-from its one folder, with what its `/usage` reports; [Kimi Code CLI](docs/agents.md#kimi-code-cli-kimi)
-sessions are listed, shown, converted and moved between its homes, and [ZCode](docs/agents.md#zcode-zcode)'s
-are listed, shown and converted from its database. [DeepSeek Harness](docs/agents.md#deepseek-harness-dsh)
-sessions are listed and shown from raw or compressed v4 logs and converted out, never written;
-`dsh web` opens its session history. [MiniMax Code](docs/agents.md#minimax-code-mcode) sessions
-are listed and shown from its v2 catalog and canonical JSONL and converted out, never written;
-`mcode --session mvs_<id>` resumes them directly. [Qwen Code](docs/agents.md#qwen-code-qwen)
-sessions are listed and shown from its transcripts and converted both ways, its store never
-written: a session converted for qwen is a file qwen is started on, and `qwen --resume <id>`
-resumes its own. [GitHub Copilot CLI](docs/agents.md#github-copilot-cli-copilot) and
-[OpenCode](docs/agents.md#opencode-opencode) sessions are listed and shown from their stores and
-converted both ways, through their own importers: a session converted for either is a file its
-`sessions import` or `session import` takes, and `copilot --resume <id>` and
-`opencode --session ses_<id>` resume their own. [`claude-z` and
-`claude-k`](docs/agents.md#claude-z-claude-k-claude-code-on-zai-or-kimi)
-run Claude Code on Z.ai's or Kimi's models in any profile.
+`hat` is the short name, and a subcommand can be cut to its first letters: `hat m` is `hat move`, `hat r` is `hat resume`; the list's flags have single letters that bundle, so `hat -dc` is `hat --details --by-cost`. [`claude-z`, `claude-k`, `claude-m` and `claude-d`](docs/agents.md#claude-z-claude-k-claude-m-claude-d-claude-code-on-zai-kimi-minimax-or-deepseek) run Claude Code on Z.ai's, Kimi's, MiniMax's or DeepSeek's models in any profile.
 
 
 ## Rules it keeps
@@ -214,14 +219,17 @@ run Claude Code on Z.ai's or Kimi's models in any profile.
 Each rule names the code that keeps it, so it can be checked rather than taken on trust.
 
 - **Not in the path.** Nothing of Hatcheck sits between an agent and its model. `cl`, `cx` and
-  `ck` set `CLAUDE_CONFIG_DIR`, `CODEX_HOME` or `KIMI_CODE_HOME` (and, for `cl -z` and `cl -k`, the
-  provider variables you set up) and run the agent in their place; nothing stays running
+  `ck` set `CLAUDE_CONFIG_DIR`, `CODEX_HOME` or `KIMI_CODE_HOME` (and, for `cl -z`, `-k`, `-m` and
+  `-D`, the provider variables you set up) and run the agent in their place; nothing stays running
   ([`launch.rs`](crates/hatcheck/src/launch.rs), `run`).
 - **No agent's config is rewritten**, except when you ask: `hatcheck bind --hook` adds one
   session-start hook to each profile's `settings.json`, each Codex home's `hooks.json` and
   Antigravity CLI's `~/.gemini/config/hooks.json`, or points the one it added at the `hatcheck` it
   finds now, and `unbind --hook` removes only what it added ([`bind.rs`](crates/hatcheck/src/bind.rs),
-  `add_hooks` and `remove_hooks`).
+  `add_hooks` and `remove_hooks`); `hatcheck statusline --install` sets the `statusLine` of the
+  profiles you name, leaves one somebody else set alone, and `--uninstall` takes out only the one
+  it added ([`statusline.rs`](crates/hatcheck/src/statusline.rs), `install` and `uninstall`).
+  `hatcheck profiles` and `search` only read.
 - **No credentials.** It never asks for, stores, refreshes or moves a login. For Claude it never
   reads one: Claude Code's own `/usage` is run in the profile and the snapshot it saves is read
   ([`usage.rs`](crates/hatcheck/src/usage.rs), `run_claude_usage` and `claude_live`). For Codex, the
@@ -240,8 +248,9 @@ Each rule names the code that keeps it, so it can be checked rather than taken o
   model list agy fetches first to say it's signed in. `CODEX_USAGE_URL` in `usage.rs` and
   `DEFAULT_USAGE_URL` and `GLOBAL_USAGE_URL` in `kimi.rs` are the only addresses the binary itself
   calls; DSH, mcode, qwen, copilot and opencode add none. `--cached` and `--no-usage` make none. The
-  Z.ai and Kimi endpoints in [`provider.rs`](crates/hatcheck/src/provider.rs) are handed to Claude
-  Code, which calls them only when you run `cl -z` or `cl -k`.
+  Z.ai, Kimi, MiniMax and DeepSeek endpoints in [`provider.rs`](crates/hatcheck/src/provider.rs) are
+  handed to Claude Code, which calls them only when you run `claude-z`, `claude-k`, `claude-m` or
+  `claude-d`, or `cl` with `-z`, `-k`, `-m` or `-D`.
 - **What the agents send is theirs to govern.** Hatcheck adds no data path of its own. What each
   agent sends to its maker, and whether that is kept or used to train models, depends on the
   maker's terms for your product and plan, which differ between them and change; check them for
@@ -301,95 +310,39 @@ off until you turn it on. See [desktop/README.md](desktop/README.md) to build an
 
 ## Files in this repo
 
-- **`crates/hatcheck/`**: hatcheck in Rust, the commands and the launchers. Its `src/` has a file per
-  subcommand (`sessions.rs`, `usage.rs`, `move_cmd.rs`, `open_cmd.rs`, `desktop.rs` and the rest),
-  `launch.rs` for `cl`, `cx`, `ck`, `claude-z` and `claude-k`, `agy.rs`, `kimi.rs`, `zcode.rs`,
-  `dsh.rs`, `mcode.rs`, `qwen.rs`, `copilot.rs` and `opencode.rs` for what it reads and writes of
-  Antigravity CLI, Kimi Code CLI, ZCode, DeepSeek Harness, MiniMax Code, Qwen Code, GitHub Copilot
-  CLI and OpenCode, `doctor.rs` for `hatcheck doctor`, and
-  `src/bin/` for those binaries and `hat`.
-  Its own README is the crate's page on crates.io. It was ported from a Python version with the
-  same output; see [docs/rust-port.md](docs/rust-port.md).
-- **`CHANGELOG.md`**: what changed in each release of the CLI; a release's notes on GitHub are its
-  section there, and [docs/maintenance.md](docs/maintenance.md#releasing-the-cli) has the steps of
-  a release.
-- **`install.sh`** / **`install.ps1`**: build the commands from a clone and put them on your `PATH`
-  (`~/.local/bin` by default).
-- **`pyproject.toml`**: the PyPI package, the binaries as wheels built with maturin.
-  **`dist-workspace.toml`**: the release builds, installers and Homebrew formula, made by cargo-dist.
-  **`packaging/`**: the app's Homebrew cask, and the winget manifests for the app and the CLI.
-- **`desktop/`**: the desktop app: Tauri, with the CLI inside it ([its README](desktop/README.md)).
-- **`site/`**: the site, four pages sharing one stylesheet, with the images beside them, served at [hatcheck.dev](https://hatcheck.dev)
-  from Cloudflare as static assets; `site/deploy.sh` ships it. The logo lives there too:
-  `logo.svg` and `logo-dark.svg` (the mark), `logo-wordmark.svg` and `logo-wordmark-dark.svg`, `favicon.svg`.
-- **`docs/proposals/`**: the plans these came from: [the CLI features](docs/proposals/cli-features.md),
-  [the desktop app](docs/proposals/desktop-app.md), [Antigravity CLI](docs/proposals/antigravity.md)
-  and [Kimi Code CLI and ZCode](docs/proposals/kimi-zcode.md).
+- **`crates/hatcheck/`**: the CLI in Rust: a file per subcommand in `src/` and one per agent
+  (`agy.rs`, `kimi.rs`, `zcode.rs` and the rest), with the launchers in `launch.rs` and `src/bin/`.
+  It was ported from a Python version with the same output ([docs/rust-port.md](docs/rust-port.md)).
+- **`desktop/`**: the desktop app, Tauri with the CLI inside it ([its README](desktop/README.md)).
 - **`docs/`**: [commands.md](docs/commands.md), [agents.md](docs/agents.md) and
   [install.md](docs/install.md), each command, agent and way of installing as it is;
-  [desktop-instances.md](docs/desktop-instances.md) for the Desktop instances;
-  [rust-port.md](docs/rust-port.md) on the port from Python; [formats.md](docs/formats.md), each
-  agent's session format side by side and how a conversion works; [maintenance.md](docs/maintenance.md)
-  on checking each agent's newest version every week or two.
-- **`AGENTS.md`** and **`docs/lessons.md`**: notes for coding agents (`CLAUDE.md` imports them): how
-  to build and check, the rules the code keeps, and what earlier work got wrong, with the rule that
-  would have caught it.
-- **`tests/`**: the command tests, which run the binary against throwaway home folders:
-  `python3 -m unittest discover -s tests`, which builds it with cargo first, and the crate's own
-  tests with `cargo test -p hatcheck`. They never read your real profiles, Keychain or the network.
-  GitHub Actions runs both on macOS, Linux and Windows (`.github/workflows/tests.yml`).
-- **`scripts/`**: `upstream.py`, the read-only first step of [maintenance.md](docs/maintenance.md),
-  which `.github/workflows/upstream.yml` runs every Monday, keeping an issue open for what it
-  finds; and `provider_probe.py`, which runs each `claude-k` and `claude-z` model once.
+  [formats.md](docs/formats.md), each agent's session format side by side;
+  [maintenance.md](docs/maintenance.md), the check of each agent's newest version every week or
+  two, and the release steps; [desktop-instances.md](docs/desktop-instances.md); and
+  [proposals/](docs/proposals/), the plans these came from.
+- **`tests/`**: the command tests, which run the binary against throwaway home folders and never
+  read your real profiles, the Keychain or the network: `python3 -m unittest discover -s tests`,
+  beside the crate's own `cargo test -p hatcheck`. GitHub Actions runs both on macOS, Linux and
+  Windows.
+- **`AGENTS.md`** and **`docs/lessons.md`**: notes for coding agents (`CLAUDE.md` imports them),
+  and what earlier work got wrong, with the rule that would have caught it.
+- **`CHANGELOG.md`**, each release's notes; **`install.sh`** and **`install.ps1`**, to build from a
+  clone; **`pyproject.toml`** and **`dist-workspace.toml`**, the PyPI wheels and the release
+  builds; **`packaging/`**, the app's cask and the winget manifests; **`scripts/`**, `upstream.py`
+  (the Monday check) and `provider_probe.py`; and **`site/`**, [hatcheck.dev](https://hatcheck.dev)
+  and the logo.
 
 ## Roadmap
 
-- **Claude Desktop instances on Windows.** Claude Desktop is an Electron app there too, so a
-  separate `--user-data-dir` per account should work. A Windows version would create a shortcut per
-  instance with its own icon, and a launcher that brings a running instance forward instead of
-  opening a duplicate. It needs testing on a Windows machine first.
 - **Claude Desktop instances on Linux.** Claude Desktop for Linux is in beta, for Ubuntu and
   Debian. Whether its own `--user-data-dir` keeps an instance apart there, as on macOS, hasn't been
   tried; until it has, only the CLI tools apply on Linux.
-- **Antigravity CLI profiles.** agy keeps one login per home folder, so a second account needs a
-  home folder of its own (`HOME=~/.agy-a agy`), which every command the agent runs would see
-  too. Whether hatcheck should make such folders, and a launcher for them, is still open; until
-  then it reads `~/.gemini/antigravity-cli` only. The Antigravity app has the same one login,
-  in the system keyring, shared with agy, so an instance of it with its own data folder would
-  still be the same account; nothing for hatcheck to make until Google separates logins.
-- **ZCode.** Profiles need a variable from Z.ai that moves the session database (only `HOME` does
-  today), usage needs a usage command zcode doesn't have, and a session is never written into its
-  database, which the desktop app shares: a converted session is a file zcode is started on. If
-  Z.ai documents the import its desktop app uses or adds a `zcode import` command, hatcheck should
-  use that ([the proposal](docs/proposals/kimi-zcode.md) has the reasoning).
-- **DeepSeek Harness.** A direct per-session open needs an official web deep link or resume
-  command, a handover in one step needs a first prompt `dsh web` doesn't take, and plan usage needs
-  a documented quota API. Until then hatcheck opens `dsh web` and its session history, prints the
-  prompt to paste for a converted session, and never writes DSH's store. Sessions before v4 aren't read; later ones need their own reader.
-- **MiniMax Code.** A converted session is a file mcode's terminal UI is started on, as agy's,
-  since mcode has no importer; plan quota needs a no-refresh design and maintainer approval before
-  the regional endpoint is used. Until then hatcheck reads the v2 store and shows no quota data. An idle selected TUI has no durable marker, so only an active writer lease blocks
-  opening and conversion.
-- **Qwen Code.** A session converted for qwen is a file qwen is started on, as agy's and ZCode's
-  are, since qwen has no importer (`qwen sessions` lists sessions and imports none); one written
-  into its store would need one. Moving a session between qwen homes would copy its transcript,
-  file history and side state, which hasn't been done. Plan usage needs a command or endpoint qwen
-  doesn't have (its `usage/` files count the tokens a session spent, not what a plan has left).
-  `QWEN_RUNTIME_DIR`, which moves the session data alone and leaves the login behind, isn't
-  followed: only `QWEN_HOME`, which moves the home whole.
-- **GitHub Copilot CLI.** Its `/usage` runs only inside a session, so plan usage would need an
-  endpoint and maintainer approval before any request is made; until then its homes show no data.
-  Whether its system credential store keeps one login per `COPILOT_HOME` hasn't been checked:
-  hatcheck never reads a login, and the probe is in [maintenance.md](docs/maintenance.md).
-  Sessions aren't copied between its homes.
-- **OpenCode.** One data folder: a second store needs `XDG_DATA_HOME` or `OPENCODE_DB` and
-  `--standalone`, since its background service keeps the store it started with, and which of those
-  a named profile should mean is a decision not taken; until then hatcheck reads the folder plain
-  opencode uses. Nothing marks a session open. Plan usage is its providers' own.
 - **Releases:** the CLI is on GitHub, the Homebrew tap, PyPI and crates.io from 0.2.0
   ([CHANGELOG.md](CHANGELOG.md)). Next are winget, then the app's installers, once its release
   workflow has its signing and updater secrets (`desktop.yml` lists them).
 - **Signing:** a Developer ID for the macOS app, and a certificate for the Windows one.
+- **Each agent's gaps**, from Antigravity CLI profiles to a second OpenCode store, with what
+  would close each: [docs/agents.md](docs/agents.md#what-isnt-done-yet).
 
 ## Credits
 
@@ -407,7 +360,8 @@ off until you turn it on. See [desktop/README.md](desktop/README.md) to build an
 - **Z.ai and Kimi:** the provider settings in `crates/hatcheck/src/provider.rs` (endpoints, model slots, context
   windows and the config files) come from [claude-z](https://github.com/sam-fakhreddine/claude-z) by
   Kerim ([lettt325](https://github.com/lettt325)), MIT-licensed, and Yi Wang's
-  [fork](https://github.com/yiwang/claude-z) of it, which added Kimi.
+  [fork](https://github.com/yiwang/claude-z) of it, which added Kimi. MiniMax's and DeepSeek's are
+  their own Claude Code guides'.
 
 ## License