zames_pro 2.84.0 → 2.85.0

package/CHANGELOG.md

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.85.0] - 2026-10-27
+
+### Added
+
+- **ui:** theme the window background, keep the unsent draft, drop the extra prompt caret
+
 ## [2.84.0] - 2026-10-27
 
 ### Added

package/README.md

@@ -38,7 +38,7 @@ lock-in. Install with `npm install -g zames_pro`, run `zames` in any project
 folder, and describe the task in plain language.
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/Viqto0r/zames_pro/master/docs/demo.png" alt="zames terminal coding agent session — an AI coding agent working in the command line without an API key" width="860">
+  <img src="https://raw.githubusercontent.com/Viqto0r/zames_pro/master/docs/shots/theme-zames.png" alt="zames terminal coding agent session — an AI coding agent working in the command line without an API key" width="860">
 </p>
 
 ## Quick start
@@ -635,7 +635,12 @@ are ports of well-known editor schemes:
 `rose-pine`, `everforest`, `kanagawa`.
 
 A theme repaints EVERYTHING: the interface, the agent's answers, the code
-highlighting inside them, the status row and the input frame. To make the choice
+highlighting inside them, the status row and the input frame. The terminal's
+BACKGROUND follows too: the theme emits OSC-11 with the palette's `bg`
+(supported by iTerm2, Windows Terminal, kitty, WezTerm, Alacritty, GNOME
+Terminal and others; where it is not supported nothing happens). Opt out with
+`ZAMES_NO_BG=1` or `NO_COLOR`.
+To make the choice
 concrete, a SAMPLE SESSION in that palette is shown before you pick (in `/theme`
 below the list, in `/config` press `p` on the theme row); after
 `/theme <id>` the sample is printed too. The frame itself is a separate
@@ -761,7 +766,7 @@ Qwen или GLM) в агента для командной строки в ду
 можно описать обычным языком.
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/Viqto0r/zames_pro/master/docs/demo.png" alt="сессия zames в терминале — терминальный coding-агент и AI-ассистент программиста без API-ключа" width="860">
+  <img src="https://raw.githubusercontent.com/Viqto0r/zames_pro/master/docs/shots/theme-zames.png" alt="сессия zames в терминале — терминальный coding-агент и AI-ассистент программиста без API-ключа" width="860">
 </p>
 
 ## Быстрый старт
@@ -1367,7 +1372,11 @@ enum переключаются на месте; числа и строки от
 `rose-pine`, `everforest`, `kanagawa`.
 
 Тема перекрашивает ВСЁ: интерфейс, ответы агента, подсветку кода в ответах,
-строку статуса и рамку ввода. Чтобы было видно, ЧТО меняется, перед выбором
+строку статуса и рамку ввода. ФОН окна терминала тоже перекрашивается: тема
+шлёт OSC-11 с цветом `bg` палитры (поддерживают iTerm2, Windows Terminal,
+kitty, WezTerm, Alacritty, GNOME Terminal и др.; где не поддерживается — просто
+ничего не происходит). Отключить фон: `ZAMES_NO_BG=1` или `NO_COLOR`.
+Чтобы было видно, ЧТО меняется, перед выбором
 показывается образец сессии в этой палитре (в `/theme` — под списком, в
 `/config` — клавиша `p` на строке темы). После применения `/theme <id>`
 образец печатается в терминал. Саму рамку можно менять отдельно:

package/dist/index.js

@@ -1519,8 +1519,9 @@ async function main() {
                 theme.dim(') '));
         }
         // No working-directory tail: it ate input width and is already in the
-        // header / /pwd. A bare prompt keeps room for the task text.
-        return theme.prompt('❯ ') + theme.dim('› ');
+        // header / /pwd. A bare `❯ ` keeps room for the task text and does not
+        // read as a SECOND prompt marker next to the cursor.
+        return theme.prompt('❯ ');
     };
     await refreshDynamicCommands(currentWorkdir);
     if (process.stdin.isTTY && process.stdout.isTTY) {
@@ -2446,9 +2447,6 @@ async function main() {
                             theme.dir(reviewMode.snapName) +
                             theme.dim(') ');
                 }
-                else {
-                    tail = theme.dim('› ');
-                }
                 input = await promptOnce(theme.prompt('❯ ') + tail);
             }
         }

package/dist/theme.js

@@ -1,5 +1,6 @@
 import chalk from 'chalk';
 import { contentWidth } from './width.js';
+import { applyBackground } from './tui/background.js';
 // Respect NO_COLOR (https://no-color.org): when the operator sets it (any
 // non-empty value) drop ALL SGR codes so the output can be piped into a file
 // or a log viewer without escape noise. chalk 5 only auto-detects TTY/CI, it
