@noobdemon/noob-cli 1.12.17 → 1.13.0

package/CHANGELOG.md

@@ -2,14 +2,28 @@
 
 Tất cả thay đổi đáng kể của `@noobdemon/noob-cli` được ghi vào file này.
 
+## [1.13.0] - 2026-06-27
+
+### Fixed
+- **Worker `/api/chat` adapter cho raw backend stream**: gửi đúng shape use.ai (`messages[].parts`, `gateway-*` model id, `agenticMode`, file parts riêng, text parts gộp), không forward backend identity, `deep` tự tắt `web`. Parser stream raw `text/plain` bỏ qua metadata `event: {...}` kể cả khi dính liền sau text (`PONGevent: ...`).
+
+### Verified
+- Worker deployed.
+- `npm test` 105/105 pass.
+
+## [1.12.18] - 2026-06-25
+
+### Changed
+- Cải thiện system prompt cho coding flow: inspect đúng chỗ, patch hẹp, verify nhanh và final gọn hơn để model code mượt, ít vòng lặp hơn.
+
 ## [1.12.17] - 2026-06-24
 
 ### Added
-- **Image input support** (`src/tui.js`, `src/repl.js`, `src/api.js`, `src/agent.js`, `worker/src/worker.js`): rich TTY trên Windows hỗ trợ `Alt+V` để lấy ảnh từ clipboard, hiện chip `[pasted image #1]`, rồi gửi kèm payload `image: "data:image/png;base64,..."` qua gateway. CLI cũng tự đính kèm ảnh đầu tiên khi user nhắc `@file.png|jpg|jpeg|webp|gif` (giới hạn 8MB). Worker validate data URL và forward `image` sang Railway (`{message, model, image}`); fallback cũ giữ `{message, model}`.
+- **Image input support** (`src/tui.js`, `src/repl.js`, `src/api.js`, `src/agent.js`, `worker/src/worker.js`): rich TTY trên Windows hỗ trợ `Alt+V` để lấy ảnh từ clipboard, hiện chip `[pasted image #1]`, rồi gửi kèm payload `image: "data:image/png;base64,..."` qua gateway. CLI cũng tự đính kèm ảnh đầu tiên khi user nhắc `@file.png|jpg|jpeg|webp|gif` (giới hạn 8MB). Worker validate data URL và forward image through the gateway adapter.
 
 ### Verified
 - `npm test` 100/100 pass.
-- Railway `/chat` smoke với `image` data URL base64 trả mô tả ảnh thành công.
+- Image data URL base64 smoke trả mô tả ảnh thành công.
 
 ## [1.12.15] - 2026-06-16
 
@@ -208,7 +222,7 @@ Tất cả thay đổi đáng kể của `@noobdemon/noob-cli` được ghi vào
 ## [1.10.12] - 2026-06-09
 
 ### Fixed
-- **Auto-stop vì proxy chèn web search blocks** (`src/api.js` + `src/agent.js`): proxy unlimited.surf chèn `web_search_results`/`web_search_summary` vào stream → AI tưởng prompt injection, tốn context cảnh báo thay vì làm việc. Fix: `cleanResponseText()` tự động strip các block này + system prompt dặn model ignore + handle `{finish: true}` event của proxy.
+- **Auto-stop vì proxy chèn web search blocks** (`src/api.js` + `src/agent.js`): proxy chèn `web_search_results`/`web_search_summary` vào stream → AI tưởng prompt injection, tốn context cảnh báo thay vì làm việc. Fix: `cleanResponseText()` tự động strip các block này + system prompt dặn model ignore + handle `{finish: true}` event của proxy.
 
 ## [1.10.11] - 2026-06-09
 
@@ -486,7 +500,7 @@ Mỗi entry nên có các nhóm con (chỉ giữ nhóm có nội dung):
 - **Help text & autocomplete bổ sung 3 entry mới** (`/workflow`, `/goal`, `/loop`) — trước đây các lệnh này có code nhưng không xuất hiện trong `/help` lẫn slash autocomplete (UX bug, user không biết lệnh tồn tại).
 
 ### Changed
