zames_pro 2.82.137 → 2.82.139

package/CHANGELOG.md

@@ -7,6 +7,159 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.82.139] - 2026-10-25
+
+### Changed
+
+- docs(test/security-sandbox): drop the backlog priority label
+- docs(test): remove the last backlog ids (I2, U2/U3)
+- docs(test/extra-tools): drop a backlog id from a section header
+- docs(test/cancel-ask): stop quoting a stale watchdog deadline
+- docs(test/send-runtime-block-lift): fix a header that contradicted its own fix
+- docs(test/tui-hints-locale): wrap two over-long comment lines
+- docs(test/tui-hints-locale): wrap the over-long note
+- docs(test): translate leftover Russian comments
+- docs(test/readme-built): say why a second readme is forbidden
+- docs(test/readme-built): say why a second readme is forbidden
+- docs(test/agent-loop): state why the first send is not an agent turn
+- docs(test/statusline-cap): untangle the settle-vs-exit note
+- docs(test/i18n-unused): drop the shouting prefix
+- docs(test/legacy-paste-marker): drop a time-relative word
+- docs(test): replace first-person narration with the subject
+- docs(test/continue-button): drop the first-person narration
+- docs(test/auto-compact): drop a pointer to the fixture value
+- docs(test/run-task): drop the refactor history from the header
+- docs(test/attach-flow-shared): keep only the why of the fake clock
+- docs(test/send-telemetry-nan-block): drop a case that lives in another test
+- docs(test/wsl): state the real reason instead of the CI setup
+- docs(test/agent-loop-robust): name the retry budget constant
+- docs(test/diff-large-file): stop quoting a removed source comment
+- docs(test/auth-login): trim a comment that restated its asserts
+- docs(agents): remove the last backlog ids from the root instructions
+- docs(scripts): remove backlog ids from scenario comments
+- docs(test/generation-incomplete): stop quoting a stale watchdog value
+- docs(test/cancel-ask): drop the runner version from the keep-alive note
+- docs(test/cli-flags): name the skip-list constant
+- docs(test/continue-button): name the real continue constant
+- docs(test/finished-answer-plain-json): name the real constants
+- docs(test/tool-name-resolution): drop the meta clause
+- docs(test/mcp-truncate-surrogate): finish the meta-narration cleanup
+- docs(test): drop meta-narration from test comments
+- docs(test/log-window): state the bug instead of narrating the test
+- docs(readme): mention /rewind next to /undo
+- docs(llms): regenerate llms-full.txt after the readme fixes
+- docs(readme): clarify the per-provider context window sentence
+- docs(readme): the Qwen send pause is 4 s, not 1 s
+- docs(readme): the context percentage is per provider, not always 1M
+- docs(readme): complete the CLI options block
+- docs(readme): list BashOutput and AskUser among the tools
+- docs(readme): make the slash-command list match SLASH_COMMANDS
+- docs(scripts): fix a typo in the build-readme usage line
+- docs(test/agent-loop-robust): fix a section header that contradicted the code
+- docs(test/i18n-unused): tighten the vacuously-green note
+- docs(test/attach-flow): drop a what-comment
+- docs(test/browser-login): drop a duplicated probe walkthrough
+- docs(scripts): document the postinstall contract
+- docs(test/agent-facing-english): point at the split i18n catalog
+- docs(test): remove backlog ids missed by the first sweep
+- docs(developing): refresh module sizes and drop backlog ids
+- docs(agents): drop backlog ids from the module map
+- docs(agents): the providers are three, with three profiles
+- docs(contributing): fix the provider list and the dev-mode description
+- docs(citation): sync the version and keep CITATION.cff updated on release
+- docs(readme): mention GLM in the provider section
+- docs(readme): fix three default/config facts (mouseScroll, telemetry, config write target)
+- docs(readme): state the real Node.js requirement (>= 22)
+- docs(design-notes): replace a backlog id with the actual reason
+- docs(scripts): translate a Russian header and drop backlog ids
+- docs(test/xml): prune and fix stale comments
+- docs(test/subagent): prune stale comments
+- docs(test/ssrf): prune stale comments
+- docs(test/skill): prune and fix stale comments
+- docs(test/mcp): prune stale comments and translate a leftover Russian note
+- docs(test/i18n): repair a corrupted word and prune stale comments
+- docs(test/glm): prune and fix stale comments
+- docs(test/editor): drop remaining backlog ids
+- docs(test/editor): prune and fix stale comments
+- docs(test/context): prune and fix stale comments
+- docs(test/config): prune and fix stale comments
+- docs(test/cli): prune and fix stale comments
+- docs(test/browser): prune and fix stale comments
+- docs(test/backlog): prune and fix stale comments
+- docs(test/answer-parse): prune and fix stale comments
+- docs(test/agent-loop): prune and fix stale comments
+- docs: add a text-audit protocol for an unattended loop run
+
+## [2.82.138] - 2026-10-25
+
+### Changed
+
+- docs(types): fix a stale provider count
+- docs(tui/widgets): prune a section divider
+- docs(tui): prune section dividers
+- docs(system-prompt): drop a backlog-id reference
+- docs(statusline): prune and fix stale comments
+- docs(status-command): prune and fix stale comments
+- docs(spinner): prune and fix stale comments
+- docs(shell): prune and fix stale comments
+- docs(sessions): prune and fix stale comments
+- docs(send-throttle): prune and fix stale comments
+- docs(send-telemetry): prune and fix stale comments
+- docs(send-runtime): prune and fix stale comments
+- docs(self-review): prune section dividers
+- docs(run-task): prune and fix stale comments
+- docs(qwen-ui): prune and fix stale comments
+- docs(qwen-net-capture): prune and fix stale comments
+- docs(qwen-chats): prune and fix stale comments
+- docs(qwen-browser): prune section dividers
+- docs(prompt): prune and fix stale comments
+- docs(permissions): prune and fix stale comments
+- docs(path-token): prune and fix stale comments
+- docs(net-capture): prune and fix stale comments
+- docs(mcp): prune and fix stale comments
+- docs(markdown): prune and fix stale comments
+- docs(limits-command): prune and fix stale comments
+- docs(input/suggest): prune and fix stale comments
+- docs(input/layout): drop a backlog-id reference
+- docs(input): prune backlog ids and section dividers
+- docs(index): prune section dividers
+- docs(i18n): prune and fix stale comments
+- docs(i18n): drop backlog-id references from common.ts comments
+- docs(goal): prune and fix stale comments
+- docs(glm-ui): prune and fix stale comments
+- docs(glm-net-capture): prune and fix stale comments
+- docs(glm-chats): prune and fix stale comments
+- docs(glm-browser): prune and fix stale comments
+- docs(glm-browser): prune and fix stale comments
+- docs(gitTools): prune and fix stale comments
+- docs(fsutil): prune and fix stale comments
+- docs(extraTools): prune and fix stale comments
+- docs(diff): prune and fix stale comments
+- docs(diagnostics): prune and fix stale comments
+- docs(deepseek-ui): prune and fix stale comments
+- docs(config): prune and fix stale comments
+- docs(config-menu): prune and fix stale comments
+- docs(config-live): prune and fix stale comments
+- docs(config-commands): prune and fix stale comments
+- docs(config-command): prune and fix stale comments
+- docs(commands): prune and fix stale comments
+- docs(code-blocks): prune and fix stale comments
+- docs(cli-args): prune and fix stale comments
+- docs(checkpoint): prune and fix stale comments
+- docs(changelog): prune and fix stale comments
+- docs(browser): prune and fix stale comments
+- docs(browser-pure): prune and fix stale comments
+- docs(browser-login): prune and fix stale comments
+- docs(browser-dom): prune and fix stale comments
+- docs(browser-chats): prune and fix stale comments
+- docs(banner): prune and fix stale comments
+- docs(backlog): prune and fix stale comments
+- docs(attachments): prune and fix stale comments
+- docs(attach-refs): prune and fix stale comments
+- docs(attach-flow): prune and fix stale comments
+- docs(answer-parse): prune and fix stale comments
+- docs(agent-loop): prune and fix stale comments
+
 ## [2.82.137] - 2026-10-24
 
 ### Changed

