@jkwd/inbase 0.1.11 → 0.1.13

package/bin/session.mjs

@@ -30,15 +30,31 @@ function printAck(kind, detail) {
   console.log(`VISUAL_CODER_ACK ${kind}: ${detail}`)
 }
 
-function createManifestGate(manifestPath) {
+export function createManifestGate(manifestPath, watch = fs.watch) {
   const dir = path.dirname(manifestPath)
   let wake = () => {}
   let watcher = null
+
+  const dropWatcher = () => {
+    try {
+      watcher?.close()
+    } catch {
+      // Already closed after an error, or never opened.
+    }
+    watcher = null
+  }
+
   try {
-    watcher = fs.watch(dir, () => wake())
+    watcher = watch(dir, () => wake())
+    watcher?.on?.('error', () => {
+      // EMFILE and sandbox limits must not crash wait-for-approval. Poll instead.
+      dropWatcher()
+      wake()
+    })
   } catch {
-    watcher = null
+    dropWatcher()
   }
+
   return {
     wait(ms) {
       return new Promise((resolve) => {
@@ -50,7 +66,7 @@ function createManifestGate(manifestPath) {
       })
     },
     close() {
-      watcher?.close()
+      dropWatcher()
     },
   }
 }
@@ -163,7 +179,7 @@ export async function attachSession(args) {
   console.log(`VISUAL_CODER_SESSION ${manifest.sessionId}`)
   printAck('attached', manifest.name || manifest.sessionId)
   console.log(
-    `VISUAL_CODER_ATTACHED Attached to the focused visualizer session ${manifest.name || manifest.sessionId} (${manifest.phase}). Use --session ${manifest.sessionId} for every later command. Run inbase wait-for-blueprint --session ${manifest.sessionId} to read the optional blueprint and instruction; it does not wait.`,
+    `VISUAL_CODER_ATTACHED Attached to the next waiting visualizer session ${manifest.name || manifest.sessionId} (${manifest.phase}). Use --session ${manifest.sessionId} for every later command. Run inbase wait-for-blueprint --session ${manifest.sessionId} to read the optional blueprint and instruction; it does not wait.`,
   )
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jkwd/inbase",
-  "version": "0.1.11",
+  "version": "0.1.13",
   "description": "A first-person 3D map of a codebase, with a visual coding workflow for Cursor.",
   "license": "MIT",
   "author": "Joris Kuijper",

package/skill/commands/inbase.md

@@ -1,12 +1,12 @@
 ---
-description: Attach this chat to the focused Inbase visualizer session
+description: Attach this chat to the next waiting Inbase visualizer session
 ---
 
 The user invoked `/inbase`. This is how a chat joins the visualizer session that **Setup LLM session** already created.
 
 Do **not** ask for a session id. Do **not** run `inbase start-session`. Do **not** print the "direct chat interaction not allowed" message.
 
-1. Attach to the focused visualizer session:
+1. Attach to the next waiting visualizer session (newest first; skip sessions that already have an LLM):
 
 ```bash
 npx inbase attach

package/skill/inbase/SKILL.md

@@ -57,7 +57,8 @@ If this chat is not yet attached, run:
 npx inbase attach
 ```
 
-That attaches this chat to the session currently focused in the map. No id is
+That attaches this chat to the next waiting visualizer session (newest first).
+Already-attached sessions are skipped. Window focus does not matter. No id is
 passed in; read `VISUAL_CODER_SESSION` from the output and use that
 `--session` value for every later command. Then continue from
 `wait-for-blueprint` below. Do **not** run `start-session`. Do **not** wait
@@ -144,11 +145,13 @@ npx inbase report-plan \
 npx inbase wait-for-approval --session "<session-id>"
 ```
 
-   Do not edit project files until this prints `VISUAL_CODER_ACK execute` /
-   `VISUAL_CODER_EXECUTE`. If Step by step is off, this returns immediately for
-   each remaining step. First reply in chat acknowledging the ack, then re-read
-   this session's `blueprint.json`; the user can place files and islands on any
-   step.
+   Describe this tool call as `inbase wait-for-approval`, not "waiting for the
+   user to invoke". The command keeps running until they invoke; when it
+   returns, they already did. Do not edit project files until this prints
+   `VISUAL_CODER_ACK execute` / `VISUAL_CODER_EXECUTE`. If Step by step is off,
+   this returns immediately for each remaining step. First reply in chat
+   acknowledging the ack, then re-read this session's `blueprint.json`; the
+   user can place files and islands on any step.
 9. Implement only the invoked step by editing the live project files (Write,
    StrReplace, Delete). Paths are the same ids as `codebase.json`. Then record
    the step — Inbase diffs the working tree against the snapshot taken at