@@ -367,6 +368,9 @@ export function applyTheme(name) {
         theme[key] = built[key];
     }
     activeName = next;
+    // The window background is part of the look: paint it (best effort) so a
+    // dark palette does not sit on a light terminal background.
+    applyBackground(next);
     return next;
 }
 /**

package/dist/tui/InputLine.js

@@ -12,7 +12,7 @@ import { useCallback, useEffect, useMemo, useRef, useState } from 'react';
 import { Box, Text, useInput, usePaste, useCursor, useWindowSize, useStdin, } from 'ink';
 import { translate } from '../i18n.js';
 import { expandPastes, inputInnerCols, layoutInput, SUGGEST_PAGE, } from '../input/layout.js';
-import { insertText, insertPaste, insertNewline, backspace, del, moveLeft, moveRight, moveHome, moveEnd, wordLeft, wordRight, deleteWordLeft, deleteWordRight, killToLineEnd, moveVisualRows, pushUndo, undoEdit, historyUp, historyDown, searchStart, searchNext, searchAccept, searchCancel, searchInput, searchBackspace, recordHistory, afterSubmit, } from './edit.js';
+import { insertText, insertPaste, insertNewline, backspace, del, moveLeft, moveRight, moveHome, moveEnd, wordLeft, wordRight, deleteWordLeft, deleteWordRight, killToLineEnd, moveVisualRows, pushUndo, undoEdit, historyUp, historyDown, searchStart, searchNext, searchAccept, searchCancel, searchInput, searchBackspace, recordHistory, afterSubmit, rememberDraft, } from './edit.js';
 import { dispatchKey, parseCsiU } from './keys.js';
 import { useSyncExternalStore } from 'react';
 import { matchSlashCommands, suggestWindow, completeSlashCommand, } from '../input/suggest.js';
@@ -125,17 +125,20 @@ export function InputLine(props) {
             case 'submit':
                 doSubmit();
                 return;
+            // The EDIT actions first write the line into the draft slot, so a
+            // remembered draft is replaced only by a REAL edit and an accidental
+            // Up cannot lose the typed message.
             case 'newline':
-                apply(insertNewline);
+                apply((s) => pushUndo(rememberDraft(insertNewline(s)), true));
                 return;
             case 'insert':
-                apply((s) => pushUndo(insertText(s, action.text), true));
+                apply((s) => pushUndo(rememberDraft(insertText(s, action.text)), true));
                 return;
             case 'backspace':
-                apply((s) => backspace(pushUndo(s, true)));
+                apply((s) => backspace(pushUndo(rememberDraft(s), true)));
                 return;
             case 'delete':
-                apply((s) => del(pushUndo(s, true)));
+                apply((s) => del(pushUndo(rememberDraft(s), true)));
                 return;
             case 'left':
                 apply(moveLeft);

package/dist/tui/background.js

@@ -0,0 +1,42 @@
+// Terminal BACKGROUND handling.
+//
+// A terminal cannot be told to paint "the background" — only the cells an app
+// writes are styled. So a theme's `bg` reaches the screen by
+//   1. emitting an OSC-11 background colour for the whole window (most modern
+//      terminals support it; a terminal that does not answers nothing), and
+//   2. re-emitting it AFTER a full-screen app exits: the alternate screen keeps
+//      the window's background, and Ink's exit sequence resets attributes
+//      (SGR reset does not touch OSC-11, but some terminals do reset the colour
+//      on 1049l). Re-emitting is harmless where unsupported.
+//
+// The OSC sequence is written STRAIGHT to stdout (not through chalk), because
+// it is not an SGR attribute: `\x1b]11;rgb:rr/gg/bb\x07`.
+import { PALETTES, isThemeName, DEFAULT_THEME } from '../theme.js';
+/** `#rrggbb` -> the `rr/gg/bb` part of an OSC-11 payload. */
+function hexToOsc(hex) {
+    const h = hex.replace('#', '');
+    return `${h.slice(0, 2)}/${h.slice(2, 4)}/${h.slice(4, 6)}`;
+}
+/**
+ * The OSC-11 sequence that sets the window background, or '' when the operator
+ * opted out (NO_COLOR / ZAMES_NO_BG). Exported pure, so the encoding is
+ * testable without a terminal.
+ */
+export function backgroundOsc(name) {
+    if (process.env.NO_COLOR || process.env.ZAMES_NO_BG)
+        return '';
+    const id = isThemeName(name) ? name : DEFAULT_THEME;
+    return '\x1b]11;rgb:' + hexToOsc(PALETTES[id].bg) + '\x07';
+}
+/** Paint the window background for the palette `name` (best effort). */
+export function applyBackground(name) {
+    const seq = backgroundOsc(name);
+    if (!seq)
+        return;
+    try {
+        process.stdout.write(seq);
+    }
+    catch {
+        // A closed/redirected stdout must not break a theme switch.
+    }
+}

