usebeeline 0.0.110 → 0.0.112

package/README.md

@@ -9,7 +9,7 @@
 <p align="center"><strong>Team messaging for agents and humans.</strong></p>
 <p align="center">One Room for your people and your coding agents. Talk it through, hand off the work, watch it merge.</p>
 
-`usebeeline` connects **a coding agent you already run — Claude Code, Codex, Goose, Pi, or Grok — to a Room in the Beeline app on your phone**. One command on the machine where the agent lives, and it walks into the conversation as a member: it reads what your teammates actually said, answers when it is tagged, and takes work away when someone asks it to. In top-level Rooms and corners, it can also continue the conversation with the person it last addressed, without piling on from another agent. Nothing is retyped into a prompt box.
+`usebeeline` connects **a coding agent you already run — Claude Code, Codex, Goose, Pi, Grok, or Cursor — to a Room in the Beeline app on your phone**. One command on the machine where the agent lives, and it walks into the conversation as a member: it reads what your teammates actually said, answers when it is tagged, and takes work away when someone asks it to. In top-level Rooms and corners, it can also continue the conversation with the person it last addressed, without piling on from another agent. Nothing is retyped into a prompt box.
 
 The agent stays on your machine. Your provider key stays on your machine. What crosses the wire is the conversation, and — when repository work starts — a pull request.
 

package/dist/usebeeline.mjs

@@ -6092,16 +6092,18 @@ var AGENT_KINDS = [
   "goose",
   "pi",
   "grok",
+  "cursor",
   "reference",
   "custom"
 ];
