agent-office-studio 0.2.0 → 0.3.0

package/dist/index.html

@@ -25,12 +25,13 @@
       })();
     </script>
     <title>Agent Office</title>
-    <script type="module" crossorigin src="/assets/index-CozPk6R9.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-i7sU9SN-.css">
+    <script type="module" crossorigin src="/assets/index-DgXF8Kqx.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-D5IzEWKU.css">
   </head>
   <body>
     <div class="app" id="app" data-m="office">
       <aside class="side">
+        <div class="side-grip" id="side-grip" role="separator" aria-orientation="vertical" aria-label="Resize the side panel" tabindex="0"></div>
         <header class="brand">
           <div class="title">
             <h1>Agent Office</h1>
@@ -39,6 +40,9 @@
               <button type="button" class="theme-btn" id="lbBtn" aria-label="Leaderboard" aria-haspopup="true" aria-expanded="false" title="Leaderboard">
                 <svg viewBox="0 0 24 24"><path d="M8 4h8v5a4 4 0 0 1-8 0z"/><path d="M8 6H5v1a3 3 0 0 0 3 3"/><path d="M16 6h3v1a3 3 0 0 1-3 3"/><path d="M12 13v4"/><path d="M8.5 20h7"/></svg>
               </button>
+              <button type="button" class="theme-btn" id="linkBtn" aria-label="Linked offices" aria-haspopup="true" aria-expanded="false" title="Linked offices">
+                <svg viewBox="0 0 24 24"><path d="M10 14a4.5 4.5 0 0 0 6.4 0l3-3a4.5 4.5 0 0 0-6.4-6.4l-1.2 1.2"/><path d="M14 10a4.5 4.5 0 0 0-6.4 0l-3 3a4.5 4.5 0 0 0 6.4 6.4l1.2-1.2"/></svg>
+              </button>
               <button type="button" class="theme-btn" id="acctBtn" aria-label="Claude access" aria-haspopup="true" aria-expanded="false" title="Claude access">
                 <svg viewBox="0 0 24 24"><circle cx="8" cy="15" r="4"/><path d="M10.8 12.2 20 3"/><path d="m17 6 3 3"/><path d="m14.5 8.5 2 2"/></svg>
               </button>
@@ -48,6 +52,7 @@
             </span>
             <div class="theme-pop" id="themePop" role="dialog" aria-label="Appearance" hidden></div>
             <div class="theme-pop lb-pop" id="lbPop" role="dialog" aria-label="Leaderboard" hidden></div>
+            <div class="theme-pop link-pop" id="linkPop" role="dialog" aria-label="Linked offices" hidden></div>
             <div class="theme-pop acct-pop" id="acctPop" role="dialog" aria-label="Claude access" hidden></div>
           </div>
           <div class="level">

package/docs/README.md

@@ -11,6 +11,7 @@
 - [Using the office](using-the-office.md) — the chat, channels, threads, standup, the break room
 - [Jobs](jobs.md) — clearance, which model, what changed
 - [The leaderboard](leaderboard.md) — an optional board of jobs, tokens and agent time
+- [Linked offices](linked-offices.md) — see a friend's agents in your office, and invite guests to run yours
 
 **Setting it up**
 - [Claude access](claude-access.md) — Claude Code login or API key, and the plan meters

package/docs/configuration.md

@@ -10,8 +10,9 @@ voice toggle, team profiles, theme — are made in the office and remembered.
 |---|---|---|
 | `OFFICE_ROOT` | the folder above this one; with `agentoffice`, the folder you run it from | its subfolders are the projects |
 | `OFFICE_DATA` | `data/` here; with `agentoffice`, `~/.agent-office` | where the office keeps its state |
-| `PORT` | `4317` | |
+| `PORT` | `4317` | with `agentoffice`, a free port is chosen if this is taken (or `--port <n>`); one you set is used as given |
 | `OFFICE_ALLOWED_HOSTS` | none | extra hostnames to accept, comma-separated; see [On your phone](phone.md) |
+| `OFFICE_SHARE_JOB_TITLES` | unset | `1` lets linked offices see your agents' job titles, not just that they're busy |
 
 ## Claude
 
