pitroom 0.18.0 → 0.19.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "pitroom",
   "description": "A free pit crew for your expensive coding agent: the superpowers development workflow, run by cheap workers. Delegate research, fixes, tests, reviews and whole plans from Claude Code, Codex or any agent to OpenCode, Codex or Claude Code workers, with receipts that prove the savings.",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "author": {
     "name": "TahaAtas"
   },

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "pitroom",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "description": "A free pit crew for your expensive coding agent: delegate research, fixes, tests, reviews and parallel investigations to cheap worker agents running your own models, with verified answers, exact diffs and cost receipts.",
   "author": {
     "name": "TahaAtas"

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## 0.19.0
+
+### Doctor
+- `pitroom doctor` has a **Use** section: with no runs yet it says so and how to start ("ask your agent to use Pitroom", or `pitroom run "where is <something> defined?"`); afterwards it says how many runs there have been and when the last one was. Skills can be installed and an agent may still never think of Pitroom: this is the first thing a new user sees.
+
+### Fixes
+- **`pitroom dash --detach` could not find a dash that was up.** The registry entry (`dash.json`) was deleted whenever the dash did not answer within 1.5 s, or when the file was read while the server was writing it; the command then reported "did not start" with the server running (seen as a flake on Windows and once on macOS). The entry is now removed only when its process is gone, and is written through a temp file.
+
+### Docs
+- Cursor has its own entry in the Quick start (`pitroom install --mcp --client cursor`), with what is and is not verified: Cursor's documentation lists `~/.agents/skills` and `~/.claude/skills`, where `pitroom install` links the skills; we have not run it in a Cursor session, and a forum report says its CLI does not load `~/.agents/skills`.
+
 ## 0.18.0
 
 ### Windows

package/README.md

@@ -282,7 +282,16 @@ gemini extensions install https://github.com/ATASTECH/pitroom
 npm i -g pitroom
 ```
 
-**Any agent that speaks MCP (Cursor, Claude Desktop, and the three above too)**
+**Cursor**
+
+```bash
+npm i -g pitroom
+pitroom install --mcp --client cursor
+```
+
+<sub>This adds `pitroom mcp` to `~/.cursor/mcp.json` and leaves the other servers in that file alone; restart Cursor if it does not show up. Cursor gets the ten MCP tools described below. The skills are linked into `~/.agents/skills` and `~/.claude/skills` (`--no-skills` skips that), and [Cursor's documentation](https://cursor.com/docs/skills) lists both as places it loads skills from; we have not run that in a Cursor session, and a Cursor forum report says its CLI (`cursor-agent`) does not load `~/.agents/skills`. `pitroom install --mcp --dry-run` shows what it would change first.</sub>
+
+**Any agent that speaks MCP (Claude Desktop, and the ones above too)**
 
 Pitroom is also an [MCP](https://modelcontextprotocol.io) server on stdio: ten tools instead of shell commands and skills (`pitroom_run`, `pitroom_wait`, `pitroom_show`, `pitroom_info`, `pitroom_review`, `pitroom_audit`, `pitroom_apply`, `pitroom_discard`, `pitroom_revert`, `pitroom_stop`), the runs as resources, and four prompts. The tool definitions sit in the client's context for the whole session, so they are kept small: about 1.9k tokens. It is listed in the [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.ATASTECH/pitroom`, so clients that browse the registry can find it. After `npm i -g pitroom`, let Pitroom register itself in the clients it finds (Claude Code, Codex, Gemini CLI, Cursor, Claude Desktop):
 

package/dist/pitroom.mjs

@@ -3691,7 +3691,7 @@ function progress(meta) {
 }
 
 // src/core/run.ts
-var VERSION2 = true ? "0.18.0" : "0.0.0-dev";
+var VERSION2 = true ? "0.19.0" : "0.0.0-dev";
 function planWork(o) {
   if (!o.plan) return { task: o.task.trim(), tier: o.tier };
   if (o.continueFrom) throw new UserError("a follow-up continues its parent's task; drop --plan/--step");
@@ -5410,13 +5410,17 @@ async function ping(port) {
   }
 }
 async function runningDash() {
+  let r;
   try {
-    const r = JSON.parse(fs27.readFileSync(registryFile(), "utf8"));
-    if (isAlive(r.pid) && await ping(r.port)) return { ...r, url: `http://127.0.0.1:${r.port}/` };
+    r = JSON.parse(fs27.readFileSync(registryFile(), "utf8"));
   } catch {
+    return void 0;
   }
-  fs27.rmSync(registryFile(), { force: true });
-  return void 0;
+  if (!isAlive(r.pid)) {
+    fs27.rmSync(registryFile(), { force: true });
+    return void 0;
+  }
+  return await ping(r.port) ? { ...r, url: `http://127.0.0.1:${r.port}/` } : void 0;
 }
 function openBrowser(url) {
   const [cmd, args] = process.platform === "darwin" ? ["open", [url]] : process.platform === "win32" ? ["cmd", ["/c", "start", "", url]] : ["xdg-open", [url]];
@@ -5468,7 +5472,9 @@ async function dashCommand(o) {
     dash = await startDash({ port: 0, idleMs: o.idleMs });
   }
   fs27.mkdirSync(home(), { recursive: true });
-  fs27.writeFileSync(registryFile(), JSON.stringify({ pid: process.pid, port: dash.port }));
+  const tmp = `${registryFile()}.${process.pid}.tmp`;
+  fs27.writeFileSync(tmp, JSON.stringify({ pid: process.pid, port: dash.port }));
+  renameOver(tmp, registryFile());
   const stop = () => void dash.close();
   process.once("SIGINT", stop);
   process.once("SIGTERM", stop);
@@ -6868,6 +6874,19 @@ var NEXT = [
   { when: /not logged in/, command: "claude auth login", why: "sign in the Claude Code worker (Codex: codex login)" },
   { when: /Gemini CLI is not signed in|IneligibleTierError/, command: "export GEMINI_API_KEY=\u2026", why: "a Google AI Studio key for the Gemini worker" }
 ];
+function usageLine() {
+  const ids = listRunIds();
+  if (!ids.length) {
+    return 'no runs yet. Ask your agent to use Pitroom (for example "have a worker find where X is defined"), or try it yourself: pitroom run "where is <something> defined?"';
+  }
+  let when2 = "";
+  try {
+    const hours = Math.max(0, Math.round((Date.now() - Date.parse(readMeta(ids[ids.length - 1]).startedAt)) / 36e5));
+    when2 = hours < 1 ? ", the last one within the hour" : hours < 48 ? `, the last one ${hours} h ago` : `, the last one ${Math.round(hours / 24)} days ago`;
+  } catch {
+  }
+  return `${ids.length} run${ids.length === 1 ? "" : "s"} so far${when2} (pitroom savings shows what they saved)`;
+}
 function firstNodeOnPath() {
   for (const dir of (process.env.PATH ?? "").split(path30.delimiter).filter(Boolean)) {
     const file2 = path30.join(dir, process.platform === "win32" ? "node.exe" : "node");
@@ -6985,6 +7004,8 @@ function doctor5(probe) {
   for (const m of stale) add("warn", `${m.name} runs a different command for pitroom mcp than this install's: \`pitroom install --mcp --no-skills\` updates it`);
   section2("Skills and agents");
   addAll(skillChecks());
+  section2("Use");
+  add("ok", usageLine());
   if (probe && chain[0]) {
     section2("Live probe");
     const p = liveProbe(chain[0]);

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "pitroom",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "description": "A free pit crew for your expensive coding agent: hand reading, fixes, tests and reviews to cheap worker agents and get back the answer, the exact diff and a receipt. Fourteen skills adapt a full development workflow. Needs the pitroom command (npm i -g pitroom).",
   "contextFileName": "gemini-context.md"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pitroom",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "mcpName": "io.github.ATASTECH/pitroom",
   "description": "A free pit crew for your expensive coding agent: the superpowers development workflow, run by cheap workers. Delegate research, fixes, tests, reviews and whole plans from Claude Code, Codex or any agent to OpenCode, Codex, Claude Code or Gemini CLI workers, with receipts that prove the savings.",
   "type": "module",