-var AUTO_DETECT_AGENT_KINDS = ["codex", "claude", "goose", "pi", "grok"];
+var AUTO_DETECT_AGENT_KINDS = ["codex", "claude", "goose", "pi", "grok", "cursor"];
 var AGENT_EXECUTABLES = {
   codex: "codex",
   claude: "claude",
   goose: "goose",
   pi: "pi",
-  grok: "grok"
+  grok: "grok",
+  cursor: "cursor-agent"
 };
 var ADAPTER_INSTALL_COMMANDS = {
   codex: {
@@ -6115,6 +6117,10 @@ var ADAPTER_INSTALL_COMMANDS = {
   pi: {
     command: "npm",
     args: ["install", "-g", "pi-acp"]
+  },
+  cursor: {
+    command: "npm",
+    args: ["install", "-g", "cursor-agent-acp"]
   }
 };
 function adapterInstallHint(kind) {
@@ -6295,6 +6301,11 @@ function resolveAgentCommand(opts) {
     const command2 = requireExecutable("pi-acp", env, cwd, `Pi needs an ACP adapter. Install it with \`${adapterInstallHint("pi")}\`, then retry with \`--agent pi\`.`);
     return { kind: typedKind, command: command2, args: [] };
   }
+  if (typedKind === "cursor") {
+    requireExecutable("cursor-agent", env, cwd, "Cursor Agent CLI not found. Install it from https://cursor.com/docs/cli, then retry with `--agent cursor`.");
+    const command2 = requireExecutable("cursor-agent-acp", env, cwd, `Cursor ACP adapter not found. Install it with \`${adapterInstallHint("cursor")}\`, then retry with \`--agent cursor\`.`);
+    return { kind: typedKind, command: command2, args: [] };
+  }
   if (typedKind === "grok") {
     const command2 = requireExecutable("grok", env, cwd, "Grok CLI not found. Install it with `curl -fsSL https://x.ai/cli/install.sh | bash`, then retry with `--agent grok`.");
     return { kind: typedKind, command: command2, args: ["agent", "stdio"] };
@@ -6762,6 +6773,13 @@ var PROFILES = [
       enforcement: "allowlisted",
       note: "buzz-agent mounts only the MCP servers the daemon passes; it has no operator-global tool config"
     }
+  },
+  {
+    match: /(^|[/\\])cursor-agent-acp(\.[a-z]+)?$/i,
+    profile: {
+      enforcement: "config-isolated",
+      note: "cursor-agent-acp bridges cursor-agent to ACP; cursor-agent loads MCP servers from ~/.cursor/mcp.json, so an isolated CURSOR_HOME scopes the session"
+    }
   }
 ];
 function sessionToolScopeMeta(agentCommand) {
@@ -18026,6 +18044,7 @@ var DaemonApiClient = class {
   liveReconnectDelayMs = 1e3;
   liveRooms = /* @__PURE__ */ new Map();
   roomsChangedListener;
+  configChangedListener;
   constructor(baseUrl, daemonToken, agentId, fetchImpl = fetch, webSocketFactory = (url, protocols) => new wrapper_default(url, protocols)) {
     this.baseUrl = baseUrl;
     this.daemonToken = daemonToken;
@@ -18078,6 +18097,12 @@ var DaemonApiClient = class {
   setRoomsChangedListener(listener) {
     this.roomsChangedListener = listener;
   }
+  /** Register the one listener invoked when the server reports the agent's
+   * model/effort selection changed — the wake that hot-restarts every
+   * retained session (agent-wide; the event names no single Room). */
+  setConfigChangedListener(listener) {
+    this.configChangedListener = listener;
+  }
   updateLiveCursor(roomId, cursor3) {
     const room = this.liveRooms.get(roomId);
     if (room && cursor3)
@@ -18127,6 +18152,10 @@ var DaemonApiClient = class {
         this.roomsChangedListener?.();
         return;
       }
+      if (event.type === "config-changed") {
+        this.configChangedListener?.();
+        return;
+      }
       if (event.type === "subscribed" && typeof event.roomId === "string") {
         const capabilities = event.capabilities;
         this.liveRooms.get(event.roomId)?.onState?.(true, {
@@ -18510,6 +18539,10 @@ var HARNESS_HOME_STATE_DIRS = [
   {
     match: /(^|[/\\])grok(\.[a-z]+)?$/i,
     dirs: [".grok"]
+  },
+  {
+    match: /(^|[/\\])cursor-agent-acp(\.[a-z]+)?$/i,
+    dirs: [".cursor"]
   }
 ];
 function harnessHomeStateDirs(agentCommand, home = homedir3()) {
@@ -19381,6 +19414,7 @@ function isAgentPairingCode(value) {
 
 // apps/body/dist/beeline-skill.js
 var USING_BEELINE_SKILL_NAME = "using-beeline";
+var BEELINE_TRIAGE_SKILL_NAME = "beeline-triage";
 var BEELINE_REVIEW_SKILL_NAME = "beeline-review";
 function isConfiguredReviewer(agentHandle, reviewerHandle) {
   return Boolean(agentHandle && reviewerHandle && agentHandle.replace(/^@/, "") === reviewerHandle.replace(/^@/, ""));
@@ -19397,6 +19431,7 @@ var BEELINE_ROOM_CAPABILITIES = [
   `To react to things that HAPPEN in this Room rather than only to what is said to you, call beeline-agent subscribe_events with the kinds you want (${SERVER_EVENT_KINDS.join(", ")}); each one then wakes you for a turn. Subscriptions are per Room and cover every way the event lands: joining a Room you subscribed to wakes you, and so does a person arriving in the Workspace when that arrival projects into this Room - subscribe to joined in an onboarding Room and every newcomer wakes you, exactly like a greeter. It replaces your list, so send every kind you want - list_event_subscriptions shows the current one. You do this yourself: nobody has to configure it for you. grant-decided carries the grant id and status and resumes the turn that asked for the grant.`,
   "To state something that happened so the Room and other agents can act on it, call beeline-agent emit_event with your own agent:<slug> kind, one sentence, and optionally the agent members to wake. Chains of events are bounded and a refused emit posts nothing.",
   "When repository work is needed, you MUST call beeline-agent open_corner with a name of at most three words - it titles the corner everywhere - and a complete objective of no more than 24 words. The host-governed call is the only way to start write work.",
+  "Before emitting `Proposed corner:` or calling open_corner, consult the release-versioned beeline-triage skill and follow it. An unclear request requires a question; a warranted-work or desirability warning does not block the proposal or corner.",
   "Never open a corner from your own reading of a person's ask. For every ask, first reply on one line `Proposed corner: <name> \u2014 <objective>`, using the exact title and objective you would pass to open_corner, then stop and wait. If one message contains several asks, list one numbered `Proposed corner:` line per ask; `go on 1 and 3` opens exactly those objectives and leaves the others proposed. A person's `go`, `yes`, or equivalent opens exactly the proposed corner; if they edit it, their edited text is the objective. Skip this ceremony only when the message itself explicitly commands a corner and states its scope, such as `open a corner and do X` or `go build X in a corner`; open that scope immediately.",
   "Agreement is not action: never merely acknowledge an ask. Reply with a proposed corner, a question, or a line beginning `parked:` with the reason.",
   "When open_corner succeeds, the server posts the corner card: do not announce or restate the opening. End the turn with nothing more unless the person asked something else.",
@@ -19488,6 +19523,11 @@ Follow these steps in order. Do not skip or reorder them.
 
 ## 2. P0 - OBJECTIVE FULFILLED, DEMONSTRATED
 
+Before judging the implementation, independently repeat the two judgment legs from request triage:
+
+- **Work warranted:** For a bug, reproduce the reported behavior on the target branch. For another request, establish the unmet user need from the request and current product. Search current code, history, issues, and open or recently merged pull requests for work that already resolves or supersedes it. Treat title similarity only as a candidate, not proof of duplication. FAIL confirmed duplicate or obsolete work.
+- **Desirable:** Check repository-owned goals, invariants, architecture, and established product behavior. Require a concrete user benefit, the smallest coherent solution, and no unapproved scope. FAIL a confirmed conflict or an unsupported product judgment; put merely plausible concerns below as non-blocking findings.
+
 - Quote the corner objective verbatim.
 - Derive its end-user story in one sentence: \`a user who does X sees Y\`.
 - Make Y happen against the built PR head: run the app or affected service and perform X.
@@ -19531,6 +19571,8 @@ Follow these steps in order. Do not skip or reorder them.
 
 \`objective quoted:\`
 \`user story:\`
+\`work warranted evidence:\`
+\`desirability evidence:\`
 \`how Y was demonstrated (or FAIL):\`
 \`commands run + results:\`
 \`critical findings (block):\`
@@ -19545,6 +19587,49 @@ Then take exactly one action:
 - Approving is your last step as reviewer. The author merges it; you never do, and nothing merges it automatically.
 `;
 }
+function beelineTriageSkillMarkdown(releaseId) {
+  return `---
+name: beeline-triage
+description: Clarify and assess a user request before proposing or opening a Beeline corner. Use immediately before emitting Proposed corner or calling open_corner.
+---
+
+<!-- beeline-release: ${releaseId} -->
+
+# Beeline request triage
+
+Run these checks before proposing or opening a corner.
+
+## 1. Is it clear?
+
+- Rewrite the request as a concrete outcome and acceptance criteria.
+- State material exclusions needed to prevent unrequested work.
+- Keep the corner objective complete and within 24 words.
+- If an ambiguity could materially change the outcome, ask one focused question instead of proposing or opening the corner.
+
+## 2. Is work warranted?
+
+- For a bug, try to reproduce the exact user-visible behavior and record the evidence.
+- For another request, identify the unmet user need and the current behavior that does not meet it.
+- Search current code, history, issues, and open or recently merged pull requests for released or unreleased work that resolves or supersedes the request.
+- Treat similar titles as candidates. Confirm behavior and scope before calling work duplicate.
+- If the need cannot be established, reproduction fails, or other work may obviate it, warn; do not block.
+
+## 3. Is it desirable?
+
+- Compare the request with repository-owned goals, invariants, architecture, and established product behavior.
+- Look for concrete user benefit, the smallest coherent solution, and ongoing maintenance cost.
+- Do not invent product strategy. If the evidence is absent or conflicting, warn; do not block.
+
+## Output
+
+When proposing work, emit the ordinary \`Proposed corner: <name> \u2014 <objective>\` line. Add only applicable warnings on following lines:
+
+\`Triage warning \u2014 warranted: <evidence-backed reason>\`
+\`Triage warning \u2014 desirable: <evidence-backed reason>\`
+
+Do not emit a warning merely because evidence is incomplete when the repository offers no practical way to obtain it. Never describe a warning as approval or rejection. Warnings inform the user and implementer; they do not block work.
+`;
+}
 
 // apps/body/dist/external-mcp-capabilities.js
 var SQUIRE_MCP_VERSION = "latest";
@@ -20139,11 +20224,15 @@ var SHARED_CREDENTIALS = [
   // Grok relocates ~/.grok via GROK_HOME; auth.json holds its login (same
   // shape as codex).
   { dir: "grok", source: ".grok/auth.json", target: "auth.json" },
-  { dir: "pi", source: ".pi/agent/auth.json", target: "auth.json" }
+  { dir: "pi", source: ".pi/agent/auth.json", target: "auth.json" },
+  // Cursor CLI stores auth state under ~/.cursor/; cursor-agent-acp
+  // reads CURSOR_HOME to relocate the data directory.
+  { dir: "cursor", source: ".cursor/agent-cli-state.json", target: "agent-cli-state.json" }
 ];
 var GOOSE_SHARED_CONFIG_FILES = ["config.yaml", "secrets.yaml"];
 var BEELINE_DEFAULT_SKILL_NAMES = [
   BEELINE_REVIEW_SKILL_NAME,
+  BEELINE_TRIAGE_SKILL_NAME,
   USING_BEELINE_SKILL_NAME
 ];
 var OPERATOR_SKILL_SOURCE_DIRS = [
@@ -20152,7 +20241,7 @@ var OPERATOR_SKILL_SOURCE_DIRS = [
   ".codex/skills",
   ".pi/agent/skills"
 ];
-var AGENT_SKILL_DIRS = ["claude", "codex", "grok", "pi"];
+var AGENT_SKILL_DIRS = ["claude", "codex", "grok", "pi", "cursor"];
 function agentSkillDir(kind) {
   return AGENT_SKILL_DIRS.includes(kind ?? "") ? kind : "codex";
 }
@@ -20180,6 +20269,7 @@ var HOME_SUBDIRS = [
   "goose",
   "grok",
   "pi",
+  "cursor",
   "state",
   "cache",
   "tmp"
@@ -20225,6 +20315,7 @@ async function prepareRoomAgentHome(input) {
 async function provisionAgentSkillsAndMcp(root, operatorHome, skillReleaseId, failClosed, sharedSkills, skillDir, openRouterRouting, isReviewer) {
   const managedSkills = [
     { name: USING_BEELINE_SKILL_NAME, content: usingBeelineSkillMarkdown(skillReleaseId) },
+    { name: BEELINE_TRIAGE_SKILL_NAME, content: beelineTriageSkillMarkdown(skillReleaseId) },
     ...isReviewer ? [{ name: BEELINE_REVIEW_SKILL_NAME, content: beelineReviewSkillMarkdown(skillReleaseId) }] : []
   ];
   const shared = await resolveSharedSkillSources(operatorHome, sharedSkills);
@@ -20634,6 +20725,7 @@ function roomAgentHomeEnv(root) {
     CODEX_HOME: resolve13(resolved, "codex"),
     GOOSE_PATH_ROOT: resolve13(resolved, "goose"),
     GROK_HOME: resolve13(resolved, "grok"),
+    CURSOR_HOME: resolve13(resolved, "cursor"),
     PI_CODING_AGENT_DIR: resolve13(resolved, "pi"),
     XDG_STATE_HOME: resolve13(resolved, "state"),
     XDG_CACHE_HOME: resolve13(resolved, "cache"),
@@ -20645,6 +20737,7 @@ var HARNESS_STATE_ENV_VARS = [
   "CODEX_HOME",
   "GOOSE_PATH_ROOT",
   "GROK_HOME",
+  "CURSOR_HOME",
   "PI_CODING_AGENT_DIR",
   "XDG_STATE_HOME",
   "XDG_CACHE_HOME",
@@ -24434,6 +24527,23 @@ var SessionScheduler = class {
     this.live.delete(key);
     await this.retire(session);
   }
+  /**
+   * Retire every RETAINED session — the warm processes holding no turn — in
+   * one pass. This is the config-change hot restart: a phone-side model/effort
+   * selection change must not wait for each Room's next hand-back currency
+   * check to notice. A busy, draining, queued, or still-spawning session is
+   * deliberately left alone: interrupting a live turn buys nothing, and its
+   * next hand-back runs the ordinary `isCurrent` check, which cold-activates
+   * against the new selection. Suspending a key that is no longer live is a
+   * no-op, so overlapping wakes coalesce safely.
+   */
+  async suspendIdle() {
+    for (const [key, session] of [...this.live.entries()]) {
+      if (session.pending || this.busy.has(key) || this.drainingKeys.has(key) || (this.queues.get(key)?.length ?? 0) > 0)
+        continue;
+      await this.suspend(key);
+    }
+  }
   /**
    * Tear down a poisoned session even when its task is still marked busy.
    * The watchdog uses this only after a Room has stopped making progress; the
@@ -24867,6 +24977,9 @@ var RoomRuntimeCoordinator = class {
     this.options.daemonApi.setRoomsChangedListener?.(() => {
       this.discoveryWakes.wake();
     });
+    this.options.daemonApi.setConfigChangedListener?.(() => {
+      void this.scheduler.suspendIdle().catch((error) => console.error("[body] config-change session restart failed", error));
+    });
     this.watchdogStaleMs = options.watchdogStaleMs ?? DEFAULT_ROOM_WATCHDOG_STALE_MS;
     this.reconcileHeartbeatMs = options.reconcileHeartbeatMs ?? DEFAULT_RECONCILE_HEARTBEAT_MS;
     this.drainDeadlineMs = options.drainDeadlineMs ?? DEFAULT_DRAIN_DEADLINE_MS;
@@ -25900,6 +26013,7 @@ Install one of these supported agents:
   goose  https://block.github.io/goose/docs/getting-started/installation/
   pi     npm install -g @mariozechner/pi-coding-agent pi-acp
   grok   curl -fsSL https://x.ai/cli/install.sh | bash
+  cursor npm install -g cursor-agent-acp
 Then retry, or explicitly use \`--agent reference\` with an LLM key.
 For another ACP server, use \`--agent custom --agent-command "<cmd> [args...]"\`.`;
 async function clackConfirmInstall(message) {
@@ -26138,7 +26252,8 @@ var DEFAULT_MODELS = {
   xai: "grok-4",
   codex: "gpt-5.4",
   claude: "claude-opus-4-1",
-  grok: "grok-4"
+  grok: "grok-4",
+  cursor: "claude-sonnet-4"
 };
 function connectHarnessNeedsProvider(harness) {
   return CONNECT_PROVIDER_HARNESSES.has(harness);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "usebeeline",
-  "version": "0.0.110",
+  "version": "0.0.112",
   "description": "Connect an AI coding agent to Beeline with one command.",
   "homepage": "https://usebeeline.app",
   "bugs": {