@@ -46,7 +47,7 @@ voice toggle, team profiles, theme — are made in the office and remembered.
 
 | Env | Default | |
 |---|---|---|
-| `OFFICE_LEADERBOARD_URL` | unset | address of a leaderboard service; see [The leaderboard](leaderboard.md) |
+| `OFFICE_LEADERBOARD_URL` | the hosted board | address of a different leaderboard service; see [The leaderboard](leaderboard.md) |
 | `OFFICE_TERMINAL` | unset | `1` opens the in-app terminal |
 | `OFFICE_TERMINAL_SHELL` | your `$SHELL` | |
 | `OFFICE_TERMINAL_MAX` | `4` | sessions at once |

package/docs/getting-started.md

@@ -18,7 +18,10 @@ npm install
 npm start            # builds, then serves on http://localhost:4317
 ```
 
-Open <http://localhost:4317>.
+Open the link it prints, `Agent Office open on http://localhost:4317/?key=…`.
+The key keeps other accounts on the machine out; your browser remembers it, so
+after that <http://localhost:4317> is enough. Lost the link? `agentoffice --link`,
+or from a clone, the key is in `data/office-key`.
 
 ## Where your projects are
 

package/docs/guides/troubleshooting.md

@@ -5,8 +5,9 @@ Find the message you're seeing, or the symptom.
 ## The office won't start
 
 **`Error: listen EADDRINUSE: address already in use 127.0.0.1:4317`**
-Something is already on that port — usually another office. Find it with
-`lsof -i :4317`, or start this one elsewhere: `PORT=4400 npm start`.
+Something is already on that port — usually another office. `agentoffice`
+picks a free port on its own; to choose, use `agentoffice --port 4400`. With
+`npm start`, find the other one with `lsof -i :4317` or set `PORT=4400`.
 
 **The page says "No build yet."**
 The server is running but `dist/` is empty. Run `npm run build`, or use
@@ -18,6 +19,16 @@ remote desktops and VMs), the 3D view can't draw.
 
 ## Jobs don't run
 
