@namzu/cli 34.1.1 → 36.0.0

package/dist/tui/web-activity.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"web-activity.d.ts","sourceRoot":"","sources":["../../src/tui/web-activity.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAIH,MAAM,MAAM,eAAe,GAAG,QAAQ,GAAG,OAAO,CAAA;AAEhD,oFAAoF;AACpF,MAAM,WAAW,WAAW;IAC3B,QAAQ,CAAC,IAAI,EAAE,eAAe,CAAA;IAC9B,sDAAsD;IACtD,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAA;IACxB,6EAA6E;IAC7E,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAA;IACzB,+EAA+E;IAC/E,QAAQ,CAAC,MAAM,CAAC,EAAE,OAAO,CAAA;CACzB;AAED,iFAAiF;AACjF,wBAAgB,eAAe,CAAC,QAAQ,EAAE,MAAM,GAAG,eAAe,GAAG,SAAS,CAI7E;AAED;;;;;;GAMG;AACH,wBAAgB,oBAAoB,CAAC,QAAQ,EAAE,MAAM,EAAE,KAAK,EAAE,OAAO,GAAG,WAAW,GAAG,SAAS,CAU9F;AAED,iGAAiG;AACjG,wBAAgB,YAAY,CAAC,QAAQ,EAAE,WAAW,GAAG,MAAM,CAI1D;AAED,wCAAwC;AACxC,wBAAgB,aAAa,CAAC,QAAQ,EAAE,WAAW,GAAG,MAAM,CAI3D;AAED,uDAAuD;AACvD,wBAAgB,cAAc,CAC7B,QAAQ,EAAE,WAAW,EACrB,OAAO,EAAE;IAAE,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAA;CAAE,GAChE,MAAM,CASR;AAED;;;;;;GAMG;AACH,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,GAAG,SAAS,CAOjF;AAED,gCAAgC;AAChC,wBAAgB,WAAW,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAIjD"}
+{"version":3,"file":"web-activity.d.ts","sourceRoot":"","sources":["../../src/tui/web-activity.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,OAAO,EAAE,UAAU,EAAE,MAAM,mBAAmB,CAAA;AAG9C,MAAM,MAAM,eAAe,GAAG,QAAQ,GAAG,OAAO,CAAA;AAEhD,oFAAoF;AACpF,MAAM,WAAW,WAAW;IAC3B,QAAQ,CAAC,IAAI,EAAE,eAAe,CAAA;IAC9B,sDAAsD;IACtD,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAA;IACxB,6EAA6E;IAC7E,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAA;IACzB,+EAA+E;IAC/E,QAAQ,CAAC,MAAM,CAAC,EAAE,OAAO,CAAA;CACzB;AAED,iFAAiF;AACjF,wBAAgB,eAAe,CAAC,QAAQ,EAAE,MAAM,GAAG,eAAe,GAAG,SAAS,CAI7E;AAED;;;;;;GAMG;AACH,wBAAgB,oBAAoB,CAAC,QAAQ,EAAE,MAAM,EAAE,KAAK,EAAE,OAAO,GAAG,WAAW,GAAG,SAAS,CAU9F;AAED,iGAAiG;AACjG,wBAAgB,YAAY,CAAC,QAAQ,EAAE,WAAW,GAAG,MAAM,CAI1D;AAED,wCAAwC;AACxC,wBAAgB,aAAa,CAAC,QAAQ,EAAE,WAAW,GAAG,MAAM,CAI3D;AAED,uDAAuD;AACvD,wBAAgB,cAAc,CAC7B,QAAQ,EAAE,WAAW,EACrB,OAAO,EAAE;IAAE,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAA;CAAE,GAChE,MAAM,CASR;AAED;;;;;;GAMG;AACH,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,GAAG,SAAS,CAOjF;AAED,mCAAmC;AACnC,eAAO,MAAM,WAAW,mBAAa,CAAA"}

package/dist/tui/zen-free-refusal.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Zen answers a keyless free-model request with HTTP 403 and a body saying the free tier is not
+ * available to this client. Nothing about the person's key is wrong (none was sent), so the
+ * screens say that Zen did not accept the free model and offer the ways on, and keep the
+ * service's own words for the Details / debug view.
+ */
+/** What happened, in the words a person reads. */
+export declare const ZEN_FREE_REFUSED_WHAT = "Zen didn\u2019t accept the free model right now.";
+/** What to do, for a surface with a model picker command. */
+export declare const ZEN_FREE_REFUSED_NEXT = "Try again in a while, or choose another provider. A Zen API key also works.";
+/** Exactly the keyless free-tier refusal; any other 403 keeps its own copy. */
+export declare function isZenFreeTierRefusal(facts: {
+    readonly providerId?: string | undefined;
+    readonly status?: number | undefined;
+    readonly detail?: string | undefined;
+}): boolean;
+//# sourceMappingURL=zen-free-refusal.d.ts.map

package/dist/tui/zen-free-refusal.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"zen-free-refusal.d.ts","sourceRoot":"","sources":["../../src/tui/zen-free-refusal.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,kDAAkD;AAClD,eAAO,MAAM,qBAAqB,qDAAgD,CAAA;AAElF,6DAA6D;AAC7D,eAAO,MAAM,qBAAqB,gFAC4C,CAAA;AAE9E,+EAA+E;AAC/E,wBAAgB,oBAAoB,CAAC,KAAK,EAAE;IAC3C,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,GAAG,SAAS,CAAA;IACxC,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,GAAG,SAAS,CAAA;IACpC,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,GAAG,SAAS,CAAA;CACpC,GAAG,OAAO,CAIV"}

package/dist/usage-error.d.ts

@@ -0,0 +1,15 @@
+/**
+ * How a command-line mistake reads.
+ *
+ * Commander writes `error: option '--effort <level>' argument 'turbo' is
+ * invalid. Allowed choices are none, minimal, low…` as one unbroken line. That
+ * is a log line, not a sentence for a person: it starts in lower case, carries
+ * no full stop when the cause is short, and runs past the edge of the terminal.
+ * This turns it into sentences in sentence case, wrapped at word boundaries,
+ * and points at `--help` once. The exit code is not decided here.
+ */
+/** Wrap one line at spaces to `width` columns. A word longer than the width keeps its own row. */
+export declare function wrapAtWords(line: string, width: number): string[];
+/** Commander's complaint as sentences, wrapped, with the way forward on its own line. */
+export declare function formatUsageError(text: string, columns: number | undefined): string;
+//# sourceMappingURL=usage-error.d.ts.map

package/dist/usage-error.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"usage-error.d.ts","sourceRoot":"","sources":["../src/usage-error.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAIH,kGAAkG;AAClG,wBAAgB,WAAW,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE,CAejE;AAoBD,yFAAyF;AACzF,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,CAoBlF"}

package/dist/warning-filter.d.ts

@@ -0,0 +1,30 @@
+/**
+ * The one Node warning the terminal never shows.
+ *
+ * Node 22 prints `(node:1234) ExperimentalWarning: SQLite is an experimental
+ * feature and might change at any time` the first time `node:sqlite` loads,
+ * above the banner, and a person reads it as Namzu being unsure of itself. The
+ * session index uses `node:sqlite` on purpose (and falls back to a scan where
+ * it does not load), so the notice tells nobody anything they can act on.
+ *
+ * Exactly that warning is dropped, and only that one: the type must be
+ * `ExperimentalWarning` and the text must be Node's own sentence about SQLite.
+ * Any other warning, including every other experimental feature, still prints.
+ *
+ * This is installed by importing the module first in each entry (`bin.ts`),
+ * before anything can load `node:sqlite`; ESM evaluates imports in order, so a
+ * side-effect import at the top is earlier than any import below it.
+ */
+type EmitWarning = typeof process.emitWarning;
+interface WarningTarget {
+    emitWarning: EmitWarning;
+}
+/** Whether these `emitWarning` arguments are Node's SQLite experimental notice. */
+export declare function isSqliteExperimentalWarning(warning: unknown, rest: readonly unknown[]): boolean;
+/**
+ * Wrap `target.emitWarning` so the SQLite notice is dropped. Returns a function
+ * that puts the original back; calling it twice is harmless.
+ */
+export declare function suppressSqliteExperimentalWarning(target?: WarningTarget): () => void;
+export {};
+//# sourceMappingURL=warning-filter.d.ts.map

package/dist/warning-filter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"warning-filter.d.ts","sourceRoot":"","sources":["../src/warning-filter.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAIH,KAAK,WAAW,GAAG,OAAO,OAAO,CAAC,WAAW,CAAA;AAE7C,UAAU,aAAa;IACtB,WAAW,EAAE,WAAW,CAAA;CACxB;AAED,mFAAmF;AACnF,wBAAgB,2BAA2B,CAAC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,SAAS,OAAO,EAAE,GAAG,OAAO,CAc/F;AAED;;;GAGG;AACH,wBAAgB,iCAAiC,CAChD,MAAM,GAAE,aAAmD,GACzD,MAAM,IAAI,CAUZ"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@namzu/cli",
-  "version": "34.1.1",
+  "version": "36.0.0",
   "description": "Interactive and headless terminal agent for Namzu, with provider discovery, durable sessions, tools and diagnostics.",
   "keywords": [
     "namzu",
@@ -38,32 +38,40 @@
     "!dist/**/__fixtures__",
     "!dist/**/test-setup.*",
     "skills",
+    "assets/pal-blender-mcp.py",
+    "assets/pal-godot-mcp.cjs",
+    "assets/pal-godot-mcp-pin.json",
     "README.md",
     "CHANGELOG.md"
   ],
   "dependencies": {
+    "@jitl/quickjs-wasmfile-release-sync": "0.32.0",
     "@modelcontextprotocol/client": "^2.1.0",
+    "@xterm/addon-serialize": "0.14.0",
+    "@xterm/headless": "6.0.0",
     "commander": "^14.0.3",
     "ink": "7.0.3",
+    "quickjs-emscripten-core": "0.32.0",
     "react": "19.2.6",
     "string-width": "8.2.1",
     "yaml": "^2.9.0",
-    "@namzu/browser": "2.0.0",
-    "@namzu/anthropic": "6.2.2",
-    "@namzu/files": "1.1.2",
-    "@namzu/deepseek": "^2.0.2",
+    "@namzu/anthropic": "6.3.0",
+    "@namzu/browser": "2.0.1",
     "@namzu/computer-use": "3.1.0",
-    "@namzu/openai": "4.1.3",
+    "@namzu/deepseek": "^2.0.2",
+    "@namzu/files": "1.1.2",
+    "@namzu/google": "^1.1.2",
     "@namzu/ollama": "2.2.5",
-    "@namzu/sdk": "^48.3.1",
+    "@namzu/openai": "4.1.4",
     "@namzu/openrouter": "3.0.3",
-    "@namzu/google": "^1.1.1",
-    "@namzu/zen": "^3.1.0"
+    "@namzu/sandbox": "^25.0.0",
+    "@namzu/sdk": "^50.0.0",
+    "@namzu/zen": "^4.0.0"
   },
   "devDependencies": {
     "@biomejs/biome": "^1.9.4",
     "@types/react": "^19.2.15",
-    "@xterm/headless": "^6.0.0",
+    "esbuild": "0.28.1",
     "ink-testing-library": "^4.0.0",
     "typescript": "^5.5.0",
     "vitest": "^4.1.11",
@@ -75,8 +83,11 @@
   "publishConfig": {
     "access": "public"
   },
+  "optionalDependencies": {
+    "node-pty": "1.1.0"
+  },
   "scripts": {
-    "build": "tsc --build && chmod +x dist/bin.js",
+    "build": "tsc --build && node scripts/bundle.mjs && chmod +x dist/bin.js",
     "dev": "tsc --build --watch",
     "typecheck": "tsc --noEmit",
     "lint": "biome check src/",

package/skills/schedule-task/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: schedule-task
-description: How to propose a scheduled job that runs later with nobody watching - choosing its permission set, schedule, time zone and budget, and wording its prompt for an unattended run. Use when the user asks for something to happen on a schedule, every night, every hour, at a time, or while namzu is closed.
+description: How to choose an open-conversation loop or propose a durable scheduled job, with its workspace, permissions, schedule, time zone and budget. Use when the user asks for something to repeat, happen later, or run while namzu is closed.
 invocation: both
 metadata:
   namzu-requires-tools: schedule
@@ -8,7 +8,17 @@ metadata:
 
 # Scheduling a task
 
-A scheduled job runs later in a folder with **nobody watching**. An agent
+First decide whether the request belongs to this open conversation or needs
+to survive when Namzu closes. For a repeat in this same conversation **only
+while the TUI is open**, use `session_loop` (or tell the operator `/loop`). It
+re-sends the prompt between turns under the conversation's current permission
+mode. It stops firing when the TUI closes; resuming the conversation later
+restores an unexpired loop. Never describe `/loop` as a background service.
+
+For a durable task, use `schedule`. It runs later with **nobody watching**,
+including while Namzu is closed when the scheduler service is installed. The
+conversation that requested a job owns it and can receive its important
+result; that is separate from the directory in which a run executes. An agent
 job runs a prompt in a new conversation; a pure script job runs the exact
 confirmed script with no model or session. It cannot ask questions. An agent
 call that its permission set does not allow either waits for the operator
@@ -20,6 +30,31 @@ until they do.
 Ask the user whatever you cannot infer, then propose. Do not create a job
 the user did not ask for.
 
+Check the tools actually offered in this session before proposing the work.
+Permission rules authorize tools; they do not install or mount them. For example,
+allowing `web_fetch` does not make it available when only `web_search` is offered.
+Do not investigate installed package files to invent an unavailable output tool.
+If the requested page or artifact service is absent, explain that gap and agree
+on a supported output before promising the job. A local HTML file written with
+`write` is a file, not an integrated artifact page.
+
+Keep unattended research bounded and reserve budget for writing its result.
+The token budget covers cumulative model input and output across iterations,
+including search results sent again on later requests. It is not the model's
+context-window size. A long series of broad searches can exhaust it before any
+output file is written. Tool calls made together belong to one model iteration;
+do not equate the iteration budget with the number of tool calls.
+
+If the task needs no project files, do not create a visible project folder
+merely because the current directory is home, root or `NAMZU_HOME`. Use the
+job's `workspace: "none"` option with `kind: "script"`, and omit `folder`.
+The scheduler makes a private working directory after confirmation. This
+changes the working directory, not the script's authority: it still runs as
+the operator on the host, and the directory is not a write boundary. The
+source conversation can receive the significant result. If a task does
+need project files, use the actual existing project folder; ask the user when
+the project cannot be identified.
+
 ## 0. Choosing a kind
 
 `kind` picks what the run does; it changes what every later section means,
@@ -81,6 +116,17 @@ generic “finished” desktop notice after successful no-change runs. This
 choice does not turn off failure or approval notices; leave it unset for
 jobs where routine completion notices are wanted (subject to rate limits).
 
+For a pure script that should report a result only when something changes,
+set `script.report: "json-v1"`. It must print exactly one JSON object line
+to stdout: `{"v":1,"state":"quiet"}` for no change, or
+`{"v":1,"state":"changed","summary":"what changed"}` for a result.
+An optional string `nextState` persists in scheduler-owned state; the
+previous value arrives as `NAMZU_SCHEDULE_STATE`. Keep diagnostic output on
+stderr so stdout stays one JSON line. The operator reviews this protocol
+and the exact script. The raw JSON is not the result shown in the source
+conversation. Omit `report` for an ordinary script; it is not supported on
+`script+agent` gates.
+
 The operator confirms the **exact script text**, once; a later change needs
 re-confirmation, so do not propose a script expecting to iterate on it live
 — get it right, or `update` it (which asks again).
@@ -185,18 +231,22 @@ minute (`7 3 * * *`) to the top of the hour for anything not time-critical.
 ## 3. Budget
 
 `budget` is the limits of ONE run, not of the job. Leave it unset unless
-the user asked for limits: the defaults are 500 000 tokens and 30 minutes a
-run (or the operator's `limits`). If you set it:
+the user asked for limits: tokens default to unlimited (`tokenBudget: 0`),
+with 50 model steps and 30 minutes a run (or the operator's `limits`). Do not
+invent a finite token allowance. If you set it:
 
-- `tokenBudget` is every token the run spends. Each model call resends the
+- `tokenBudget: 0` removes the token limit, including an inherited positive
+  value. A positive `tokenBudget` limits every token the run spends. Each model call resends the
   whole prompt (often 10 000 to 30 000 tokens), so a run needs far more
   than its answer; the confirmation warns below 50 000.
 - `maxIterations` is model steps in one run (each model call with its tool
   calls), not how many times the job runs. A browser task takes 10 or more.
 - `timeoutMs` is one run's wall clock.
 
-The confirmation shows the most the job can spend in a day (runs per day
-times the token budget).
+For a positive token budget, the confirmation shows the daily token allowance
+(runs per day times the token budget). Unlimited jobs show no daily token limit;
+this does not mean their usage is zero. Existing saved jobs retain their
+confirmed limits until the operator confirms an update.
 
 ## 4. The prompt: written for nobody watching
 
@@ -205,7 +255,8 @@ alone:
 
 - Say what to do, in which files or commands, and what "done" means.
 - Say where the result goes: a file to write, or the run's final message
-  (the operator reads it in the run's conversation).
+  (the operator reads it in the run's conversation). For a job owned by the
+  source conversation, state what significant result should appear there.
 - Say what to do when something is missing or fails: stop and report it in
   the final message. Never guess, never retry destructively.
 - Name the commands the rules allow, so the run does not wander into calls
@@ -225,24 +276,27 @@ report its error. Do not install or change anything."
 
 Call `schedule` with `name` (lowercase, digits, dashes), `when` and
 `permissions`, plus `prompt` (unless `kind` is `"script"`) and `script`
-(when `kind` is not `"agent"`). Leave `folder` unset only when the session's
-folder is a valid job folder. The file system root, the operator's home
-directory itself, `NAMZU_HOME`, and any folder containing `NAMZU_HOME` are
-refused. If the session is in one of those, choose an existing project
-subfolder or create a dedicated one when permitted, then set `folder`
-explicitly. Leave `tz`, `execution`, `budget` and `headed` unset unless the
-user asked for them. The operator sees one confirmation screen with the job
+(when `kind` is not `"agent"`). For a job that needs project files, leave
+`folder` unset only when the session's folder is the actual project and a
+valid job folder. The file system root, the operator's home directory itself,
+`NAMZU_HOME`, and any folder containing `NAMZU_HOME` are refused. In those
+locations, set `folder` to the actual existing project directory. For a
+project-free pure script, set `workspace: "none"` and omit `folder` instead
+of making a directory for the job. Leave `tz`, `execution`, `budget` and
+`headed` unset unless the user asked for them. The operator sees one
+confirmation screen with the job
 as it will run, and every value you set that differs from the default is
 marked as yours. Do not ask them to confirm again in chat. Afterwards,
 `schedule` with `action: "list"` shows every job, in any folder, and the
 operator manages them with `/schedule` or `namzu schedule list`.
 
 To change a job, call `schedule` with `action: "update"`, `job` (its name)
-and only the fields that change (`prompt`, `when`, `folder`, `tz`, `budget`,
-`notifyOnFinish`, or `permissions` as the whole new set). The operator sees what changes and
-confirms it; the job keeps its history. Never delete a job and create it
-again to change it: its history is lost. Jobs run only when the scheduler service is
-installed: if the result says none is installed, tell the user to run
+and only the fields that change (`prompt`, `when`, `folder`, `workspace`,
+`kind`, `script`, `tz`, `budget`, `notifyOnFinish`, or `permissions` as the
+whole new set). The operator sees what changes and confirms it; the job
+keeps its history. Never delete a job and create it again to change it: its
+history is lost. Jobs run only when the scheduler service is installed: if
+the result says none is installed, tell the user to run
 `namzu schedule install`; do not say the job is set up and running.
 
 ## Browser access