package/README.md

@@ -13,7 +13,7 @@
   <a href="https://www.npmjs.com/package/zames_pro"><img src="https://img.shields.io/npm/dm/zames_pro.svg" alt="npm downloads"></a>
   <a href="https://github.com/Viqto0r/zames_pro/actions/workflows/test.yml"><img src="https://github.com/Viqto0r/zames_pro/actions/workflows/test.yml/badge.svg" alt="tests"></a>
   <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT"></a>
-  <a href="package.json"><img src="https://img.shields.io/badge/node-%3E%3D20-brightgreen.svg" alt="Node.js"></a>
+  <a href="package.json"><img src="https://img.shields.io/badge/node-%3E%3D22-brightgreen.svg" alt="Node.js"></a>
   <a href="https://www.typescriptlang.org/"><img src="https://img.shields.io/badge/TypeScript-strict-3178c6.svg" alt="TypeScript"></a>
   <a href="CONTRIBUTING.md"><img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs welcome"></a>
 </p>
@@ -96,8 +96,8 @@ Key pieces:
 - **A persistent per-provider profile** (`~/.zames/profile` for DeepSeek,
   `~/.zames/qwen-profile` for Qwen) keeps you signed in; the headless
   User-Agent is patched so the site's CDN does not 403 the login.
-- **A send throttle** (15 s on DeepSeek, ~1 s on Qwen, which tolerates rapid
-  sends; GLM uses an adaptive pause that starts at 0) keeps the web chat's rate
+- **A send throttle** (15 s on DeepSeek, 4 s on Qwen, which tolerates a faster
+  pace; GLM uses an adaptive pause that starts at 0) keeps the web chat's rate
   limit happy during long tool-heavy runs.
 - **The agent is sandboxed** to the directory it was started in — no tool can
   read or write above it.