+**Every message gets "I couldn't route that one".**
+The chief is a short `claude -p` call, and it failed. The words after the colon
+say why: an error from `claude` itself (signed out, out of credit, a model your
+plan can't use), a timeout, or `claude` exiting without answering. To see the
+same thing yourself, run this in the terminal you start the office from:
+`claude -p --model sonnet "hi"`. It should answer within a few seconds. Fix
+whatever it complains about, then send the message again. Versions before
+0.3.0 only ever said "The chief could not decide"; update to see the reason.
+`/standup` and `/restart` don't go through the chief.
+
 **A job fails with "Could not start claude: spawn claude ENOENT".**
 Claude Code isn't on the `PATH` the office was started with. Check
 `which claude` in the same terminal. If it lives somewhere unusual, point the

package/docs/leaderboard.md

@@ -1,7 +1,8 @@
 # The leaderboard
 
 An optional board where offices compare how much they got done. It is off
-until you join, and it needs a leaderboard service somebody hosts (see
+until you join. Every office uses the same hosted service, https://agent-office-leaderboard.agent-office-leaderboard.workers.dev,
+so there is nothing to set up (the service's code is in
 [`leaderboard/`](../leaderboard/README.md)).
 
 ## What is ranked
@@ -49,17 +50,18 @@ those day counters. Boards list handles and totals.
 ## Leaving
 
 "Leave and delete my data" asks the service to delete your handle and counters,
-then forgets the secret here. If the service can't be reached, nothing changes
+then forgets the secret here. If you have [linked offices](linked-offices.md), only your counters are deleted: the handle stays, because the links need it. If the service can't be reached, nothing changes
 and you can try again. Your local `data/activity.json` stays; delete it if you
 want that gone too.
 
-## Setting it up
+## Using a different service
 
-Set the address of your service and restart the office:
+The hosted address is built in. To use a board you host yourself instead, set
+its address and restart the office:
 
 ```
 OFFICE_LEADERBOARD_URL=https://your-service.example npm start
 ```
 
-It must be `https` (plain `http` works only for `localhost`). Without it the
-panel says no leaderboard is set up and nothing is ever sent.
+It must be `https` (plain `http` works only for `localhost`). Either way,
+nothing is sent until you join.

package/docs/linked-offices.md

@@ -0,0 +1,81 @@
+# Linked offices
+
+Two Agent Offices on different machines can link with a code. Linked offices see
+each other's agents walk into their 3D office as visitors. An office can also
+invite a **guest**, who can then start jobs with the host's agents, within limits
+the host sets.
+
+Linking is off until you make or enter a code. It uses the same hosted service
+as [the leaderboard](leaderboard.md), so there is nothing to set up.
+
+## Linking two offices
+
+1. One of you opens the chain button in the sidebar header and picks **Invite
+   an office**. If your office has no handle yet, it asks for one first. A
+   handle doesn't put you on the leaderboard.
+2. Send the code (it looks like `K7QX-M2PD`) to the other person however you
+   like. It works once and expires after 24 hours.
+3. They open the chain button, pick **Enter a code**, and paste it in. Case,
+   dashes and spaces don't matter.
+
+Either of you can **Unlink** from the same panel at any time.
+
+## What a linked office sees
+
+Your agents' names, roles, looks, what they are doing (working, idle, on a
+break, in a meeting, gone home). That's all: no job titles, projects, files,
+logs, prompts, chat or cost. To let linked offices see the titles of the jobs
+your agents are on, start the office with `OFFICE_SHARE_JOB_TITLES=1`.
+
+Their agents walk in at the door, wear a visitor tint, and carry the office's
+handle on their nameplate (`Kai · @friend`). They don't use your desks. When
+they're working they stand at the hot desks, and on a break they join the pool
+table or the coffee. Up to six visitors are shown at once; the rest are counted
+on a sign by the door.
+
+## Inviting a guest
+
+A guest can start jobs with your agents, in your projects, on your Claude
+account. Pick **Invite a guest** and choose:
+
+- **Projects:** at least one. The guest can't see or touch any other project.
+- **Clearance cap:** *Plan only*, or *Edit files* (the default). *Full autonomy*
+  has to be ticked on its own. It lets the guest run any command on this
+  machine.
+- **Tokens per day:** 2,000,000 by default. Once a guest has used their tokens,
+  their running jobs stop and new ones are refused until midnight UTC.
+
+A guest can start up to three jobs at a time, reply to them, stop them, and see
+their logs and changes. They can't see your other jobs, chat or channels, and
+they can't use the terminal, restart the office, or change staff or settings.
+Their jobs show `from @handle` in your job list, and you can stop any of them.
+Agents working for a guest can't message or hand work to your other agents.
+They also don't get your MCP servers or claude.ai connectors (mail, Slack,
+calendar and so on), your user-level Claude Code settings and hooks, your
+Claude Code memory, or your attachments.
+Unlinking a guest stops their running jobs straight away.
+
+Even at *Edit files*, a guest can change files that run later, such as
+`package.json` scripts, build files or git hooks. Only invite someone you would
+trust with those projects. *Plan only* is the safe choice.
+
+## Visiting as a guest
+
+When an office has made you its guest, its row in the Links panel has **Visit
+@host**. It opens the host's office, showing their agents and your jobs there.
+A bar at the top shows whose office you're in and your limits, and **Back to my
+office** takes you home. Only the projects and clearances you're allowed are
+offered.
+
+## What the service keeps
+
+Your handle, a hash of your office's secret, which offices you're linked to, and
+open invites (as hashes of the codes). Presence and messages pass through
+without being stored. Guest limits and token counts stay on the host's machine,
+in `data/links.json` and `data/guests.json`.
+
+## Using a different service
+
+`OFFICE_LEADERBOARD_URL` points linking at another service too, as described in
+[The leaderboard](leaderboard.md#using-a-different-service). Offices can only
+link if they use the same service.

package/docs/phone.md

@@ -22,6 +22,10 @@ OFFICE_ALLOWED_HOSTS=my-mac.tail1234.ts.net npm start
 `OFFICE_ALLOWED_HOSTS` takes exact hostnames, comma-separated. Every other
 host and origin is still refused.
 
+On the phone, open the tailnet address once with the office key on the end,
+`https://my-mac.tail1234.ts.net/?key=…` (the key is in the link the office
+printed, or `agentoffice --link`). The phone keeps it after that.
+
 **Read this first.** Whoever can open that address can run Claude in your
 projects with full autonomy, and — if `OFFICE_TERMINAL=1` — get a shell on
 this machine. Only expose it on a tailnet that is just you. Never put it on

package/docs/security.md

@@ -8,7 +8,14 @@ hand out a shell. It is built to be used by one person, on their own machine.
 - The server listens on `127.0.0.1` only.
 - Every request's `Host` and `Origin` must be local (or a name in
   `OFFICE_ALLOWED_HOSTS`), which keeps other websites and DNS-rebinding
