frizz 0.5.1 → 0.7.0

package/README.md

@@ -1,6 +1,6 @@
 <p align="center">
   <h1 align="center"><img src="assets/logo-concepts/final/fff-tile.png" alt="" width="104" height="104"><br/>Frizz</h1>
-  <p align="center">A local web UI for running many coding agents at once.
+  <p align="center">An opinionated agent console for extreme productivity.
     <br/>
     by <a href="https://x.com/colinhacks">@colinhacks</a>
   </p>
@@ -62,7 +62,7 @@ Frizz is a browser tab, a queue, and the agent CLIs you already pay for. It brin
 - 🐙 **GitHub integration.** Browse your repo's issues and pull requests without leaving the composer, and turn a selection of them into threads. Workers can read issues, diffs, and CI on their own.
 - 👀 **Built-in CI and PR watchers.** A worker waiting on a build or a review doesn't hand the thread back to you to be told "keep going." It watches, and picks the work back up when the run goes green or a review lands.
 - 📝 **No magic.** A thread behaves like a Claude Code session you started yourself. Frizz adds no worktrees, no branches, no dev server, no build integration, no workflow engine to fight with.
-- 🔒 **Local only.** No cloud, no account, no telemetry. The server binds `127.0.0.1` by default and its state lives in your user directory, never in your checkout.
+- 🔒 **Local only.** No cloud, no account, no telemetry. The server binds `127.0.0.1` by default and its state lives in your user directory, never in your checkout. To reach a board from a phone, put your own tunnel or proxy in front of it — see [Remote access](docs/remote-access.md).
 
 ### The queue
 
@@ -121,11 +121,12 @@ $ npx frizz --help
 
 Frizz production launcher
 
-Usage: npx frizz [options] [repository]
-       npx frizz up            serve this repo publicly, board + tunnel together
+Usage: npx frizz [options]
 
-Runs the npm-resolved immutable Frizz package, then opens it in your default browser. Use frizz-dev
-only for a source checkout.
+Run it in the directory you want to work in. One server serves EVERY project on this machine,
+each at its own /project/<name> URL, so a second run joins the one already going. Runs the
+npm-resolved immutable Frizz package, then opens it in your default browser. Use frizz-dev only
+for a source checkout.
 
 Options:
   --app                  use the legacy dedicated app window instead of a browser tab
@@ -134,6 +135,8 @@ Options:
   --host [address]       serve on a network address instead of loopback (bare --host means 0.0.0.0)
   --allowed-host <name>  with --host, also accept this DNS name as the board's address (repeatable)
   --public-origin <url>  serve behind a proxy/tunnel reachable at this exact origin
+  --cloud                serve at the saved hostname and run its Cloudflare tunnel as a child
+                         process; asked once, then remembered
   --link                 print a fresh single-use access link for the running board
   --debug                stream the full event feed to the terminal instead of the compact readout
   -h, --help             show this help
@@ -196,7 +199,7 @@ trades the code for a session cookie, so the link itself stops working the momen
 <details>
 <summary><b>Can I run it on several repos at once?</b></summary>
 
-> Yes — one server and one tab per repo, each fully isolated. There is deliberately no cross-repo board.
+> Yes. One Frizz server serves every project on your machine — you don't start one per repo. Run `frizz` in any of them and switch projects from the board; each project's threads, settings and state stay separate.
 
 </details>
 

package/dist/claude-agent-broker.js

@@ -19873,6 +19873,7 @@ var CLAUDE_BROKER_CAPABILITY_CANCEL_INPUT = "cancel-input-v1";
 var CLAUDE_BROKER_CAPABILITY_STOP_TASK = "stop-task-v1";
 var CLAUDE_BROKER_CAPABILITY_RELOAD_PLUGINS = "reload-plugins-v1";
 var CLAUDE_BROKER_CAPABILITY_RENAME = "rename-v1";