package/dist/tui/edit.js

@@ -249,9 +249,11 @@ export function historyUp(s) {
     if (!s.history.length)
         return s;
     let histIndex = s.histIndex;
-    let histDraft = s.histDraft;
-    if (histIndex === s.history.length)
-        histDraft = s.buf;
+    // Snapshot the unsent line when the browse STARTS (histIndex is at the end),
+    // but NEVER replace the remembered draft with a RECALLED entry's text: a
+    // second Up after a Down used to overwrite it, and the operator's typed
+    // message was lost ("pressed Up by accident").
+    const histDraft = histIndex === s.history.length ? s.buf : s.histDraft;
     if (histIndex > 0) {
         histIndex--;
         const buf = s.history[histIndex];
@@ -269,6 +271,10 @@ export function historyDown(s) {
     if (!s.history.length)
         return s;
     let histIndex = s.histIndex;
+    // The CURRENT line is the operator's, not a history entry: leaving the
+    // history must bring it back. Without this, editing a recalled line and then
+    // pressing Down restored the OLD draft and dropped the edit.
+    const draft = browsingHistory(s) ? s.histDraft : s.buf;
     let buf;
     if (histIndex < s.history.length - 1) {
         histIndex++;
@@ -276,9 +282,38 @@ export function historyDown(s) {
     }
     else {
         histIndex = s.history.length;
-        buf = s.histDraft;
+        buf = draft;
     }
-    return { ...s, histIndex, buf, cursor: Array.from(buf).length };
+    return {
+        ...s,
+        histIndex,
+        histDraft: draft,
+        buf,
+        cursor: Array.from(buf).length,
+    };
+}
+// ---------- draft guard ----------
+//
+// The operator's UNSUBMITTED line must survive a history browse, arrow-key
+// scrolling and every other non-typing transition. `histDraft` alone did not:
+// it is snapshotted only when the browse STARTS (histIndex === history.length),
+// so once the cursor was inside the history an edit or a second Up path could
+// replace it — a real report was "I pressed Up by accident and my typed message
+// was gone".
+//
+// The rule: typing/recalling may change the visible buffer, but a transition
+// that is NOT an explicit edit must keep the draft; leaving the history restores
+// it. `typingRun` is true while the operator types (so a real edit adopts the new
+// text as the draft on the next browse).
+/** True while the buffer is a RECALLED history entry (not the draft). */
+export function browsingHistory(s) {
+    return s.history.length > 0 && s.histIndex < s.history.length;
+}
+/** Remember the current buffer as the draft when it is NOT a history entry. */
+export function rememberDraft(s) {
+    if (s.buf === s.histDraft)
+        return s;
+    return { ...s, histDraft: s.buf };
 }
 export function searchStart(s) {
     if (!s.history.length)

package/llms-full.txt

@@ -23,7 +23,7 @@ lock-in. Install with `npm install -g zames_pro`, run `zames` in any project
 folder, and describe the task in plain language.
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/Viqto0r/zames_pro/master/docs/demo.png" alt="zames terminal coding agent session — an AI coding agent working in the command line without an API key" width="860">
+  <img src="https://raw.githubusercontent.com/Viqto0r/zames_pro/master/docs/shots/theme-zames.png" alt="zames terminal coding agent session — an AI coding agent working in the command line without an API key" width="860">
 </p>
 
 ## Quick start
@@ -620,7 +620,12 @@ are ports of well-known editor schemes:
 `rose-pine`, `everforest`, `kanagawa`.
 
 A theme repaints EVERYTHING: the interface, the agent's answers, the code
-highlighting inside them, the status row and the input frame. To make the choice
+highlighting inside them, the status row and the input frame. The terminal's
+BACKGROUND follows too: the theme emits OSC-11 with the palette's `bg`
+(supported by iTerm2, Windows Terminal, kitty, WezTerm, Alacritty, GNOME
+Terminal and others; where it is not supported nothing happens). Opt out with
+`ZAMES_NO_BG=1` or `NO_COLOR`.
+To make the choice
 concrete, a SAMPLE SESSION in that palette is shown before you pick (in `/theme`
 below the list, in `/config` press `p` on the theme row); after
 `/theme <id>` the sample is printed too. The frame itself is a separate

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zames_pro",
-  "version": "2.84.0",
+  "version": "2.85.0",
   "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": {