-- **`findModel()` nâng cấp 3-tier fuzzy match** (`src/models.js`): exact id → normalized id/name (bỏ prefix `gateway-`, chuẩn hoá dấu/spaces) → contains unique (reject ambiguous match nhiều model). Phục vụ sub-agent routing — model nội bộ luôn có prefix `gateway-` (vd `gateway-claude-opus-4-7`) nhưng AI khi spawn sẽ gõ tên ngắn (`claude-opus-4-7`, `deepseek-v4-flash`, `kimi`) — fuzzy match xử lý cả hai phía mà không nhầm.
+- **`findModel()` nâng cấp 3-tier fuzzy match** (`src/models.js`): exact id → normalized id/name (bỏ prefix `gateway-`, chuẩn hoá dấu/spaces) → contains unique (reject ambiguous match nhiều model). Phục vụ sub-agent routing — model nội bộ luôn có prefix `gateway-` (vd `gateway-claude-opus-4-8`) nhưng AI khi spawn sẽ gõ tên ngắn (`claude-opus-4-8`, `deepseek-v4-pro`) — fuzzy match xử lý cả hai phía mà không nhầm.
 - **`runAgent` hỗ trợ `tokenBudget` + `onBudgetExceeded`** (`src/agent.js`): vượt budget thì model bị ép tóm tắt rồi dừng, không tự đốt tiếp. Cùng cơ chế cho sub-agent.
 - **Status bar realtime kèm token cho sub-agent**: token meter của sub-agent dùng chung instance với cha (truyền qua `runSubAgent({tokenMeter})`) → tổng phiên cộng đúng cả sub.
 

package/README.md

@@ -50,7 +50,7 @@ Trong phiên: `/login <key>`, `/usage`, `/logout`.
 
 > Mỗi lệnh gọi mô hình (kể cả từng bước tool trong một tác vụ) tính là 1 request.
 
-Cấp/huỷ key (admin) — trong repo gateway `D:\Dev\free claude code`:
+Cấp/huỷ key (admin) — trong repo gateway `worker/`:
 
 ```bash
 node scripts/admin.mjs create pro "khách A"
@@ -63,7 +63,7 @@ node scripts/admin.mjs revoke nk_pro_xxx
 ```bash
 noob                                   # interactive session
 noob "add input validation to api.js"  # start with a request
