zames_pro 2.82.137 → 2.82.139

package/dist/qwen-browser.js

@@ -6,7 +6,7 @@
 // and the chat-id scheme. DeepSeekBrowser is already large; folding a second
 // site into it would make both harder to audit. The shared surface is the
 // ChatProvider interface (types.ts); the agent loop only needs BrowserLike and
-// never sees either concrete class.
+// never sees a concrete class.
 //
 // Verified against a live session (headless Chromium, guest + logged in):
 //   input  -> textarea.message-input-textarea
@@ -233,7 +233,6 @@ export class QwenBrowser {
     sendIntervalMs() {
         return this.minSendIntervalMs;
     }
-    // ---------- lifecycle ----------
     async launch() {
         if (await profileLooksLocked(QWEN_USER_DATA_DIR)) {
             if (this.debug)
@@ -487,7 +486,6 @@ export class QwenBrowser {
         }
         catch { }
     }
-    // ---------- login ----------
     // Are we signed in? Detected from the PAGE, the same way a human sees it: a
     // signed-out visitor has the header "Log in" / "Sign up" buttons, a signed-in
     // one shows the account menu instead. The `auths/refresh` API was the first
@@ -1005,7 +1003,6 @@ export class QwenBrowser {
         }
         return false;
     }
-    // ---------- chat management ----------
     async newChat() {
         const before = await this.getCurrentChatId();
         const btn = this.page.locator(NEW_CHAT_SELECTOR).first();
@@ -1272,7 +1269,6 @@ export class QwenBrowser {
     getLastTokenUsage() {
         return this._lastTokenUsage;
     }
-    // ---------- answer reading ----------
     async _readLastAnswerText() {
         if (this._netCapture && this._netCaptureAt >= this._lastSentAt) {
             return this._netCapture;
@@ -1346,7 +1342,6 @@ export class QwenBrowser {
         catch { }
         return false;
     }
-    // ---------- toggles (model thinking / search) ----------
     getToggleStatesSync() {
         return this._toggles;
     }
@@ -1523,7 +1518,6 @@ export class QwenBrowser {
         }
         catch { }
     }
-    // ---------- diagnostics ----------
     async dumpDom(filePath) {
         if (!this.page)
             throw new Error('qwen: browser not launched');
@@ -1566,7 +1560,6 @@ export class QwenBrowser {
     chatUrl(id) {
         return chatUrl(id);
     }
-    // ---------- ask ----------
     async _waitForSendSlot(agent) {
         if (!agent)
             return;

package/dist/qwen-chats.js

@@ -84,7 +84,6 @@ export function scrapeQwenChatMessages(opts) {
     }
     return out;
 }
-// ---------- API payload parsers (pure, unit-tested) ----------
 /**
  * Parse the chat list from `GET /api/v2/chats/?page=1&exclude_project=true`.
  * The shape has drifted between builds, so accept several:

package/dist/qwen-net-capture.js

@@ -223,13 +223,10 @@ export function isFinishedWithoutAnswer(body) {
     return extractFromSse(b) === '';
 }
 // True when the body carries Qwen's rate-limit / busy notice, so ask() can
-// back off instead of waiting out the deadline. Matched against the RAW body.
-// The classifier runs against the RAW body, so a phrase like `please try again
-// later` would also match a NORMAL answer (the model writing about retry
-// logic) and make ask() back off on a good turn. A real notice arrives in an
-// ERROR payload (`event: error` / `"type":"error"`) or as a code; answer text
-// lives in `choices[].delta.content`. We therefore only inspect the body when
-// it is NOT a plain answer stream, or when it carries no answer content.
+// back off instead of waiting out the deadline. The classifier runs against the
+// RAW body, where a phrase like `please try again later` also matches a NORMAL
+// answer (the model writing about retry logic) and made ask() back off on a
+// good turn. So it only counts an ERROR payload or a body with NO answer text.
 export function isRateLimitText(body) {
     const b = String(body || '');
     if (!b)

package/dist/qwen-ui.js

@@ -174,9 +174,6 @@ export const STATUS_RE = /^(thinking|searching|generating|thinking completed|о
 // Qwen's rate-limit / busy notices (best-effort; the toast may be short-lived).
 export const RATE_LIMIT_RE = /too many requests|rate limit|too frequent|please try again later|слишком часто/i;
 export const SERVER_BUSY_RE = /server is busy|service unavailable|try again later/i;
-// ---------- toggles ----------
-// The "Auto" thinking/search toggle and the mode selector. Read-only probing
-// support; the model's thinking mode is set via config when supported.
 // ---------- toggles (thinking mode / web search) ----------
 // Qwen exposes thinking as a MODE dropdown (`.qwen-thinking-selector`, label
 // "Auto" by default) with options Auto / Thinking / Fast — NOT a boolean

package/dist/run-task.js

@@ -330,7 +330,7 @@ export async function runTask(deps, browser, tools, taskText, workdir, opts, att
         });
     try {
         // Set when the loop ends without a real answer (iteration limit / watchdog)
-        // so the one-shot mode can exit non-zero. See N5.
+        // so the one-shot mode can exit non-zero.
         let failure = null;
         // The machine-readable reason for the last task's outcome.
         let outcomeKind = 'ok';
@@ -351,7 +351,7 @@ export async function runTask(deps, browser, tools, taskText, workdir, opts, att
         // Calling it here made the spinner run for the whole pre-send phase (chat
         // creation, throttle wait) with no generation in flight.
         while (true) {
-            // T7: per-task summary (duration + number of tool calls + tokens).
+            // Per-task summary: duration, number of tool calls and tokens spent.
             const taskStart = Date.now();
             // Token delta for THIS task: accumulated_token_usage is cumulative for
             // the whole chat, so the per-task spend is after - before. Null when the
@@ -461,8 +461,8 @@ export async function runTask(deps, browser, tools, taskText, workdir, opts, att
             else {
                 outcomeKind = 'ok';
             }
-            // T7: one summary line per task (duration + tool calls + tokens spent).
-            // Printed even on an abort, so the operator sees what happened.
+            // One summary line per task, printed even on an abort, so the operator
+            // sees what happened.
             const tokensAfter = getTokenUsage ? getTokenUsage() : null;
             const tokenDelta = typeof tokensBefore === 'number' && typeof tokensAfter === 'number'
                 ? Math.max(0, tokensAfter - tokensBefore)

package/dist/self-review.js

@@ -122,7 +122,6 @@ async function copyContextFiles(srcDir, snapDir) {
         }
     }
 }
-// ---------- /self-review ----------
 export async function selfReview({ browser, focus, transcript, locale, }) {
     const t = translator(locale);
     const stamp = new Date().toISOString().replace(/[:.]/g, '-');
@@ -190,7 +189,6 @@ export async function selfReview({ browser, focus, transcript, locale, }) {
     console.log();
     return { snapDir, reportPath, changed };
 }
-// ---------- /self-diff ----------
 export async function selfDiff({ name, locale, }) {
     const t = translator(locale);
     const snapDir = path.join(SNAP_ROOT, name);
@@ -218,7 +216,6 @@ export async function selfDiff({ name, locale, }) {
         console.log(theme.system(t('self.no_diff')));
     }
 }
-// ---------- /self-apply ----------
 export async function selfApply({ name, locale, }) {
     const t = translator(locale);
     const snapDir = path.join(SNAP_ROOT, name);
@@ -247,7 +244,6 @@ export async function selfApply({ name, locale, }) {
     console.log(theme.system(t('self.backup', { dir: backupDir })));
     console.log(theme.warn('\n' + t('self.restart_hint') + '\n'));
 }
-// ---------- /self-list ----------
 export async function selfList({ locale, } = {}) {
     const t = translator(locale);
     const snapRoot = path.join(SNAP_ROOT);
@@ -285,7 +281,6 @@ export async function selfList({ locale, } = {}) {
     console.log();
     console.log(theme.system(t('self.list_commands') + '\n'));
 }
-// ---------- helpers ----------
 async function diffFiles(origDir, newDir) {
     const files = await listTsFiles(newDir).catch(() => []);
     const changed = [];

package/dist/send-runtime.js

@@ -78,11 +78,9 @@ export class SendRuntime {
         if (typeof extra.retryAfterMs === 'number') {
             e.retryAfterMs = extra.retryAfterMs;
         }
-        // A SUCCESS after a rate limit IS the lift of that block. onBlockLifted()
-        // was the only producer of `blockMs`, but no provider's ask() calls it (a
-        // rate limit is retried IN PLACE and the retry simply succeeds), and the
-        // fold below clears `blockedAt` first. The measured duration is therefore
-        // taken HERE, before the state is folded; it is attached to the SAME event
+        // A SUCCESS after a rate limit IS the lift of that block: the retry happens
+        // IN PLACE and simply succeeds. The duration is therefore measured HERE,
+        // before the fold below clears `blockedAt`, and attached to the SAME event
         // line, so one block still yields exactly one sample.
         let blockMs;
         if (outcome === 'ok' &&
@@ -101,11 +99,9 @@ export class SendRuntime {
             this.state = { ...this.state, blocked: true, blockedAt: this.now() };
         }
         if (outcome === 'rate_limit') {
-            // The block START is only known AFTER the fold above (the adaptive path
-            // sets it there). The event itself carries NO duration: a rate-limit
-            // send is not the END of the block, so any value measured here is a
-            // lower bound that would then be averaged together with the real
-            // duration written by onBlockLifted — the same block counted TWICE.
+            // The event carries NO duration: a rate-limit send is not the END of the
+            // block, so a value measured here would be averaged together with the
+            // real duration measured at the lift — the same block counted TWICE.
             if (!this.state.blockedAt) {
                 this.state = { ...this.state, blocked: true, blockedAt: this.now() };
             }

package/dist/send-telemetry.js

@@ -51,14 +51,12 @@ export function summarizeSends(events, now = Date.now()) {
         const age = now - t;
         return age >= 0 && age <= ms;
     }).length;
-    // `blockMs` may arrive as a NUMBER (the writer) or a string (an older
-    // build, a hand-edited file): a numeric string is accepted so the average
-    // is not silently 0 for a file that records the block.
     const blocks = events
-        // `Number(null)`/`Number(undefined)` — 0/NaN, and 0 IS a finite
-        // non-negative number: an event that carries no block duration (the
-        // rate-limit event only records `blockedAt`) was averaged as a ZERO-length
-        // block, halving the reported average. Only a REAL value counts.
+        // `blockMs` may arrive as a NUMBER (the writer) or a string (an older
+        // build, a hand-edited file), so it is coerced. A missing value must NOT
+        // become 0: 0 is a finite non-negative number, and an event without a
+        // block duration (the rate-limit event only records `blockedAt`) was
+        // averaged as a ZERO-length block, halving the reported average.
         .map((e) => e.blockMs === null || e.blockMs === undefined ? NaN : Number(e.blockMs))
         // A finite value is not enough: the SUM of many large durations overflows
         // a JS number (two `Number.MAX_VALUE` entries add up to Infinity), so the

package/dist/send-throttle.js

@@ -39,11 +39,10 @@ function prune(recent, now, windowMs) {
  */
 export function nextWaitMs(state, lastSentAt, now) {
     if (state.forcedWaitMs > 0) {
-        // A forced wait must EXPIRE: a long Retry-After used to block every
-        // send forever (the check was `> 0` only), until another event cleared
-        // it. With the request stamp the remaining time is exact; without one
-        // (a caller-built or restored state) the wait is reported ONCE, from
-        // the current call, and expires on the next.
+        // A forced wait must EXPIRE: with only `forcedWaitMs > 0` a long
+        // Retry-After blocked every send until another event cleared it. The
+        // request stamp makes the remaining time exact; without one (a caller-built
+        // or restored state) the wait is reported ONCE, from the current call.
         if (state.forcedWaitAt) {
             const left = state.forcedWaitMs - (now - state.forcedWaitAt);
             return left > 0 ? left : 0;

package/dist/sessions.js

@@ -133,13 +133,12 @@ function writeIndex({ id, workdir }) {
     }
     catch { }
 }
-// The last session for the working directory. If there is none —
-// we return the last session overall (useful when launched from a new place).
-// The last session for the working directory, restricted to `provider` when
-// given. A chat id only exists on ITS backend, so restoring a DeepSeek chat
-// while the active provider is Qwen (or vice versa) would fail to open — the
-// filter makes auto-restore and /last pick the right one (and fall back to the
-// global last only within the same provider).
+// The last session for the working directory (the last one overall when the
+// directory has none — useful when launched from a new place), restricted to
+// `provider` when given. A chat id only exists on ITS backend, so restoring a
+// DeepSeek chat while the active provider is Qwen (or vice versa) would fail to
+// open; the filter makes auto-restore and /last pick the right one, and fall
+// back to the global last only within the same provider.
 export function loadLastSession(workdir = '', provider) {
     try {
         const index = JSON.parse(fs.readFileSync(INDEX_FILE, 'utf-8'));

package/dist/spinner.js

@@ -152,10 +152,9 @@ export function createSpinner(locale = 'ru') {
             }
             startThinking();
         },
-        // The agent is waiting out the send-interval pause before a real send.
-        // Show it as an ANIMATED status line with the remaining seconds, so the
-        // spinner keeps moving during the pause (previously a static console line
-        // was printed and the dots stayed frozen).
+        // The agent is waiting out the send-interval pause before a real send: an
+        // ANIMATED status with the remaining seconds, so the spinner keeps moving
+        // (a static line made the pause look frozen).
         sendPause: (seconds) => {
             if (pending)
                 return;

package/dist/statusline.js

@@ -58,10 +58,6 @@ export function runStatusLineCommand(workdir, command, info, timeoutMs = 4000) {
             // (the row overflows and the cursor arithmetic drifts).
             resolve(clipBadge(first));
         };
-        // Only the FIRST LINE is shown, so there is no reason to keep collecting a
-        // big blob: a chatty command (a JSON dump, `ls -R`) would grow `out`
-        // unboundedly and the status row then repainted megabytes. Stop appending
-        // once a short line is buffered (the rest of that line does not matter).
         const timer = setTimeout(() => {
             try {
                 if (process.platform !== 'win32' && child.pid) {
@@ -74,15 +70,15 @@ export function runStatusLineCommand(workdir, command, info, timeoutMs = 4000) {
             catch { }
             finish();
         }, timeoutMs);
-        // A status line is a short badge: cap what is buffered so a chatty
-        // command cannot grow it (and the rendered row) without bound.
+        // Only the FIRST line is shown and the status line is a short badge, so the
+        // buffer is capped: a chatty command (a JSON dump, `ls -R`) would otherwise
+        // grow `out` and make the status row repaint megabytes on every tick.
         const MAX_OUT = 400;
         child.stdout?.on('data', (c) => {
             if (out.length >= MAX_OUT)
                 return;
-            // A chunk can be huge (one 64 KB read); clip it to the remaining space
-            // so the buffer never exceeds MAX_OUT. An unbounded `out` made the
-            // status row repaint megabytes on every tick.
+            // A chunk can be huge (one 64 KB read): clip it to the remaining space so
+            // the buffer never exceeds MAX_OUT.
             out += c.toString().slice(0, MAX_OUT - out.length);
         });
         child.on('error', () => {

package/dist/system-prompt.js

@@ -124,7 +124,7 @@ export function renderContextSection(context) {
                 f.content +
                 '\n';
     }
-    // B6: nested AGENTS.md/MEMORY.md from the directories this task touches.
+    // Nested AGENTS.md/MEMORY.md from the directories this task touches.
     // Deliberately a SEPARATE section: these apply only to part of the tree and
     // must not be mistaken for project-wide rules.
     for (const f of context.scopedAgents || []) {

package/dist/tui/widgets.js

@@ -1,6 +1,5 @@
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 import { Box, Text } from 'ink';
-// ---- palette (kept in one place so every menu is consistent) ----
 export const UI = {
     accent: '#c8b06a',
     accentDim: '#7a6b45',

package/llms-full.txt

@@ -80,8 +80,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.
@@ -99,7 +99,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
@@ -132,7 +133,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
@@ -178,8 +179,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
@@ -193,9 +194,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.
@@ -214,10 +216,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
@@ -279,11 +281,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).
@@ -320,8 +322,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
@@ -352,15 +357,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
@@ -368,11 +377,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`).
@@ -434,11 +444,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
@@ -571,8 +582,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
 
@@ -629,7 +641,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
 ```

package/llms.txt

@@ -20,7 +20,7 @@ LLM-friendly map of the project. Everything below is plain Markdown.
 - **Supported backends:** DeepSeek (`chat.deepseek.com`, default), Qwen
   (`chat.qwen.ai`), GLM (`chat.z.ai`). Live switch with
   `/provider <deepseek|qwen|glm>`; each backend keeps its own browser profile.
-- **Language / stack:** TypeScript (strict), Node.js >= 20, Playwright,
+- **Language / stack:** TypeScript (strict), Node.js >= 22, Playwright,
   Ink/React TUI, MCP client.
 - **License:** MIT. **Not affiliated** with DeepSeek, Alibaba or Zhipu AI.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zames_pro",
-  "version": "2.82.137",
+  "version": "2.82.139",
   "description": "Terminal coding agent that drives a real browser to chat with DeepSeek, Qwen and other web LLMs — no API key required. Reads and edits files, runs commands, commits to git, like Claude Code / Codex CLI.",
   "type": "module",
   "bin": {

package/scripts/postinstall.mjs

@@ -1,3 +1,8 @@
+// Post-install step: fetch the Chromium build Playwright drives and, on a
+// Linux box that needs it, its system libraries. It runs BEFORE tsx is
+// guaranteed to be installed, so it stays a plain .mjs script. Every failure
+// is a WARNING, never a non-zero exit: a missing browser must not break
+// `npm install`, and the warning names the manual command to run instead.
 import { spawnSync } from 'node:child_process'
 
 const NL = String.fromCharCode(10)