@@ -115,7 +115,8 @@ Key pieces:
 
 - **Tools like Claude Code / Codex** — `Read`, `Write`, `Edit`, `Bash`,
   `Glob`, `Grep`, plus `MultiEdit`, `ApplyPatch`, `LS`, `TodoWrite`, git and web
-  tools. Every edit is backed by `/undo`.
+  tools. Every edit is backed by `/undo`, and `/rewind` restores the whole
+  working tree from a checkpoint.
 - **Runs while you keep typing** — queue messages during a task; they run right
   after it, in the same chat (like typing during generation on the web).
 - **Plan mode** — `/plan` (or `--plan`) drops all mutating tools, so the agent
@@ -148,7 +149,7 @@ Key pieces:
 
 ## Requirements
 
-- Node.js >= 20
+- Node.js >= 22
 - An account on the chat you want to use — **DeepSeek** (`chat.deepseek.com`,
   the default), **Qwen** (`chat.qwen.ai`) or **GLM** (`chat.z.ai`). Qwen also
   works in guest mode for a few messages. On first launch zames asks for your login in the terminal
@@ -194,8 +195,8 @@ Credentials and toggles can also be edited from `/config`
 
 ## Switching providers (DeepSeek / Qwen / GLM)
 
-zames can drive either **DeepSeek** (`chat.deepseek.com`, the default) or
-**Qwen** (`chat.qwen.ai`):
+zames can drive **DeepSeek** (`chat.deepseek.com`, the default), **Qwen**
+(`chat.qwen.ai`) or **GLM** (`chat.z.ai`):
 
 ```bash
 /provider qwen      # switch to Qwen (persisted) — applied live, no restart
@@ -209,9 +210,10 @@ zames can drive either **DeepSeek** (`chat.deepseek.com`, the default) or
 Notes:
 
 - The switch is **live**: zames closes the current backend and opens the other
-  one in place, so no restart is needed. The two backends use **separate
+  one in place, so no restart is needed. The backends use **separate
   persistent profiles** (`~/.zames/profile` for DeepSeek, `~/.zames/qwen-profile`
-  for Qwen), so switching never signs the other one out.
+  for Qwen, `~/.zames/glm-profile` for GLM), so switching never signs the other
+  one out.
 - A chat id belongs to ONE backend, so the new provider opens a **fresh chat**.
   If the previous chat had messages they are summarized and posted as a
   handoff with the next task; an empty chat is switched silently.
@@ -230,10 +232,10 @@ Notes:
   solved programmatically). zames therefore launches GLM headed by default and
   prints a note about it; `--headless` still forces headless (sends will hit
   the captcha). `--headed` is accepted everywhere.
-- **Send telemetry**: every send is recorded in
+- **Send telemetry** (off by default): when enabled, every send is recorded in
   `~/.zames/logs/sends-<provider>.jsonl` (timing, mode flags, the outcome and
-  the server error — never the prompt or the answer). Turn it off with
-  `/config set browser.sendTelemetry false`. `/limits` shows the recent sends
+  the server error — never the prompt or the answer). Turn it on with
+  `/config set browser.sendTelemetry true`. `/limits` shows the recent sends
   and the current pause. GLM additionally uses an **adaptive pause**: it starts
   at 0 and backs off from a REAL rate limit.
 - **Warning**: automating a web chat may violate the service's terms of use and
@@ -295,11 +297,11 @@ The prompt is a small line editor with persistent history:
 Full-screen mode adds dialog navigation, so a long answer can be read and
 selected without leaving the terminal:
 
-- `ui.mouseScroll=false` (default) — the terminal owns the mouse: normal text
-  selection works and the wheel is inert (it never scrolls the input history —
-  history is arrow keys only).
-- `ui.mouseScroll=true` — the app consumes the wheel and scrolls the dialog;
-  selecting text then needs `Shift`+click (the TUI convention).
+- `ui.mouseScroll=true` (default) — the app consumes the wheel and scrolls the
+  dialog; selecting text then needs `Shift`+click (the TUI convention). The
+  wheel never scrolls the input history — history is arrow keys only.
+- `ui.mouseScroll=false` — the terminal owns the mouse again: normal text
+  selection works and the wheel is inert.
 - `PgUp` / `PgDn` — move up/down the dialog half a screen.
 - `Home` / `End` — jump to the very top / bottom of the dialog (only while the
   input line is empty; with text typed they move the caret as usual).
@@ -336,8 +338,11 @@ instead of staying silent.
 zames --task <task text>
 zames --chat <id>
 zames --new-chat
+zames --resume-last
 zames --resend-prompt
 zames --dir <path>
+zames --provider <deepseek|qwen|glm>
+zames --max-iter <n>
 zames --headless
 zames --headed
 zames --plan
@@ -368,15 +373,19 @@ zames --task "..." --output-format jsonl \
 
 The agent has the same style of tools as Claude Code / Codex CLI:
 
-- **File tools** — `Read`, `Write`, `Edit`, `Bash`, `Glob`, `Grep`. `Read`
-  returns raw content by default; pass `numbered=true` to get `cat -n`-style
-  line numbers (for reference only — do not paste them into `Edit`).
+- **File tools** — `Read`, `Write`, `Edit`, `Bash`, `BashOutput`, `Glob`,
+  `Grep`. `Read` returns raw content by default; pass `numbered=true` to get
+  `cat -n`-style line numbers (for reference only — do not paste them into
+  `Edit`). `Bash` takes `run_in_background`; `BashOutput` then polls or kills
+  that process.
 - **Extra tools** — `LS` (list a directory), `MultiEdit` (several edits to one
   file applied atomically), `TodoWrite` (session task checklist), `ApplyPatch`
   (multi-file patch in Codex's V4A format: `*** Begin Patch` … `*** End Patch`).
 - **Git** — `GitStatus`, `GitDiff`, `GitLog`, `GitShow`, `GitBranchList`,
   `GitAdd`, `GitCommit`, `GitPush`.
 - **Web** — `WebFetch`, `WebSearch`.
+- **Operator** — `AskUser` (a modal question with options; skipped in plan
+  mode so a plan is never interrupted).
 - **Service** — `respond` (final answer to the operator, ends the task).
 
 All file tools stay inside the working directory (sandbox). `Write`/`Edit` and
@@ -384,11 +393,12 @@ All file tools stay inside the working directory (sandbox). `Write`/`Edit` and
 
 ## Slash commands
 
-Type / in the prompt for hints (Tab completes). Besides the session and
-config commands (/new, /chats, /resume, /cd, /status, /config,
-/undo, /transcript, /mcp, /skills, /memory, /init, /reload,
-/debug-dom, /help, /exit) there are a few that mirror Claude Code /
-Codex CLI:
+Type / in the prompt for hints (Tab completes) — that list is always complete,
+`/help <command>` describes any single one. Besides the session and config
+commands (/new or /clear, /sessions, /chats, /resume-id, /last, /chat, /cd,
+/pwd, /status, /config, /undo, /undo-list, /rewind, /rewind-list, /transcript,
+/tasks, /mcp, /skills, /memory, /remember, /init, /reload, /debug-dom, /help,
+/exit) there are a few that mirror Claude Code / Codex CLI:
 
 - /diff [--staged] — show the working-tree git diff (--staged for the index).
 - /diffstat — a one-line change summary (`git diff --stat`).
@@ -450,11 +460,12 @@ tests`). /cron "<min> <hour> <dom> <month> <dow>" <task> — run on a schedule.
   current task.
 
 The token context is also shown live: the status line above the input has the
