zames_pro 2.82.139 → 2.82.141

package/dist/i18n/mcp.js

@@ -1,8 +1,8 @@
 // MCP server messages.
 export const mcpMessages = {
     'help.cmd.mcp': {
-        ru: '/mcp                     показать MCP-серверы и их инструменты',
-        en: '/mcp                     show MCP servers and their tools',
+        ru: '/mcp                     MCP-серверы: число инструментов, ошибки и предупреждения',
+        en: '/mcp                     MCP servers: tool count, errors and warnings',
     },
     'mcp.loaded': {
         ru: 'MCP: подключено инструментов {n} ({servers})',
@@ -21,15 +21,21 @@ export const mcpMessages = {
         en: 'No MCP servers configured.',
     },
     'mcp.hint': {
-        ru: 'Добавь ~/.zames/mcp.json или <project>/.zames/mcp.json.',
-        en: 'Add ~/.zames/mcp.json or <project>/.zames/mcp.json.',
+        ru: 'Добавь ~/.zames/mcp.json, <project>/.zames/mcp.json или <project>/.mcp.json.',
+        en: 'Add ~/.zames/mcp.json, <project>/.zames/mcp.json or <project>/.mcp.json.',
     },
     'mcp.title': {
         ru: 'MCP-серверы (инструментов: {n}):',
         en: 'MCP servers ({n} tools):',
     },
+    'mcp.floating': {
+        ru: 'MCP-сервер «{v}» использует плавающую версию (@latest/@next); закрепите точную версию, чтобы набор инструментов не менялся между запусками.',
+        en: 'MCP server "{v}" uses a floating version (@latest/@next); pin an exact version so the tool set does not change between runs.',
+    },
     'mcp.status_error': { ru: '(ошибка: {v})', en: '(error: {v})' },
-    'status.mcp': { ru: 'MCP-инструменты: {v}', en: 'MCP tools: {v}' },
+    // `{v}` is a COUNT (or 'unknown' when no pool is configured) — not a
+    // list of tool names, so the label must not read as one.
+    'status.mcp': { ru: 'MCP-инструментов: {v}', en: 'MCP tools: {v}' },
     'status.toggles': {
         ru: 'Размышление: {think} · Поиск: {search}',
         en: 'Deep thinking: {think} · Search: {search}',

package/dist/i18n/prompt.js

@@ -1,8 +1,11 @@
 // System-prompt fragments.
 export const promptMessages = {
+    // AGENT-FACING: the model reads this, so neither locale may carry Cyrillic
+    // prose (see AGENTS.md "Language policy"). Only the LANGUAGE NAME differs,
+    // which is what actually steers the answer language.
     'prompt.answer_language': {
-        ru: 'ВАЖНО: отвечай оператору на русском языке. Весь текст в поле message инструмента respond, а также любые пояснения — на русском.',
-        en: 'IMPORTANT: reply to the operator in English. All text in the respond tool message field, and any explanations, must be in English.',
+        ru: 'IMPORTANT: answer the operator in Russian. All text in the message field of the respond tool, and any explanations, must be in Russian.',
+        en: 'IMPORTANT: answer the operator in English. All text in the message field of the respond tool, and any explanations, must be in English.',
     },
     // The hard "ONLY TOOL CALLS" block. All prose around a tool call is a
     // protocol violation: the operator never sees it (only tool calls and the
@@ -10,7 +13,10 @@ export const promptMessages = {
     // stop DeepSeek from generating it INSIDE its chat with code (that is the
     // model's output); we can only forbid it by prompt and hide it here.
     'prompt.only_tool_calls': {
-        ru: '## ТОЛЬКО ВЫЗОВЫ ИНСТРУМЕНТОВ (жёсткое правило)\n\nОбщайся с оператором ТОЛЬКО через вызовы инструментов. Любой обычный текст — объяснения, планы, рассуждения, комментарии, извинения, приветствия, заголовки, списки, markdown, эмодзи — ЗАПРЕЩЁН. Он не читается и считается ошибкой.\n\nТВОЙ ЕДИНСТВЕННЫЙ ВЫВОД — вызов инструмента. В каждом ответе ровно один JSON-объект вызова (или массив независимых вызовов), без единого слова до и после.\n\nНЕЛЬЗЯ писать: «сейчас сделаю», «давай посмотрим», «проверю», планы, объяснения, итоги между шагами.\n\nМОЖНО только вызов инструмента и, в самом конце, когда задача выполнена, respond с итогом.\n\nЕдинственное место, где допускается текст, — поле message внутри respond, и только в самом конце.',
+        // AGENT-FACING: the model reads this, so BOTH locales carry the English
+        // text (see AGENTS.md "Language policy"): a Russian operator still gets an
+        // English protocol block, and the answer LANGUAGE is set separately above.
+        ru: '## ONLY TOOL CALLS (hard rule)\n\nTalk to the operator ONLY through tool calls. Any plain text — explanations, plans, reasoning, comments, apologies, greetings, headings, lists, markdown, emoji — is FORBIDDEN. It is not read and counts as an error.\n\nYOUR ONLY OUTPUT is a tool call. Each turn contains exactly one JSON tool-call object (or an array of independent calls), with not a single word before or after.\n\nYou MUST NOT write: "I will now...", "let us look...", "let me check", plans, explanations, progress notes between steps.\n\nALLOWED: only a tool call and, at the very end, when the task is done, respond with the summary.\n\nThe only place where text is allowed is the message field inside respond, and only at the very end.',
         en: '## ONLY TOOL CALLS (hard rule)\n\nTalk to the operator ONLY through tool calls. Any plain text — explanations, plans, reasoning, comments, apologies, greetings, headings, lists, markdown, emoji — is FORBIDDEN. It is not read and counts as an error.\n\nYOUR ONLY OUTPUT is a tool call. Each turn contains exactly one JSON tool-call object (or an array of independent calls), with not a single word before or after.\n\nYou MUST NOT write: "I will now...", "let us look...", "let me check", plans, explanations, progress notes between steps.\n\nALLOWED: only a tool call and, at the very end, when the task is done, respond with the summary.\n\nThe only place where text is allowed is the message field inside respond, and only at the very end.',
     },
 };

package/dist/i18n/qwen.js

@@ -3,8 +3,8 @@
 // so provider-specific wording has one home.
 export const qwenMessages = {
     'qwen.guest_mode': {
-        ru: 'Qwen: вход не выполнен, работаю в гостевом режиме (≈10 сообщений в сутки, без вложений). Войдите через /provider login или запустите с --headed.',
-        en: 'Qwen: not signed in, running in guest mode (~10 messages/day, no attachments). Log in via /provider login or launch with --headed.',
+        ru: 'Qwen: вход не выполнен, работаю в гостевом режиме (суточная квота гостя ограничена, вложения недоступны). Войдите через /provider login (он сам откроет видимое окно) или запустите с --headed.',
+        en: 'Qwen: not signed in, running in guest mode (the guest daily quota is limited, attachments are unavailable). Log in via /provider login (it opens a visible window itself) or launch with --headed.',
     },
     'qwen.login_email_prompt': {
         ru: 'Email для входа в Qwen{def}: ',

package/dist/i18n/self-review.js

@@ -177,6 +177,10 @@ export const selfReviewMessages = {
         ru: 'Сохранённых сессий нет. Они появятся после первой задачи/чата.',
         en: 'No saved sessions. They appear after the first task/chat.',
     },
+    'sessions.none_here': {
+        ru: 'Для этого каталога сохранённых сессий нет — сначала выполните здесь задачу.',
+        en: 'No saved session for this directory — run a task here first.',
+    },
     'sessions.restore_hint': {
         ru: 'Восстановить: /resume-id <id> (полный id) или выбери сессию в списке /sessions.',
         en: 'Restore: /resume-id <id> (full id) or pick a session from the /sessions list.',

package/dist/i18n/spinner.js

@@ -25,26 +25,31 @@ export const spinnerMessages = {
     },
     'editor.more': { ru: '…ещё {n}', en: '…{n} more' },
     'editor.page_hint': {
-        ru: '(Ctrl+N/Ctrl+P — вверх/вниз, Tab — вставить)',
-        en: '(Ctrl+N/Ctrl+P — up/down, Tab — insert)',
+        ru: '(Ctrl+N/Ctrl+P — выбор, Tab — вставить)',
+        en: '(Ctrl+N/Ctrl+P — select, Tab — insert)',
     },
     'editor.answer': { ru: '● Ответ', en: '● Answer' },
     // Shown in the full-screen log viewport before the first turn, so a fresh
     // chat is not a blank screen with no hint of what to do.
     'editor.empty_hint': {
-        ru: 'Напишите задачу и нажмите Enter. /help — команды, Ctrl+J — новая строка.',
-        en: 'Type a task and press Enter. /help for commands, Ctrl+J for a new line.',
+        ru: 'Напишите задачу и нажмите Enter. /help — команды, \\ + Enter — новая строка.',
+        en: 'Type a task and press Enter. /help for commands, \\ + Enter for a new line.',
     },
     // One-line key hint UNDER the input box (full-screen mode). Two variants:
     // with in-app wheel scroll the mouse belongs to the app, so selection needs
     // Shift; without it the terminal keeps the mouse and the wheel is inert.
+    // Kept SHORT: the row is truncated, and the long "up/down" / "top/bottom"
+    // tails pushed the MODE-specific part (wheel vs inert) off a narrow screen.
     'editor.keys_hint': {
-        ru: 'выделение — Shift+клик · колесо — скролл · PgUp/PgDn — вверх/вниз · Home/End — в начало/конец',
-        en: 'select — Shift+click · wheel — scroll · PgUp/PgDn — up/down · Home/End — top/bottom',
+        // The wheel belongs to the app ONLY in this mode; in SELECT mode the
+        // terminal keeps it (see useMouseWheel.ts), so that hint never advertises
+        // a wheel scroll.
+        ru: 'колесо — скролл · выделение — Shift+клик · Esc — стоп · PgUp/PgDn · Home/End',
+        en: 'wheel — scroll · select — Shift+click · Esc — stop · PgUp/PgDn · Home/End',
     },
     'editor.keys_hint_select': {
-        ru: 'выделение — мышью · PgUp/PgDn — вверх/вниз · Home/End — в начало/конец',
-        en: 'select — drag · PgUp/PgDn — up/down · Home/End — top/bottom',
+        ru: 'выделение — мышью · колесо инертно · Esc — стоп · PgUp/PgDn · Home/End',
+        en: 'select — drag · wheel inert · Esc — stop · PgUp/PgDn · Home/End',
     },
     // Reverse search (Ctrl+R) status line. The query may be empty.
     'editor.search_prompt': {

package/dist/index.js

@@ -20,7 +20,7 @@ import { LineEditor } from './input.js';
 import { TuiEditor } from './tui/TuiEditor.js';
 import { promptOnce } from './prompt.js';
 import { parseImagePaste, extForMime, saveToTemp, guessMime, formatSize, readClipboardImageDetailed, sniffMime, readWindowsClipboardFiles, hasClipboardTool, writeClipboardText, contentHash, } from './attachments.js';
-import { loadConfig, DEFAULTS, CONFIG_PATHS, ZAMES_HOME, CONFIG_SCHEMA, getByPath, validateConfigValue, writeConfigValue, resetConfigValue, providerAskDeadlineMs, } from './config.js';
+import { loadConfig, DEFAULTS, CONFIG_PATHS, ZAMES_HOME, CONFIG_SCHEMA, getByPath, validateConfigValue, writeConfigValue, resetConfigValue, providerAskDeadlineMs, shadowedConfigKeys, } from './config.js';
 import { runConfigMenu } from './config-menu.js';
 import { runConfigMenuInk } from './tui/run-config-menu.js';
 import { formatConfigList } from './config-commands.js';
@@ -126,6 +126,17 @@ let currentLocale = isLocale(config.ui?.locale)
 // Translation: reads currentLocale at call time, so a language change takes
 // effect immediately, without a restart (for lines printed afterwards).
 const t = (key, params) => translate(currentLocale)(key, params);
+// A project `.zamesrc.json` wins over the HOME config, so a key it ALSO sets
+// silently defeats `/config set` — the value looks saved and comes back stale
+// after a restart (the reported "language resets to English" case). Say it at
+// startup, before a task, instead of letting the operator hunt for it.
+const shadowedAtStartup = shadowedConfigKeys();
+if (shadowedAtStartup.length) {
+    console.error(theme.warn(t('cfg.shadowed', {
+        file: CONFIG_PATHS.PROJECT_CONFIG,
+        keys: shadowedAtStartup.join(', '),
+    })));
+}
 // Headless is the default. --headed forces a visible window (useful for the
 // first sign-in or debugging the DOM). --headless keeps it explicit.
 // DeepSeek/Qwen run headless by default; GLM CANNOT: z.ai answers a headless
@@ -474,9 +485,9 @@ ${theme.bold(t('help.while_working'))}
   ${t('help.key.search')}
   ${t('help.key.words')}
   ${t('help.key.undo')}
+  ${t('help.key.clear_screen')}
   ${t('help.key.slash')}
   ${t('help.key.newline')}
-  ${t('help.key.backslash')}
   ${t('help.key.attach')}
   ${t('help.key.esc')}
   ${t('help.key.bang')}
@@ -692,7 +703,7 @@ async function resolveWorkdir() {
     const dir = explicitDir ? path.resolve(explicitDir) : process.cwd();
     const stat = await fs.stat(dir).catch(() => null);
     if (!stat || !stat.isDirectory()) {
-        throw new Error(t('msg.not_dir', { v: dir }));
+        throw new Error(t('cd.not_dir', { v: dir }));
     }
     return dir;
 }
@@ -1052,7 +1063,7 @@ async function main() {
                 console.error(theme.warn(t('mcp.server_error', { name: srv.name, error: srv.error })));
         }
         for (const w of st.warnings)
-            console.error(theme.warn(w));
+            console.error(theme.warn(t(w.key, w.params)));
     }
     catch (e) {
         console.error(theme.warn(t('mcp.load_failed', { v: e.message })));
@@ -1213,6 +1224,7 @@ async function main() {
     const recoverFromContextLimit = async () => {
         const res = await performCompact({
             browser,
+            providerLabel: providerLabel(config.provider),
             currentChatId,
             workdir: currentWorkdir,
             locale: currentLocale,
@@ -1349,10 +1361,23 @@ async function main() {
     // never bypassing the send throttle). Started lazily on the first job.
     const scheduler = new Scheduler();
     let scheduleTimer = null;
+    // Ctrl+C on an idle agent EXITS the process. Without this latch a /loop job
+    // whose task was interrupted (and every later fire) would be dropped into
+    // the queue while nobody waits for it, and each tick printed "fired" into a
+    // dying terminal. A loop is meant to outlive a single task, not the agent.
+    let shuttingDown = false;
+    const stopScheduleTicker = () => {
+        if (scheduleTimer) {
+            clearInterval(scheduleTimer);
+            scheduleTimer = null;
+        }
+    };
     const startScheduleTicker = () => {
         if (scheduleTimer)
             return;
         scheduleTimer = setInterval(() => {
+            if (shuttingDown)
+                return;
             const due = scheduler.due(Date.now());
             for (const job of due) {
                 // Do not pile MANY copies of the same job while the agent is busy: if
@@ -1403,6 +1428,8 @@ async function main() {
     let reviewMode = null;
     process.on('SIGINT', async () => {
         running = false;
+        shuttingDown = true;
+        stopScheduleTicker();
         // Kill any background processes so no dev-server outlives the agent.
         killAllBackground();
         await browser.close().catch(() => { });
@@ -1827,8 +1854,12 @@ async function main() {
                 lastCtrlCAt = now;
             }
             else {
-                // Not busy — exit. We wake takeInput() so the loop finishes.
+                // Not busy — exit. We wake takeInput() so the loop finishes. The
+                // scheduler must stop too: a live /loop ticker keeps firing into the
+                // queue while the process is shutting down.
                 running = false;
+                shuttingDown = true;
+                stopScheduleTicker();
                 if (waiter) {
                     const r = waiter;
                     waiter = null;
@@ -2160,6 +2191,7 @@ async function main() {
             schema: CONFIG_SCHEMA,
             homeConfigPath: CONFIG_PATHS.HOME_CONFIG,
             projectConfigPath: CONFIG_PATHS.PROJECT_CONFIG,
+            shadowedKeys: shadowedConfigKeys,
         });
     }
     // Open a chat by its ChatInfo and print the restored dialogue. Shared by
@@ -2939,7 +2971,7 @@ async function main() {
             // finding it meant /chats (a network fetch) or copying the id.
             const last = loadLastSession(currentWorkdir, config.provider);
             if (!last || !last.id) {
-                console.error(theme.error(t('sessions.none')));
+                console.error(theme.error(t('sessions.none_here')));
                 continue;
             }
             if (editor)
@@ -3222,7 +3254,7 @@ async function main() {
                 }
             }
             for (const w of st.warnings)
-                console.log(theme.warn('  ' + w));
+                console.log(theme.warn('  ' + t(w.key, w.params)));
             continue;
         }
         if (lower === '/skills') {
@@ -3704,6 +3736,7 @@ async function main() {
             // paths stay identical (same retries, same fallback, same resend).
             const res = await performCompact({
                 browser,
+                providerLabel: providerLabel(config.provider),
                 currentChatId,
                 workdir: currentWorkdir,
                 locale: currentLocale,
@@ -4167,6 +4200,7 @@ async function main() {
                     ? async () => {
                         const res = await performCompact({
                             browser,
+                            providerLabel: providerLabel(config.provider),
                             currentChatId,
                             workdir: currentWorkdir,
                             locale: currentLocale,

package/dist/mcp.js

@@ -486,7 +486,10 @@ export async function createMcpPool(opts) {
         status: () => ({
             servers: infos,
             toolCount: tools.length,
-            warnings: floating.map((n) => `MCP server "${n}" uses a floating version (@latest/@next); pin an exact version so the tool set does not change between runs.`),
+            warnings: floating.map((n) => ({
+                key: 'mcp.floating',
+                params: { v: n },
+            })),
         }),
         close: async () => {
             if (closed)

package/dist/prompt.js

@@ -10,6 +10,17 @@
 //      pasted text in the markers \x1b[200~ … \x1b[201~, so we know for sure
 //      that this is a paste, not keyboard typing, and Enter inside it is not
 //      treated as submission.
+//
+// A `data` chunk is a stream of UTF-8 BYTES and a terminal hands them over in
+// whatever sizes the pty chose: an emoji (4 bytes) or any other non-ASCII
+// character can be split between two reads. `Buffer#toString('utf-8')` decodes
+// every read on its own, so a split character became a run of U+FFFD — the
+// operator's answer (a login, a path, a Cyrillic task) arrived corrupted. The
+// decoder below holds back an INCOMPLETE trailing sequence until the bytes
+// that finish it arrive, and every read (keys, paste, the pasted tail) goes
+// through it. The non-TTY path instead CONCATENATES the raw buffers and decodes
+// once at EOF, so a split there heals by itself.
+import { StringDecoder } from 'node:string_decoder';
 export async function promptOnce(question) {
     const stdin = process.stdin;
     const stdout = process.stdout;
@@ -71,8 +82,12 @@ export async function promptOnce(question) {
             line = line.slice(0, cursor) + clean + line.slice(cursor);
             cursor += clean.length;
         };
+        // One decoder for the WHOLE read loop: it keeps the bytes of a character
+        // that was split between two `data` events and prepends them to the next
+        // read, instead of turning both halves into U+FFFD.
+        const decoder = new StringDecoder('utf8');
         const onData = (buf) => {
-            let s = buf.toString('utf-8');
+            let s = decoder.write(buf);
             // Fallback for terminals without bracketed paste: if the whole chunk is
             // a "bare" newline (one byte), then Enter was pressed → submit.
             // If newlines came TOGETHER with other text in one chunk — that's a

package/dist/status-command.js

@@ -7,7 +7,7 @@ export function formatStatus(s, t = translate('en')) {
     const onoff = (b) => (b ? t('common.on') : t('common.off'));
     const lines = [];
     lines.push(t('status.workdir', { v: s.workdir }));
-    lines.push(t('status.review_mode', { v: s.reviewMode || t('status.review_none') }));
+    lines.push(t('status.review_mode', { v: s.reviewMode || no }));
     if (s.reviewMode && s.origDir) {
         lines.push(t('status.orig_dir', { v: s.origDir }));
     }
@@ -36,7 +36,11 @@ export function formatStatus(s, t = translate('en')) {
     // A NEGATIVE tool count is nonsense (a broken MCP server status, a
     // hand-edited value): "MCP tools: -2" reads like a real measurement, the
     // same rule the token counter below already follows.
-    const mcpCount = s.mcpToolCount === null || s.mcpToolCount < 0 ? none : s.mcpToolCount;
+    // `none` ("(none)") would claim that the tools themselves are absent;
+    // with no MCP pool configured the COUNT is simply unknown.
+    const mcpCount = s.mcpToolCount === null || s.mcpToolCount < 0
+        ? t('common.unknown')
+        : s.mcpToolCount;
     lines.push(t('status.mcp', { v: mcpCount }));
     // A NEGATIVE count is nonsense (a broken provider counter): show "unknown"
     // rather than a number that reads like a real measurement.

package/dist/system-prompt.js

@@ -351,6 +351,11 @@ and the (MCP server: ...) note in its description tells you which server
 it belongs to. The JSON Schema in the description lists the exact fields
 (including their descriptions and enums) - follow it.
 
+In plan (read-only) mode an MCP tool whose name looks mutating (click,
+type, write, ...) is REMOVED from your tool set, exactly like the
+built-in writers. The list you were given is the whole truth: if a tool
+is not in it, it is not available in this run - do not try to call it.
+
 ## How to use tools
 
 To call ONE tool, respond with ONLY a JSON object (no markdown fences, no extra text):
@@ -420,6 +425,9 @@ reliably, pass the content in base64 instead of plain text:
 
 - Write: use 'content_base64' instead of 'content'.
 - Edit: use 'old_base64' / 'new_base64' instead of 'old_string' / 'new_string'.
+- MultiEdit: use 'edits_base64' (base64 of the JSON array) instead of 'edits'.
+- TodoWrite: use 'todos_base64' (base64 of the JSON array) instead of 'todos'.
+- ApplyPatch: use 'patch_base64' instead of 'patch'.
 
 base64 alphabet is [A-Za-z0-9+/=] and is not corrupted. Encode with the
 base64 command or in Node via Buffer.from(text).toString('base64').

package/dist/tui/AskQuestion.js

@@ -91,7 +91,7 @@ export function AskQuestion({ question, options, recommended, allowText, locale
             out.push(line);
         return out.length ? out : [''];
     };
-    return (_jsxs(Box, { flexDirection: "column", borderStyle: "round", borderColor: UI.accent, paddingX: 2, children: [_jsx(Text, { color: UI.title, bold: true, children: '◆ ' + t('askuser.title') }), wrap(question).map((line, i) => (_jsx(Text, { color: UI.text, children: line }, i))), _jsx(Text, { color: "#3a3f4b", children: '─'.repeat(innerCols) }), typing ? (_jsxs(Box, { flexDirection: "column", children: [_jsx(Text, { color: UI.dim, children: t('askuser.your_answer') }), _jsxs(Text, { color: UI.accent, children: ['❯ ', text, '▏'] })] })) : (rows.map((label, i) => {
+    return (_jsxs(Box, { flexDirection: "column", borderStyle: "round", borderColor: UI.accent, paddingX: 2, children: [_jsx(Text, { color: UI.title, bold: true, children: '◆ ' + t('askuser.title') }), wrap(question).map((line, i) => (_jsx(Text, { color: UI.text, children: line }, i))), _jsx(Text, { color: "#3a3f4b", children: '─'.repeat(innerCols) }), typing ? (_jsxs(Box, { flexDirection: "column", children: [_jsx(Text, { color: UI.dim, children: t('askuser.your_answer') }), _jsx(Text, { color: UI.dim, children: t('askuser.enter_send') }), _jsxs(Text, { color: UI.accent, children: ['❯ ', text, '▏'] })] })) : (rows.map((label, i) => {
                 const sel = i === cursor;
                 const isRec = i === recommended;
                 return (_jsxs(Text, { children: [_jsx(Text, { color: UI.accent, children: sel ? '❯ ' : '  ' }), _jsx(Text, { color: sel ? UI.accent : undefined, bold: sel, children: label }), isRec ? (_jsx(Text, { color: "#6fd0b0", children: '  (' + t('askuser.recommended') + ')' })) : null] }, i));

package/dist/tui/TuiEditor.js

@@ -134,6 +134,13 @@ export class TuiEditor {
             // printAbove), so Ink must not patch them: an unmount (clearScreen)
             // would otherwise restore the native console and lose that routing.
             patchConsole: false,
+            // Shift+Enter is INDISTINGUISHABLE from a plain Enter unless the
+            // terminal disambiguates escape codes: both arrive as CR. The kitty
+            // keyboard protocol makes the modified form a distinct CSI-u
+            // sequence, which is what `dispatchKey` maps to a newline.
+            // 'auto' probes the terminal (CSI ? u) and stays silent when the
+            // terminal does not answer, so an unsupporting one is unaffected.
+            kittyKeyboard: { mode: 'auto' },
             alternateScreen: this.alternateScreen,
         });
         this.rendered = true;

package/dist/tui/widgets.js

@@ -45,8 +45,10 @@ export function HintBar({ hints, }) {
  *
  * The agent's answers are printed as pre-rendered ANSI (markdown.ts already
  * highlights with cli-highlight), so the live log does NOT use this component —
- * it exists for menus/panels that show a snippet inline (and for a future
- * structured log).
+ * it exists for menus/panels that show a snippet inline. No call site today:
+ * the Ctrl+Y / `/copy-code` feature that used it was removed, and plain `/copy`
+ * copies the whole answer, so `extractCodeBlocks` (src/code-blocks.ts) is only
+ * reached from its own tests.
  */
 export function CodeBlock({ code, lang, highlighted, width, hint, focused, }) {
     return (_jsxs(Box, { flexDirection: "column", borderStyle: "round", borderColor: focused ? UI.accent : UI.border, paddingX: 1, width: width, children: [_jsxs(Box, { justifyContent: "space-between", children: [_jsx(Text, { color: UI.dim, children: lang || 'code' }), hint ? _jsx(Text, { color: UI.accent, children: hint }) : null] }), (highlighted || code).split(String.fromCharCode(10)).map((line, i) => (_jsx(Text, { children: line || ' ' }, i)))] }));

package/llms-full.txt

@@ -1,7 +1,8 @@
 # zames_pro — full documentation for LLMs
 
 > Terminal coding agent that drives a real web chat LLM (DeepSeek, Qwen,
-> GLM) through a headless Playwright browser — no API key required.
+> GLM) through a Playwright browser (DeepSeek and Qwen headless, GLM in a
+> visible window) — no API key required.
 > Package: https://www.npmjs.com/package/zames_pro
 > Source: https://github.com/Viqto0r/zames_pro
 
@@ -111,7 +112,9 @@ Key pieces:
 - **Subagents** — the `Task` tool delegates a self-contained sub-task to an
   agent in its own separate chat (isolated context), which returns only a
   report, so heavy research does not flood the main context. On by default;
-  tune with `browser.subagents` / `browser.maxSubagents`.
+  `browser.subagents` turns it off and `browser.maxSubagents` caps the runs
+  per TASK (default 3). Calls are sequential, not parallel, and the subtype
+  matters: `explore` is read-only, `general` may edit files.
 - **MCP support** — plug in external tool servers (e.g. `@playwright/mcp`).
 - **Scheduling** — `/loop`, `/cron` and `/jobs` repeat tasks on a timer.
 - **Bilingual UI** — Russian / English (`/config lang`).
@@ -271,8 +274,12 @@ The prompt is a small line editor with persistent history:
 - `Ctrl+_` — undo the last edit in the input line (a fat-fingered `Ctrl+U` /
   `Ctrl+K` is recoverable).
 - `Ctrl+U` — clear the line, `Ctrl+K` — delete to end of line, `Ctrl+W` —
-  delete the word before the cursor, `Ctrl+←`/`Ctrl+→` — move by words.
-- `\` + `Enter`, `Ctrl+J`, `Ctrl+Enter` or `Shift+Enter` — insert a newline.
+  delete the word before the cursor, `Ctrl+←`/`Ctrl+→` — move by words,
+  `Ctrl+Delete`/`Alt+Delete` — delete the word after the cursor.
+- `\` + `Enter` and `Ctrl+J` — insert a newline; these two work in
+  every terminal. `Ctrl+Enter` and `Shift+Enter` do it too, but only where the
+  terminal implements the kitty keyboard protocol: without it the terminal
+  sends a PLAIN Enter for Shift+Enter and the message is sent.
 - `/` + `Tab` — slash-command hints and completion.
 - `!command` — run a shell command directly, bypassing the model (like
   Claude Code's bash mode). The same sandbox guard as the `Bash` tool applies,
@@ -286,9 +293,10 @@ selected without leaving the terminal:
   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).
+- the mouse wheel, `PgUp` / `PgDn` (half a screen) and `Home` / `End` (the very
+  top / bottom) scroll the dialog; the wheel needs `ui.mouseScroll=true` (the default), and
+  Home/End jump only while the input line is empty (with text typed they
+  move the caret as usual).
 - To copy a LARGE block, use `/export` (writes the whole session as Markdown)
   or the transcript file (`/transcript` shows the path) — the terminal's own
   drag-select cannot reach past one screen.
@@ -297,8 +305,8 @@ Set `NO_COLOR=1` to disable colors (a calm default palette is used otherwise).
 
 ### Images and files
 
-You can paste an image or a file into the input line (Ctrl+Shift+V / Shift+Insert
-or the terminal's own paste). zames saves it under `<project>/tmp` and shows a
+You can paste an image or a file into the input line (Shift+Insert or the
+terminal's own paste; for a FILE from the clipboard press Ctrl+V). zames saves it under `<project>/tmp` and shows a
 marker in the line - `[image#1]` for images, `[file#1]` for other files - then
 uploads the real file to the chat together with your message. These are the
 same formats the DeepSeek / Qwen / GLM web chat accepts (PNG, JPEG, GIF, WEBP, BMP,
@@ -368,6 +376,8 @@ The agent has the same style of tools as Claude Code / Codex CLI:
 - **Git** — `GitStatus`, `GitDiff`, `GitLog`, `GitShow`, `GitBranchList`,
   `GitAdd`, `GitCommit`, `GitPush`.
 - **Web** — `WebFetch`, `WebSearch`.
+- **Subagents** — `Task` (delegate a self-contained sub-task to an agent in
+  its own chat; `explore` is read-only, `general` may edit; capped per task).
 - **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).
@@ -415,8 +425,9 @@ commands (/new or /clear, /sessions, /chats, /resume-id, /last, /chat, /cd,
 - /review [focus] [--staged] — ask the agent to review uncommitted changes
   and report findings (no code changes).
 - /plan [on|off] — plan (read-only) mode. While it is on, the mutating tools
-  (Write/Edit/MultiEdit/ApplyPatch/Bash, GitAdd/GitCommit/GitPush) are removed
-  from the tool set, so the agent can investigate without touching the tree.
+  (Write/Edit/MultiEdit/ApplyPatch/Bash/BashOutput, GitAdd/GitCommit/GitPush,
+  AskUser) are removed from the tool set, and so are MCP tools with a mutating
+  name, so the agent can investigate without touching the tree.
   Start in it with `--plan`.
 - /compact — ask the active backend to compress the current chat into a handover
   summary, then open a NEW chat, resend the system prompt and post the summary
@@ -424,9 +435,10 @@ commands (/new or /clear, /sessions, /chats, /resume-id, /last, /chat, /cd,
 - /goal <condition> — set a **completion condition** (Claude Code parity). The
   agent starts working toward it at once and keeps starting new turns until a
   separate evaluator model judges the condition met. The goal clears itself
-  automatically when it is met (or judged impossible), or with `/goal clear`.
-  The condition is stored in `<project>/.zames-goal` (git-ignored) and restored
-  on the next launch. `/goal` with no argument shows the current state.
+  automatically when it is met (or judged impossible), or with `/goal clear`
+  (or its synonym `/goal off`). The condition is stored in `<project>/.zames-goal`
+  (git-ignored) and restored on the next launch. `/goal` with no argument — or
+  `/goal on` — shows the current state.
 - /loop <interval> <task> — repeat a task periodically (e.g. `/loop 10m run the
 tests`). /cron "<min> <hour> <dom> <month> <dow>" <task> — run on a schedule.
   /jobs [rm <id>|clear] lists and stops them. A fired job is put into the same
@@ -440,8 +452,9 @@ tests`). /cron "<min> <hour> <dom> <month> <dow>" <task> — run on a schedule.
   "Web search" item in the "+" menu.
   These (and /queue, /jobs, /goal, `/config <sub>`) can be used WHILE the agent
   is working — they do not touch the in-flight generation.
-- /queue [clear] — list or clear the messages waiting to be sent after the
-  current task.
+- /queue [list|ls|clear|c|clean] — list (`list`/`ls`) or clear
+  (`clear`/`c`/`clean`) the messages waiting to be sent after the 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%`). The
@@ -547,8 +560,7 @@ too):
 
 - **Memory** (`@modelcontextprotocol/server-memory`) — a local knowledge graph
   (9 tools) for durable facts across chats. NOTE: zames already has `MEMORY.md`
-
-* `AGENTS.md`; add this only if you want a queryable graph.
+  + `AGENTS.md`; add this only if you want a queryable graph.
 
 Keep the stack SMALL: every server loads its tool definitions into the model's
 context. Add one when you feel its absence, not before.
@@ -564,13 +576,14 @@ You can view and change settings without leaving the agent — use the
 toggle in place; numbers and strings open an input prompt.
 
 ```
-/config                       interactive settings menu
-/config list                  print all editable settings
+/config                       interactive settings menu (alias: menu)
+/config list                  print all editable settings (aliases: show, ls)
 /config get <path>            show a setting
 /config set <path> <value>    change a setting
-/config reset <path>          reset a setting to its default
-/config path                  show config file paths
+/config reset <path>          reset a setting to its default (alias: unset)
+/config path                  show config file paths (alias: paths)
 /config lang <ru|en>          switch interface and agent language
+                              (aliases: language, язык)
 ```
 
 Examples:

package/llms.txt

@@ -3,8 +3,8 @@
 > zames_pro (`zames_pro` on npm, binary `zames`) is a free, open-source
 > terminal coding agent that drives a real web chat LLM — DeepSeek
 > (chat.deepseek.com), Qwen (chat.qwen.ai) or GLM (chat.z.ai) — through a
-> headless Playwright browser, so it needs NO API key and bills nothing per
-> token. It behaves like Claude Code / Codex CLI in the terminal: reads and
+> Playwright browser (DeepSeek and Qwen headless, GLM in a visible window), so
+> it needs NO API key and bills nothing per token. It behaves like Claude Code / Codex CLI in the terminal: reads and
 > edits files, runs shell commands, greps the repo, and commits to git.
 
 This file follows the llms.txt convention (https://llmstxt.org): a short,
@@ -20,6 +20,8 @@ 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.
+  DeepSeek and Qwen run headless; GLM runs with a VISIBLE window by default,
+  because z.ai answers every headless send with a slider captcha.
 - **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,7 +1,7 @@
 {
   "name": "zames_pro",
-  "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.",
+  "version": "2.82.141",
+  "description": "Terminal coding agent that drives a real browser to chat with DeepSeek, Qwen or GLM — no API key required. Reads and edits files, runs commands, commits to git, like Claude Code / Codex CLI.",
   "type": "module",
   "bin": {
     "zames": "dist/index.js"

package/skills/systematic-debugging/SKILL.md

@@ -27,6 +27,13 @@ Shrink the failure to the smallest unit that still fails.
   remember writing.
 - Check the obvious causes FIRST: wrong file, stale build, cached state,
   different config, an earlier error swallowed by a catch.
+- In zames the evidence is already on disk: the transcript at
+  `~/.zames/logs/*.jsonl` (`/transcript` prints the exact path of THIS run),
+  the raw answer bodies under `~/.zames/net-log` when started with
+  `ZAMES_NET_DEBUG=1` (`npm run dev` sets it), and the per-send telemetry at
+  `~/.zames/logs/sends-<provider>.jsonl` (written in dev mode and when
+  `browser.sendTelemetry` is on). Read them BEFORE guessing — most "it hangs
+  / it stopped" reports are visible there.
 
 ## Phase 3 — Hypothesize (one at a time)
 

package/skills/test-driven-development/SKILL.md

@@ -32,3 +32,8 @@ RED → GREEN → REFACTOR. The order is the point, not a formality.
   CODE was wrong; do not just move the assertion.
 - If the code was written before its test, delete and rewrite it driven by
   the test — otherwise the test is shaped around the implementation.
+- A test that writes a temp dir or file cleans it up itself: in this repo
+  always go through `test/tmp-dir.ts` (`makeTmpDir(t, prefix)` /
+  `makeTmpDirSync`), which registers the `t.after` cleanup. On WSL a leaked
+  `os.tmpdir()` entry lives inside ext4.vhdx and never returns its space to
+  the Windows host, so an abandoned temp dir fragments the disk permanently.

package/skills/verification-before-completion/SKILL.md

@@ -24,6 +24,11 @@ from the real artifact — not from your intent.
 5. **State the evidence** in the final report — the exact command and its
    result — so the operator can reproduce it. "Tests pass" without the
    command is not evidence.
+6. **In zames the report is ONE `respond` call.** A long task may have
+   produced several findings along the way; the operator only ever reads the
+   LAST `respond` before the run stops, so put the complete evidence there —
+   never split it across intermediate messages, and never end a turn on a
+   bare text update with work still pending.
 
 ## The two failure modes this prevents