@factiii/runner 0.10.0 → 0.10.2

package/index/index.js

@@ -92495,14 +92495,20 @@ function text(value) {
   return { content: [{ type: "text", text: value }] };
 }
 function makeTool(t) {
+  const args = t.args.strict();
   return {
     name: t.name,
     description: t.description,
     inputSchema: t.inputSchema,
-    handle: (raw) => t.run(t.args.parse(raw))
+    handle: (raw) => t.run(args.parse(raw))
   };
 }
-var objectSchema = (properties, required2) => ({ type: "object", properties, required: required2 });
+var objectSchema = (properties, required2) => ({
+  type: "object",
+  properties,
+  required: required2,
+  additionalProperties: false
+});
 function buildTools(store2, spaceSlug, fileBaseUrl) {
   return [
     makeTool({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@factiii/runner",
-  "version": "0.10.0",
+  "version": "0.10.2",
   "description": "Factiii Runner, run Board AI agents on a machine you control. Pairs with the Factiii web/mobile clients over WebRTC.",
   "license": "ISC",
   "keywords": [
@@ -23,6 +23,7 @@
   },
   "files": [
     "dist/cli.js",
+    "plugin/",
     "index/index.js",
     "index/image-package.json",
     "vendor/frpc-linux-amd64",

package/plugin/.claude-plugin/marketplace.json

@@ -0,0 +1,12 @@
+{
+  "name": "factiii-runner",
+  "description": "Everything a factiii runner hands its CLIs: session status hooks and workspace skills.",
+  "owner": { "name": "Factiii" },
+  "plugins": [
+    {
+      "name": "factiii",
+      "source": "./factiii",
+      "description": "Board terminal integration for claude and codex."
+    }
+  ]
+}

package/plugin/factiii/.claude-plugin/plugin.json

@@ -0,0 +1,7 @@
+{
+  "name": "factiii",
+  "version": "0.1.0",
+  "description": "Board terminal integration: reports what the agent is doing to the session's status dot, and ships the skills a factiii workspace provides.",
+  "author": { "name": "Factiii" },
+  "homepage": "https://factiii.com"
+}

package/plugin/factiii/bin/report-state.sh

@@ -0,0 +1,43 @@
+#!/usr/bin/env bash
+# Tell the runner what the agent is doing, so the board's status dot reflects
+# it. Called from hooks.json on the events both CLIs share.
+#
+# Everything is derived, nothing is injected. The runner sets a tmux session's
+# environment only when it CREATES the session (`new-session -A -e`), so a var
+# added by a runner upgrade never reaches a session that is already running —
+# which on any real host is most of them. TMUX_PANE is set by tmux itself at
+# pane creation, so it is already there in every session ever started.
+#
+# It doubles as the gate. This plugin installs globally, so its hooks fire on
+# every claude and codex run on this machine; outside a factiii workspace there
+# is no pane and no space redis to find, and this exits having done nothing.
+#
+# Never fails the CLI. A hook that exits non-zero can block the turn it fired
+# on, and a status dot is not worth interrupting someone's work for.
+set -u
+[ -n "${TMUX_PANE:-}" ] || exit 0
+
+# The space's redis sits at <spaceDir>/state/redis.sock and the CLI runs inside
+# that space's tree, so walk up for it. Bounded by reaching the root.
+dir="$PWD"
+sock=""
+while [ -n "$dir" ] && [ "$dir" != "/" ]; do
+  if [ -S "$dir/state/redis.sock" ]; then
+    sock="$dir/state/redis.sock"
+    break
+  fi
+  dir="$(dirname "$dir")"
+done
+[ -n "$sock" ] || exit 0
+
+state="${1:-idle}"
+# The pane is the identity; the runner resolves it to a session. Keeping that
+# mapping on the runner is what stops this script from having to know how tmux
+# sessions are named.
+#
+# SET then PUBLISH: the publish drives live dots, the key lets a subscriber
+# that starts mid-session read where things stand without waiting for a hook.
+# -t 2 so a dead socket costs milliseconds rather than hanging the turn.
+redis-cli -t 2 -s "$sock" set "agent-state:$TMUX_PANE" "$state" >/dev/null 2>&1
+redis-cli -t 2 -s "$sock" publish agent-state "$TMUX_PANE $state" >/dev/null 2>&1
+exit 0

package/plugin/factiii/hooks/hooks.json

@@ -0,0 +1,59 @@
+{
+  "hooks": {
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"${CLAUDE_PLUGIN_ROOT}/bin/report-state.sh\" working",
+            "timeout": 5
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"${CLAUDE_PLUGIN_ROOT}/bin/report-state.sh\" idle",
+            "timeout": 5
+          }
+        ]
+      }
+    ],
+    "PermissionRequest": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"${CLAUDE_PLUGIN_ROOT}/bin/report-state.sh\" blocked",
+            "timeout": 5
+          }
+        ]
+      }
+    ],
+    "Notification": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"${CLAUDE_PLUGIN_ROOT}/bin/report-state.sh\" blocked",
+            "timeout": 5
+          }
+        ]
+      }
+    ],
+    "SessionEnd": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"${CLAUDE_PLUGIN_ROOT}/bin/report-state.sh\" idle",
+            "timeout": 5
+          }
+        ]
+      }
+    ]
+  }
+}

package/plugin/factiii/skills/share-a-port/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: share-a-port
+description: Give a port running in this workspace a public HTTPS URL, with factiii-expose. TRIGGER when the user asks to share, expose, preview or publish a local server, wants a link to something running on localhost, or needs an external service to reach a local port.
+---
+
+# share-a-port
+
+This workspace can put a local port on the public internet. Both commands are
+already on your PATH; nothing needs installing.
+
+## Share a port
+
+```bash
+factiii-expose <port> <name>   # e.g. factiii-expose 3000 app
+```
+
+It prints the public URL and returns straight away - the tunnel runs in the
+background and lives until the session ends or you stop it.
+
+- `<name>` may hold letters, numbers and dashes only.
+- Re-running it with the same name replaces that tunnel rather than opening a
+  second one, so it is safe to repeat.
+- Start the server FIRST. A URL for a port nothing is listening on answers
+  with an error, which reads to the user like a broken tunnel.
+
+## Stop sharing
+
+```bash
+factiii-unexpose <name>
+```
+
+## Before you share
+
+The URL is public and unauthenticated: anyone holding the link reaches
+whatever that port serves. Do not expose a service that fronts real
+credentials, customer data, or a database. If you are unsure whether the user
+wants something reachable from outside, ask first.
+
+Always tell the user the URL you got back. They can also see every live
+tunnel, and stop any of them, in the card's Task Manager panel.
+