-spinner/text on the left and the context on the right (e.g. `125k · 13%`,
-percent of a 1M context). It is COLORED by fill level: green below 50%,
-yellow 50-80%, red above 80%. It comes from the provider's own token
-counter (DeepSeek's `accumulated_token_usage`, Qwen's `input_tokens`, GLM's
-`prompt_tokens`) and is
+spinner/text on the left and the context on the right (e.g. `125k · 13%`). The
+percentage is of the ACTIVE provider's window — 1M for DeepSeek, a per-model
+value for Qwen and GLM (`qwen.contextLimit` / `glm.contextLimit`) — and it is
+COLORED by fill level: green below 50%, yellow 50-80%, red above 80%.
+It comes from the provider's own token counter (DeepSeek's
+`accumulated_token_usage`, Qwen's `input_tokens`, GLM's `prompt_tokens`) and is
 hidden until the first answer delivers it.
 
 ## Project context, skills and memory
@@ -587,8 +598,9 @@ Examples:
 /config lang en
 ```
 
-Changes are written to the project `.zamesrc.json` and applied right away
-(where possible without a restart).
+Changes are written to the HOME config (`~/.zames/config.json`), NOT to the
+project `.zamesrc.json` — a personal toggle must not leak into git — and applied
+right away (where possible without a restart).
 
 ### Language
 
@@ -645,7 +657,7 @@ signed-in browser profile.
 **How do I install a terminal AI coding agent?**
 
 ```bash
