zames_pro 2.72.5 → 2.72.7

package/CHANGELOG.md

@@ -7,6 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.72.7] - 2026-10-09
+
+### Fixed
+
+- **ui:** show a queued-message banner for EVERY queued message
+
+### Fixed
+
+- **ui:** show a queued-message banner for EVERY queued message
+
+## [2.72.6] - 2026-10-09
+
+### Fixed
+
+- **browser:** detect the property form of quasi_status (Stopped/FINISHED hang)
+
+### Fixed
+
+- **browser:** detect the property form of quasi_status (Stopped/FINISHED hang)
+
 ## [2.72.5] - 2026-10-09
 
 ### Changed

package/dist/deepseek-ui.js

@@ -213,11 +213,18 @@ export const RATE_LIMIT_RE = /(messages? too frequent|too many requests|rate lim
 export const SERVER_BUSY_RE = /(server (is )?busy|server error|service (is )?unavailable|temporarily unavailable|internal server error|502|503|504|server overloaded|сервер занят|сервер перегружен|сервис недоступен|внутренняя ошибка|попробуйте позже)/i;
 // ---------- network protocol (SSE) ----------
 export const GENERATION_ERR_RE = /"finish_reason":\s*"generation_err"/i;
-export const INCOMPLETE_STATUS_RE = /"quasi_status","v":"INCOMPLETE"/i;
+// DeepSeek emits the generation status in TWO shapes: the initial message as a
+// JSON property (`"quasi_status":"FINISHED"` inside v.response) and later
+// BATCH updates (`{"p":"quasi_status","v":"FINISHED"}`). The old regex only
+// matched the BATCH form, so a FINISHED-without-answer turn that came in the
+// PROPERTY form (the real "Server is temporarily unavailable" case) was NOT
+// detected — the agent hung on "Stopped" until the timeout. Match both.
+export const INCOMPLETE_STATUS_RE = /"quasi_status"(?::|,"v":)"INCOMPLETE"/i;
 // A turn that ENDED (`quasi_status: FINISHED`) but produced NO answer text —
 // the reasoning was generated and the model stopped WITHOUT a RESPONSE
-// fragment. The UI shows Stopped + Continue.
-export const FINISHED_STATUS_RE = /"quasi_status","v":"FINISHED"/i;
+// fragment. The UI shows Stopped + Continue. Matches both the JSON-property
+// and the BATCH shape (see INCOMPLETE_STATUS_RE).
+export const FINISHED_STATUS_RE = /"quasi_status"(?::|,"v":)"FINISHED"/i;
 export const RESPONSE_CONTENT_RE = /"type":"RESPONSE","content":"[^"]/;
 // Only a completion/continue turn carries a real answer. Gating the capture
 // assignment to these URLs keeps a future endpoint (which happens to return a

package/dist/i18n/common.js

@@ -154,6 +154,12 @@ export const commonMessages = {
         en: '⏹ Ctrl+C — aborting generation...',
     },
     'msg.queued': { ru: '📨 В очередь ({n}): ', en: '📨 Queued ({n}): ' },
+    // TTY variant: the editor already echoed the message text, so only the
+    // count is shown (no repeated text).
+    'msg.queued_badge': {
+        ru: '📨 В очередь ({n})',
+        en: '📨 Queued ({n})',
+    },
     // Shown ONCE per session, the first time a message is queued while the
     // agent is working. It explains what happens (sent after the current task)
     // and how to inspect/clear the queue, so the operator knows nothing is lost.

package/dist/index.js

@@ -1321,12 +1321,17 @@ async function main() {
             const msg = { text, attachments };
             pendingQueue.push(msg);
             // The operator typed this WHILE the agent was working, so the message is
-            // queued and only sent after the current task. Explain that once per
-            // session (via the editor's own status area) so it is clear nothing was
-            // lost; later queued messages stay as the compact msg.queued banner only.
-            if (ed.busy && !queueHintShown) {
-                queueHintShown = true;
-                ed.printAbove(theme.dim(t('msg.queued_hint')));
+            // queued and only sent after the current task. In TTY the editor ALREADY
+            // echoed the message text (❯ …) above the input, so we add only a compact
+            // COUNT line (no repeated text) for EVERY queued message — so it is always
+            // clear the message was accepted and not lost. The FIRST one additionally
+            // explains what the queue is and how to inspect/clear it.
+            if (ed.busy) {
+                if (!queueHintShown) {
+                    queueHintShown = true;
+                    ed.printAbove(theme.dim(t('msg.queued_hint')));
+                }
+                ed.printAbove(theme.user(t('msg.queued_badge', { n: pendingQueue.length })));
             }
             if (waiter) {
                 const r = waiter;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zames_pro",
-  "version": "2.72.5",
+  "version": "2.72.7",
   "description": "Terminal coding agent that drives chat.deepseek.com through Playwright — no API key required. Reads and edits files, runs commands, commits to git, like Claude Code / Codex CLI.",
   "type": "module",
   "bin": {