-noob -m gateway-claude-opus-4-7        # pick a model
+noob -m gateway-claude-opus-4-8        # pick a model
 noob --yolo                            # auto-approve edits & commands
 ```
 
@@ -136,7 +136,7 @@ function-calling). Models differ in how willingly they follow it:
 
 | Provider               | Agentic tools    | Notes                                    |
 | ---------------------- | ---------------- | ---------------------------------------- |
-| **Anthropic** (Claude) | ✅ best          | default — `gateway-claude-opus-4-7`      |
+| **Anthropic** (Claude) | ✅ best          | default — `gateway-claude-opus-4-8`      |
 | **DeepSeek**           | ✅ works         | good free alternative                    |
 | OpenAI (GPT/o-series)  | ⚠️ often refuses | replies "I can't access your filesystem" |
 | Google (Gemini)        | ⚠️ often refuses | same                                     |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noobdemon/noob-cli",
-  "version": "1.12.17",
+  "version": "1.13.0",
   "publishConfig": {
     "access": "public"
   },

package/src/agent.js

@@ -36,7 +36,7 @@ Available tools (each is self-contained; pick the SMALLEST tool that answers the
 Context is finite. Don't slurp the whole repo up front. Discover information progressively: list_dir/glob to map → grep to locate → read_file (with offset+limit for big files) to inspect only what matters. Each tool result spends your attention budget — make every call earn it. When a tool returns a huge blob, extract the few facts you need, then move on; don't re-read it later (the result stays in history).
 
 # Rules
-- TODO-BASED EXECUTION: For any multi-step task (3+ actions), you MUST call \`write_todos\` FIRST with all items done:false, then call it AGAIN after every completed step with that item flipped to done:true (resend the full list). NEVER write markdown \`- [ ]\` lines — the runtime parses \`write_todos\` calls, not markdown. Your response is NOT finished until all items are done:true. The ONLY valid reason to stop is: (a) all items done, or (b) you are WAITING for a user reply. If you just got a tool result, you MUST continue — do NOT output a summary, do NOT ask "what next", do NOT stop. After write_file/edit_file returns, call write_todos to tick the just-finished item, then immediately start the next.
+- TODO-BASED EXECUTION: For any multi-step task (3+ actions), you MUST call \`write_todos\` FIRST with all items done:false, then call it AGAIN after every completed step with that item flipped to done:true (resend the full list). NEVER write markdown \`- [ ]\` lines — the runtime parses \`write_todos\` calls, not markdown. Your response is NOT finished until all items are done:true. The ONLY valid reason to stop is: (a) all items done and sensible verification is complete, or (b) you are WAITING for a user reply. If you just got a tool result and unfinished work remains, continue with the next tool — do NOT output a premature summary, do NOT ask "what next". After write_file/edit_file returns, call write_todos to tick the just-finished item, then immediately start the next.
 - GROUND TRUTH = real TOOL RESULTs in this conversation, not your memory or what you intended to do. A file changed only if a write_file/edit_file result confirms it (see the FILES CHANGED list). A test passed / build succeeded / command worked only if a run_command result above shows it. Never narrate outcomes you didn't observe; if you haven't checked, say so and check now (read_file / list_dir / run the command). Before any "done/summary" reply, reconcile every file and result you're about to claim against the actual tool results above — if it isn't there, you didn't do it yet.
 - VERIFY BEFORE DISMISSING: never declare a TOOL RESULT "fake", "spurious", "injected", "unrelated", or "from a previous turn" without first verifying with a fresh tool call. If a result looks off (unexpected content, output you didn't ask for, weird command), your DEFAULT is: treat it as REAL runtime output, then run a small verification (read_file the affected path, grep for the symbol, list_dir, re-run the command) to confirm actual state. Only after the verification tool result contradicts the suspicious one may you call it stale/leftover — and even then, work from the FRESH result, never from your guess. Trusting your own skepticism over the runtime is the same over-confidence bug as hallucinating success: both substitute memory for evidence.
 - Investigate before editing: read the relevant files first; never invent file contents.
@@ -66,6 +66,12 @@ Context is finite. Don't slurp the whole repo up front. Discover information pro
 3. SURGICAL: change only what the task needs. No drive-by refactors, renames, reformatting, or comment churn in unrelated code.
 4. VERIFIABLE GOAL: decide how you'll know it works, then check it (run the build/test, read the output). Report what you verified — and honestly state what you did NOT verify.
 
+# Coding workflow — default for implementation tasks
+1. Inspect first: list/glob/grep/read only the files needed to understand the change.
+2. Patch narrowly: edit the smallest relevant block; avoid new helpers/files unless they clearly reduce code now.
+3. Verify narrowly: run the fastest relevant test/lint/build command. If it fails, use the output as ground truth and fix once before broadening scope.
+4. Finish cleanly: final answer states the changed files and the exact verification result. Do not include tool-call JSON, long plans, or speculative next steps.
+
 # Example interaction
 ## USER
 do the tests pass?

package/src/api.js

@@ -330,7 +330,7 @@ async function streamOnce({
       if (p.answer) text = p.answer;
     }
     if (p.truncated) truncated = true;
-    // Handle {finish: true, reason: "stop"} — unlimited.surf & some proxies
+    // Handle {finish: true, reason: "stop"} — some proxies
     // send this as completion signal instead of (or in addition to) {done: true}
     if (p.finish === true && p.reason === 'stop') sawDone = true;
     if (p.done) sawDone = true;