-npm install -g zames_pro   # Node.js >= 20; Chromium is fetched automatically
+npm install -g zames_pro   # Node.js >= 22; Chromium is fetched automatically
 cd your-project
 zames
 ```
@@ -777,9 +789,9 @@ zames не вызывает API модели. Он запускает headless C
   `~/.zames/qwen-profile` у Qwen, `~/.zames/glm-profile` у GLM) держит вас
   залогиненным; User-Agent
   headless-браузера подменяется, чтобы CDN сайта не отдавал 403 на вход.
-- **Троттлинг отправки** (15 с у DeepSeek, ~1 с у Qwen, который спокойно
-  переносит частые отправки; у GLM — адаптивная пауза с нуля) щадит рейт-лимит
-  веб-чата во время долгих прогонов с инструментами.
+- **Троттлинг отправки** (15 с у DeepSeek, 4 с у Qwen, который спокойно
+  переносит более частый темп; у GLM — адаптивная пауза с нуля) щадит
+  рейт-лимит веб-чата во время долгих прогонов с инструментами.
 - **Агент запесочен** в директорию запуска — ни один инструмент не может
   читать или писать выше неё.
 
@@ -796,7 +808,8 @@ zames не вызывает API модели. Он запускает headless C
 
 - **Инструменты как в Claude Code / Codex** — `Read`, `Write`, `Edit`, `Bash`,
   `Glob`, `Grep`, плюс `MultiEdit`, `ApplyPatch`, `LS`, `TodoWrite`, git- и
-  веб-инструменты. Каждая правка подкреплена `/undo`.
+  веб-инструменты. Каждая правка подкреплена `/undo`, а `/rewind` возвращает
+  всё рабочее дерево к чекпойнту.
 - **Работает, пока вы печатаете** — сообщения, набранные во время задачи,
   встают в очередь и уходят сразу после неё, в тот же чат (как набор текста
   во время генерации на сайте).
@@ -832,7 +845,7 @@ zames не вызывает API модели. Он запускает headless C
 
 ## Требования
 
-- Node.js >= 20
+- Node.js >= 22
 - Аккаунт в нужном чате — **DeepSeek** (`chat.deepseek.com`, по умолчанию),
   **Qwen** (`chat.qwen.ai`) или **GLM** (`chat.z.ai`). Qwen также работает в
   гостевом режиме на несколько сообщений. При первом запуске zames спросит логин в терминале (и сохранит его
@@ -911,10 +924,10 @@ zames умеет работать с **DeepSeek** (`chat.deepseek.com`, по у
   программно её не пройти). Поэтому zames запускает GLM с окном по умолчанию и
   пишет об этом при старте; `--headless` по-прежнему форсирует headless
   (отправки будут упираться в капчу). `--headed` работает везде.
-- **Телеметрия отправок**: каждая отправка пишется в
-  `~/.zames/logs/sends-<provider>.jsonl` (тайминги, флаги режимов, исход и
-  ошибка сервера — без промптов и ответов). Отключается через
-  `/config set browser.sendTelemetry false`. Команда `/limits` показывает
+- **Телеметрия отправок** (по умолчанию выключена): когда включена, каждая
+  отправка пишется в `~/.zames/logs/sends-<provider>.jsonl` (тайминги, флаги
+  режимов, исход и ошибка сервера — без промптов и ответов). Включается через
+  `/config set browser.sendTelemetry true`. Команда `/limits` показывает
   последние отправки и текущую паузу. У GLM вдобавок **адаптивная пауза**: она
   начинается с 0 и растёт только после НАСТОЯЩЕГО лимита.
 - **Предупреждение**: автоматизация веб-чата может нарушать условия
@@ -978,11 +991,11 @@ zames
 В полноэкранном режиме добавляется навигация по диалогу, чтобы длинный ответ
 можно было прочитать и выделить не покидая терминал:
 
-- `ui.mouseScroll=false` (по умолчанию) — терминал владеет мышью: обычное
-  выделение текста работает, колесо инертно (и никогда не листает историю
-  ввода — история только стрелками).
-- `ui.mouseScroll=true` — приложение перехватывает колесо и скроллит диалог;
-  выделение текста тогда — `Shift`+клик (стандарт TUI).
+- `ui.mouseScroll=true` (по умолчанию) — приложение перехватывает колесо и
+  скроллит диалог; выделение текста тогда — `Shift`+клик (стандарт TUI). Колесо
+  никогда не листает историю ввода — история только стрелками.
+- `ui.mouseScroll=false` — мышью снова владеет терминал: обычное выделение
+  текста работает, колесо инертно.
 - `PgUp` / `PgDn` — вверх/вниз по диалогу на пол-экрана.
 - `Home` / `End` — прыжок в самый верх / низ диалога (только когда строка ввода
   пуста; при набранном тексте они двигают курсор, как обычно).
@@ -1020,8 +1033,11 @@ base64-блок с узнаваемой сигнатурой изображен
 zames --task <текст задачи>
 zames --chat <id>
 zames --new-chat
+zames --resume-last
 zames --resend-prompt
 zames --dir <path>
+zames --provider <deepseek|qwen|glm>
+zames --max-iter <n>
 zames --headless
 zames --headed
 zames --plan
@@ -1052,16 +1068,19 @@ zames --task "..." --output-format jsonl \
 
 У агента тот же стиль инструментов, что в Claude Code / Codex CLI:
 
-- **Файловые** — `Read`, `Write`, `Edit`, `Bash`, `Glob`, `Grep`. `Read` по
-  умолчанию отдаёт сырое содержимое; передайте `numbered=true`, чтобы получить
-  нумерацию строк в стиле `cat -n` (только для справки — не вставляйте её в
-  `Edit`).
+- **Файловые** — `Read`, `Write`, `Edit`, `Bash`, `BashOutput`, `Glob`,
+  `Grep`. `Read` по умолчанию отдаёт сырое содержимое; передайте
+  `numbered=true`, чтобы получить нумерацию строк в стиле `cat -n` (только для
+  справки — не вставляйте её в `Edit`). `Bash` принимает `run_in_background`,
+  а `BashOutput` затем опрашивает или убивает этот процесс.
 - **Дополнительные** — `LS` (список директории), `MultiEdit` (несколько правок
   одного файла атомарно), `TodoWrite` (чек-лист задач сессии), `ApplyPatch`
   (мультифайловый патч в формате V4A от Codex: `*** Begin Patch` … `*** End Patch`).
 - **Git** — `GitStatus`, `GitDiff`, `GitLog`, `GitShow`, `GitBranchList`,
   `GitAdd`, `GitCommit`, `GitPush`.
 - **Web** — `WebFetch`, `WebSearch`.
+- **Оператор** — `AskUser` (модальный вопрос с вариантами; в режиме плана не
+  предлагается, чтобы не прерывать план).
 - **Служебный** — `respond` (финальный ответ оператору, завершает задачу).
 
 Все файловые инструменты остаются внутри рабочей директории (песочница).
@@ -1070,10 +1089,12 @@ zames --task "..." --output-format jsonl \
 
 ## Слэш-команды
 
-Введите / в промпте для подсказок (Tab дополняет). Кроме команд сессии и
-конфига (/new, /chats, /resume, /cd, /status, /config, /undo, /transcript,
-/mcp, /skills, /memory, /init, /reload, /debug-dom, /help, /exit) есть
-несколько в духе Claude Code / Codex CLI:
+Введите / в промпте для подсказок (Tab дополняет) — этот список всегда полный,
+а `/help <команда>` описывает любую одну из них. Кроме команд сессии и конфига
+(/new или /clear, /sessions, /chats, /resume-id, /last, /chat, /cd, /pwd,
+/status, /config, /undo, /undo-list, /rewind, /rewind-list, /transcript,
+/tasks, /mcp, /skills, /memory, /remember, /init, /reload, /debug-dom, /help,
+/exit) есть несколько в духе Claude Code / Codex CLI:
 
 - /diff [--staged] — показать git-диф рабочего дерева (--staged для индекса).
 - /diffstat — сводка изменений одной строкой (`git diff --stat`).
@@ -1136,11 +1157,12 @@ zames --task "..." --output-format jsonl \
   текущей задачи.
 
 Контекст в токенах показывается и вживую: в строке статуса над вводом слева
-спиннер/текст, справа — контекст (например, `125k · 13%`, процент от 1M
-контекста). Он ОКРАШЕН по уровню заполнения: зелёный ниже 50%, жёлтый 50-80%,
-красный выше 80%. Значение приходит из счётчика токенов провайдера (у DeepSeek —
-`accumulated_token_usage`, у Qwen — `input_tokens`, у GLM — `prompt_tokens`) и
-скрыто до первого ответа.
+спиннер/текст, справа — контекст (например, `125k · 13%`). Процент считается от
+окна АКТИВНОГО провайдера — 1M у DeepSeek, у Qwen и GLM — своё значение на
+модель (`qwen.contextLimit` / `glm.contextLimit`). Он ОКРАШЕН по уровню
+заполнения: зелёный ниже 50%, жёлтый 50-80%, красный выше 80%. Значение
+приходит из счётчика токенов провайдера (у DeepSeek — `accumulated_token_usage`,
+у Qwen — `input_tokens`, у GLM — `prompt_tokens`) и скрыто до первого ответа.
 
 ## Контекст проекта, навыки и память
 
@@ -1272,8 +1294,9 @@ enum переключаются на месте; числа и строки от
 /config lang en
 ```
 