-  attacks out of it.
+  attacks out of it. A page on another localhost port counts as another
+  website.
+- The office has a key, made on first start and kept in `data/office-key` with
+  mode `0600`. Other accounts on the machine can reach `127.0.0.1` too, so the
+  page, the API and the socket all need the key. The address the office prints
+  when it starts carries the key once; your browser keeps it in a cookie
+  (HttpOnly, SameSite=Strict). `agentoffice --link` prints that address again.
+  Delete `data/office-key` and restart to sign every browser out.
 - Agents call back into the office (the roster, messages, hand-offs) with a
   per-job token that dies with the job.
 
@@ -37,10 +44,35 @@ command you could.
 
 Off until you join, and then the only thing besides Claude that the office
 talks to. It sends a handle and three counters per day (jobs, tokens, agent
-time) to the service named by `OFFICE_LEADERBOARD_URL`, signed with a random
+time) to the hosted leaderboard service (or the one named by
+`OFFICE_LEADERBOARD_URL`), signed with a random
 secret kept in `data/leaderboard.json` (mode `0600`). Never prompts, projects,
 files, chat or cost. Details in [The leaderboard](leaderboard.md).
 
+## Linked offices and guests
+
+Off until you make or enter a code. The office only ever connects out to the
+service, so nothing listens for other offices. A link shares your agents' names,
+roles, looks and states (working, on a break and so on), and nothing else. Job
+titles stay home, since a title is the first line of a prompt;
+`OFFICE_SHARE_JOB_TITLES=1` shares them. Everything a linked office
+sends is checked and trimmed before your browser sees it.
+
+A **guest** runs jobs on your machine, on your Claude account. Everything is
+enforced on your side and the guest's office is never trusted:
+
+- only the projects you picked;
+- at or below the clearance cap you set;
+- within the tokens per day you set;
+- no terminal, settings, chat, or other people's jobs;
+- their agents can't reach your other agents;
+- their jobs don't get your MCP servers or claude.ai connectors, your
+  user-level Claude Code settings and hooks, or your Claude Code memory.
+
+Even *Edit files* can change scripts or hooks that run later, so invite only
+people you would trust with those projects. Details in
+[Linked offices](linked-offices.md).
+
 ## The terminal
 
 Off unless `OFFICE_TERMINAL=1`. A session needs a single-use ticket from the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-office-studio",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "A 3D office where the staff are Claude Code agents.",
   "license": "MIT",
   "files": [
@@ -9,6 +9,7 @@
     "server",
     "shared",
     "docs",
+    "!docs/proposals",
     "CHANGELOG.md",
     "LICENSE",
     "README.md"
@@ -44,7 +45,7 @@
     "start": "vite build && node server/supervise.js",
     "voice:model": "mkdir -p data/whisper && curl -L --progress-bar -o data/whisper/ggml-base.en.bin https://huggingface.co/ggerganov/whisper.cpp/resolve/main/ggml-base.en.bin",
     "voice:piper": "python3 -m venv data/piper/venv && data/piper/venv/bin/pip install -q piper-tts && data/piper/venv/bin/python -m piper.download_voices --data-dir data/piper/voices en_GB-cori-high en_US-amy-medium en_GB-alan-medium en_US-kristin-medium en_US-ryan-high en_GB-alba-medium en_GB-aru-medium en_US-john-medium en_US-hfc_female-medium",
-    "test": "node scripts/smoke.mjs",
+    "test": "node scripts/smoke.mjs && node scripts/guests.mjs",
     "prepack": "vite build"
   },
   "dependencies": {

package/server/changes.js

@@ -11,7 +11,9 @@ const MAX_FILES = 200;
 const MAX_DIFF = 400 * 1024;
 
 const git = (cwd, args, env = {}) => new Promise((resolve, reject) => {
-  execFile('git', args, { cwd, env: { ...process.env, ...env }, maxBuffer: 64 * 1024 * 1024, timeout: 60000 }, (err, out) => {
+  // A project's own config can name commands git runs (fsmonitor, diff
+  // drivers); none of them should run just because a job ended.
+  execFile('git', ['-c', 'core.fsmonitor=false', ...args], { cwd, env: { ...process.env, ...env }, maxBuffer: 64 * 1024 * 1024, timeout: 60000 }, (err, out) => {
     if (err) reject(err); else resolve(out);
   });
 });
@@ -67,6 +69,6 @@ export async function summarize(cwd, base, end) {
 // The patch for one file, only when the boss asks for it.
 export async function fileDiff(cwd, changes, file) {
   if (!changes?.files.some((f) => f.path === file)) throw new Error('That file is not part of this job’s changes.');
-  const out = await git(cwd, ['diff', '--no-renames', '--no-color', changes.base, changes.end, '--', file]);
+  const out = await git(cwd, ['diff', '--no-renames', '--no-color', '--no-ext-diff', '--no-textconv', changes.base, changes.end, '--', file]);
   return out.length > MAX_DIFF ? `${out.slice(0, MAX_DIFF)}\n… diff cut at ${MAX_DIFF / 1024} KB` : out;
 }

package/server/chief.js

@@ -90,7 +90,8 @@ function ask(context, { bin, model, timeoutMs, env, images }) {
     let out = '', err = '';
     child.stdout.on('data', (d) => (out += d));
     child.stderr.on('data', (d) => (err += d));
-    const timer = setTimeout(() => child.kill('SIGKILL'), timeoutMs);
+    let timedOut = false;
+    const timer = setTimeout(() => { timedOut = true; child.kill('SIGKILL'); }, timeoutMs);
     child.on('error', (e) => { clearTimeout(timer); reject(e); });
     child.on('close', () => {
       clearTimeout(timer);
@@ -99,7 +100,7 @@ function ask(context, { bin, model, timeoutMs, env, images }) {
         const decision = r.structured_output || JSON.parse(r.result);
         resolve({ ...decision, cost: r.total_cost_usd || 0 });
       } catch {
-        reject(new Error(err.trim().split('\n').pop() || 'The chief could not decide.'));
+        reject(new Error(whyNot(out, err, streamed, timedOut, timeoutMs)));
       }
     });
     child.stdin.on('error', () => {});
@@ -119,6 +120,21 @@ function message(context, images) {
 }
 
 // The decision is in the last line of the stream, the one the run ends on.
+// Why a routing call gave no decision, in words the boss can act on. claude
+// reports most failures (not signed in, out of credit, a model the account
+// can't use) inside its JSON on stdout with nothing on stderr, so read that
+// before falling back.
+function whyNot(out, err, streamed, timedOut, timeoutMs) {
+  if (timedOut) return `The chief took longer than ${Math.round(timeoutMs / 1000)} seconds to answer. Check that \`claude -p "hi"\` answers in a terminal.`;
+  let r = null;
+  try { r = streamed ? result(out) : JSON.parse(out); } catch {}
+  const said = String(r?.is_error ? r.result || r.subtype || '' : '').trim();
+  if (said) return `claude said: ${said.split('\n')[0].slice(0, 300)}`;
+  const last = err.trim().split('\n').pop();
+  if (last) return last.slice(0, 300);
+  return out.trim() ? 'The chief could not decide.' : 'claude exited without answering. Check that `claude -p "hi"` answers in a terminal.';
+}
+
 function result(out) {
   for (const line of out.trim().split('\n').reverse()) {
     try {