+var CLAUDE_BROKER_CAPABILITY_LIST_SKILLS = "list-skills-v1";
 var CLAUDE_INPUT_DROP_DIAGNOSTIC_PREFIX = "input dropped, the agent never received it";
 var ClaudeAgentSdkProtocolError = class extends Error {
   constructor(message) {
@@ -20255,6 +20256,7 @@ var RealClaudeQueryHandle = class {
   closing = false;
   closed = false;
   initialized = false;
+  initSkills = [];
   sdkQuery;
   input;
   diagnostic;
@@ -20364,6 +20366,21 @@ var RealClaudeQueryHandle = class {
       errorCount: Number.isFinite(result?.error_count) ? Number(result.error_count) : 0
     };
   }
+  // The session's invocable skills: the initialize handshake already carries every slash entry WITH
+  // its description (mapped and bounded above in mapControlInitialization — the same data the SDK's
+  // `supportedCommands()` would re-serve from its cache), and the init frame's `skills` array is the
+  // harness's own verdict on which of those are skills rather than built-in commands. The intersection
+  // is exactly "what `/name` invokes a skill", with descriptions, and zero frizz-side discovery.
+  async listSkills() {
+    const initialization = await this.initializationResult();
+    const skillNames = new Set(this.initSkills);
+    const skills = [];
+    for (const command of initialization.commands) {
+      if (!command.name || !skillNames.has(command.name)) continue;
+      skills.push({ name: command.name, description: command.description.slice(0, 1024) });
+    }
+    return skills;
+  }
   // Unqueue a follow-up the operator has taken back.
   //
   // `cancelAsyncMessage` is present at runtime in @anthropic-ai/claude-agent-sdk 0.3.207 but absent
@@ -20461,6 +20478,7 @@ var RealClaudeQueryHandle = class {
         }
         if (event.kind === "init") {
           if (event.sessionId !== this.sessionId) throw new ClaudeAgentSdkProtocolError("Claude session ownership mismatch");
+          this.initSkills = event.skills;
           if (this.initialized) {
             this.output.push(event);
             continue;
@@ -20642,7 +20660,7 @@ function startClaudeQuery(executablePath, options) {
       // `AGENTS.md` and its `.claude/skills`. Measured differential in the frizz repo, one variable:
       // this factory answered `NO-CLAUDE-MD` where a plain `claude -p` in the same cwd answered
       // "# No pull requests — land on local `main`". That fix restored PROJECT + LOCAL and left USER
-      // out, which kept a second, quieter half of the same regression: the tmux transport ran plain
+      // out, which kept a second, quieter half of the same regression: the retired transport ran plain
       // `claude` and got all three scopes, so a broker session was the only place the operator's
       // `~/.claude/settings.json` stopped applying. Measured 2026-08-16 against the maintainer's real
       // config, one variable: `--setting-sources=project,local` reported their `env` block UNSET where
@@ -20657,7 +20675,7 @@ function startClaudeQuery(executablePath, options) {
       ...options.disallowedTools?.length ? { disallowedTools: [...options.disallowedTools] } : {},
       persistSession: options.persistSession ?? false,
       // Keep Claude's default (preset) system prompt and APPEND the frizz worker contract, the SDK
-      // equivalent of the tmux path's --append-system-prompt-file.
+      // equivalent of the argv path's --append-system-prompt-file.
       ...options.appendSystemPrompt ? { systemPrompt: { type: "preset", preset: "claude_code", append: options.appendSystemPrompt } } : {},
       // The 1M context window rides the MODEL value as a `[1m]` suffix, always paired with the bare
       // alias as `fallbackModel` — an unavailable long-context beta is a hard 400 that kills the
@@ -21452,7 +21470,7 @@ function createClaudeBrokerExitWriter(path, meta, now = () => /* @__PURE__ */ ne
 }
 
 // packages/server/src/backend/claude-agent-broker.ts
-var BROKER_CAPABILITIES = [CLAUDE_BROKER_CAPABILITY_SUBAGENT_STEER, CLAUDE_BROKER_CAPABILITY_CANCEL_INPUT, CLAUDE_BROKER_CAPABILITY_STOP_TASK, CLAUDE_BROKER_CAPABILITY_RELOAD_PLUGINS, CLAUDE_BROKER_CAPABILITY_RENAME];
+var BROKER_CAPABILITIES = [CLAUDE_BROKER_CAPABILITY_SUBAGENT_STEER, CLAUDE_BROKER_CAPABILITY_CANCEL_INPUT, CLAUDE_BROKER_CAPABILITY_STOP_TASK, CLAUDE_BROKER_CAPABILITY_RELOAD_PLUGINS, CLAUDE_BROKER_CAPABILITY_RENAME, CLAUDE_BROKER_CAPABILITY_LIST_SKILLS];
 var IDLE_EXIT_MS = 6 * 60 * 60 * 1e3;
 var REACHABILITY_CHECK_MS = 3e4;
 var REACHABILITY_STRIKES = 2;
@@ -21502,9 +21520,10 @@ function runClaudeBroker(config) {
     pluginDir: config.pluginDir,
     mcpServers: config.mcpServers,
     allowedTools: config.allowedTools,
-    // NO `disallowedTools` here, and the asymmetry with the tmux path (WORKER_DISALLOWED_TOOLS →
-    // `--disallowedTools=AskUserQuestion`) is DELIBERATE. That flag exists because a tmux worker's
-    // question has nowhere to go: it opens a TUI dialog in a pane nobody is looking at. On this path it
+    // NO `disallowedTools` here, and the asymmetry with the argv path (WORKER_DISALLOWED_TOOLS →
+    // `--disallowedTools=AskUserQuestion`) is DELIBERATE. That flag exists because a worker launched as
+    // its own interactive `claude` process had nowhere to put the question: it opened a TUI dialog on a
+    // terminal screen nobody was looking at. On this path it
     // has somewhere to go — canUseTool routes it to a real dashboard question card, the operator answers
     // it, and the chosen labels reach the model. A follow-up sent instead of an answer retires the card
     // and unwinds the tool call (see retirePendingFor in the bridge), so a parked turn is still steerable.
@@ -21639,6 +21658,12 @@ function runClaudeBroker(config) {
             (reloaded) => write(sock, { t: "reload-result", requestId, reloaded }),
             (error) => write(sock, { t: "reload-result", requestId, error: error instanceof Error ? error.message : String(error) })
           );
+        } else if (msg.t === "list-skills") {
+          const requestId = msg.requestId;
+          void handle.listSkills().then(
+            (skills) => write(sock, { t: "skills-result", requestId, skills }),
+            (error) => write(sock, { t: "skills-result", requestId, error: error instanceof Error ? error.message : String(error) })
+          );
         } else if (msg.t === "set-mode") void handle.setPermissionMode(msg.mode).catch(() => {
         });
       }