-Изменения пишутся в проектный `.zamesrc.json` и применяются сразу (где это
-возможно без перезапуска).
+Изменения пишутся в домашний конфиг (`~/.zames/config.json`), а НЕ в проектный
+`.zamesrc.json` — личный переключатель не должен попадать в git, — и применяются
+сразу (где это возможно без перезапуска).
 
 ### Язык
 
@@ -1332,7 +1355,7 @@ reasoning-модель при включённом «Deep thinking»). В Qwen
 **Как установить терминальный AI coding-агент?**
 
 ```bash
-npm install -g zames_pro   # Node.js >= 20; Chromium скачается автоматически
+npm install -g zames_pro   # Node.js >= 22; Chromium скачается автоматически
 cd your-project
 zames
 ```

package/dist/agent-loop.js

@@ -233,14 +233,10 @@ export async function runAgentLoop({ browser, tools, task, workdir, maxIteration
     // call but was not recognized (e.g. a DSML/XML form the strict parser
     // missed), the tool did NOT run and the echo is the only copy of the
     // call — it must be executed, not discarded as stale.
-    // const ranToolLastTurn follows the previous turn's actual effect.
     let lastTurnRanTool = false;
     let justRanTool = false;
     let watchdogRetries = 0;
     const MAX_WATCHDOG_RETRIES = 3;
-    // Retry budget for a browser.ask() TIMEOUT (not for content): the send did
-    // not come back in time. This is separate from unparsedRetries because a
-    // timeout is an infrastructure failure, not a model protocol violation.
     // Loop detection: the model sometimes repeats the SAME tool call with the
     // SAME arguments (e.g. Read the same file) turn after turn. There was no
     // explicit detector for that — the stale-answer guard only catches a
@@ -263,6 +259,9 @@ export async function runAgentLoop({ browser, tools, task, workdir, maxIteration
     // Set when the argument-error series hits the cap; appended to the message
     // AFTER the tool results are formatted (they rebuild `message`).
     let argErrNudge = '';
+    // Retry budget for a browser.ask() TIMEOUT (not for content): the send did
+    // not come back in time. Separate from unparsedRetries because a timeout is
+    // an infrastructure failure, not a model protocol violation.
     let afterToolRetries = 0;
     // toolsRanInTask: how many tools actually ran in THIS task. The protocol
     // guard uses it to tell "started, then slipped into chat mode" (a reasoning
@@ -1065,8 +1064,6 @@ export async function runAgentLoop({ browser, tools, task, workdir, maxIteration
                 const poll = setInterval(syncToolAbort, 100);
                 if (typeof poll.unref === 'function')
                     poll.unref();
-                // Time the tool: the transcript carries durationMs so /cost can
-                // show where the time goes (frequent Read→Edit cycles vs slow Bash).
                 const toolStart = Date.now();
                 try {
                     result = await tool.fn(call.args, { signal: toolAbort.signal });

package/dist/answer-parse.js

@@ -1,12 +1,9 @@
 import { parseXmlToolCalls } from './xml-toolcall.js';
 import { normText } from './browser-pure.js';
-// Pure, state-free helpers extracted from agent-loop.ts : the
-// tool-call PARSER (JSON / permissive / XML-DSML repair) and the small answer
-// heuristics. None of them touch the browser or the loop state, so this
-// module is safe to import on its own. agent-loop.ts imports the ones the
-// loop needs and RE-EXPORTS the public ones, so the existing API (tests import
-// parseToolCall / responseLooksLikeToolCall / truncateToolResult from './agent-loop.js')
-// is unchanged.
+// Pure, state-free helpers split out of agent-loop.ts: the tool-call PARSER
+// (JSON / permissive / XML-DSML repair) and the small answer heuristics. None
+// of them touch the browser or the loop state, so the module is safe to import
+// on its own; tests and agent-loop.ts import the functions from here directly.
 // Cap a tool result for the model, but make the truncation EXPLICIT: a bare
 // slice() silently hid the tail and the model had no idea it was looking at a
 // partial output (it would act on a half-read file/log).
@@ -537,11 +534,9 @@ function parseToolCallPermissive(text) {
     const tool = toolMatch[1];
     // The model occasionally puts the argument keys INLINE with "tool" —
     // {"tool": "Bash", "command": "..."} — with no "args" wrapper at all.
-    // The strict parser rejects it (no obj.args), and the permissive parser
-    // used to bail out too (indexOf('"args"') === -1). Such a call was
-    // reported as malformed and re-asked up to MAX_MALFORMED_RETRIES times;
-    // after the budget ran out the run stopped with the model's text as the
-    // final answer. Flatten the inline keys into args when "args" is absent.
+    // The strict parser rejects such a call (no obj.args); flatten the inline
+    // keys into args instead of letting the loop re-ask until it gives up and
+    // stops with the model's text as the final answer.
     if (text.indexOf('"args"') === -1) {
         const braceIdx = text.indexOf('{');
         if (braceIdx === -1)
@@ -730,16 +725,15 @@ function repairToolCallPreamble(text) {
     const m = t.match(/(?:^|[^A-Za-z0-9_])(?:\*\*)?(tool)(?:\*\*)?["'`\u2018\u2019\u201c\u201d]*\s*:/);
     if (!m || m.index === undefined)
         return null;
-    // We look for the start from the first quote/bracket around the key, otherwise from the word tool.
     let start = m.index;
     const brace = t.indexOf('{', Math.max(0, start - 1));
     if (brace !== -1 && brace < start)
         start = brace;
     let frag = t.slice(start);
-    // If the fragment does not start with `{` — we add it.
+    // The head lost its opening `{`, so rebuild one around the key below.
     if (!frag.startsWith('{')) {
-        // The key may have lost its opening quote: tool": → "tool".
-        // We trim the leading junk up to the word tool and normalize the key quotes.
+        // The key lost its opening quote (`tool":`), so drop the junk before it
+        // and re-add the quote.
         frag = frag.replace(/^[^A-Za-z0-9_]*/, '');
         frag = frag.replace(/^(?:\*\*)?(["'`\u2018\u2019\u201c\u201d]*)(tool)(?:\*\*)?["'`\u2018\u2019\u201c\u201d]*\s*:/, '"$2":');
         frag = '{' + frag;

package/dist/attach-refs.js

@@ -2,7 +2,7 @@ import fs from 'fs/promises';
 import path from 'path';
 import { looksLikeFilePath, isImageName } from './attachments.js';
 import { extractAtFileRefs } from './path-token.js';
-// Path resolution and `@file` reference inlining .
+// Path resolution and `@file` reference inlining.
 // Extracted from src/index.ts so the logic is unit-testable without the whole
 // CLI. This module touches only the filesystem (no browser/terminal).
 const NL = String.fromCharCode(10);
@@ -81,12 +81,12 @@ async function isInside(workdir, target) {
     const rel = path.relative(root, real);
     return !rel.startsWith('..') && !path.isAbsolute(rel);
 }
-// Per-file and total caps for `@path` inlining . A reference should SAVE
+// Per-file and total caps for `@path` inlining. A reference should SAVE
 // round-trips, not flood the context: a huge file is truncated with a note
 // telling the agent to read the rest itself.
 export const AT_REF_FILE_CAP = 60 * 1024;
 export const AT_REF_TOTAL_CAP = 200 * 1024;
-// Inline `@path` references found in a task text . Returns the augmented
+// Inline `@path` references found in a task text. Returns the augmented
 // text plus the list of files actually inlined (for the operator notice).
 // Unknown/unreadable references are left in place untouched -- they may be
 // part of the prose; we never fail the task over a missing file.