@noobdemon/noob-cli 1.9.10 → 1.9.12

package/package.json

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

package/src/agent.js

@@ -33,7 +33,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 do TWO things in the SAME response: (1) write the todo list as "- [ ] task" markers, and (2) IMMEDIATELY start working on the FIRST unchecked item — do NOT stop after writing the list. The todo list is NOT output — it is a planning step. NEVER output a todo list and then stop. After checking off an item ("- [x]"), CONTINUE to the next unchecked item in the SAME response. Only stop when ALL items are "- [x]" or you are waiting for a tool result. Before claiming "done", verify ALL items are checked. NEVER stop mid-plan.
+- TODO-BASED EXECUTION: For multi-step tasks, you MUST keep going until ALL items are "- [x]". NEVER stop mid-list. Flow: (1) write todo list, (2) start first item, (3) after EVERY tool result, check off the completed item AND IMMEDIATELY start the next unchecked item, (4) repeat until all done. Your response is NOT finished until ALL items are checked. 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, immediately do the next item.
 - 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.
 - Investigate before editing: read the relevant files first; never invent file contents.
 - Make the smallest change that fully solves the task. Match the surrounding code style.

package/src/repl.js

@@ -150,6 +150,12 @@ export async function startRepl(opts = {}) {
   };
   const tokenMeter = new TokenMeter();
 
+  // Set terminal title bar — hiện trên CMD/PowerShell.
+  const updateTitle = () => {
+    process.title = `noob — ${state.model.name}`;
+  };
+  updateTitle();
+
   // Prompt = dòng trạng thái sống. Luôn phản ánh yolo + version theo thời gian
   // thực (vẽ lại mỗi lượt và ngay khi Shift+Tab), nên không cần gõ /status.
   const promptStr = (lead = true) => {
@@ -306,6 +312,7 @@ export async function startRepl(opts = {}) {
       const m = findModel(s.model);
       if (m) state.model = m;
     }
+    updateTitle();
     // Re-arm /loop nếu phiên cũ đang chạy loop (timer/running không serialize được).
     if (s.loop && s.loop.task && s.loop.intervalMs) {
       state.loop = {
@@ -1790,6 +1797,7 @@ NGUYÊN TẮC:
     state.model = m;
     state.mode = "chat";
     config.setModel(m.id);
+    updateTitle();
     console.log(c.ok("  " + t.switchTo + " ") + modelBadge(m));
     if (m.provider === "openai" || m.provider === "google")
       console.log(c.dim("  ") + c.tool(t.providerRefuses(PROVIDERS[m.provider].name)));