@insitue/claude-plugin 0.6.2 → 0.6.3

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "insitue",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "description": "Drive a Claude Code session from the InSitue browser overlay. Pick an element in your app, claude reads the file and proposes the edit.",
   "mcpServers": {
     "insitue": {

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # @insitue/claude-plugin
 
+## 0.6.3
+
+- **Responsive watch — interject without cancelling.** The `next_pick` long-poll is now 8s (was 25s). While the watch is running you can just type a message: Claude Code queues it and delivers it the moment the poll returns (≤~8s), so you no longer have to cancel the watch to ask a question. The connect instructions now make clear the watch never needs to be cancelled to talk — Claude answers and resumes watching.
+
 ## 0.6.2
 
 - **Echo the request before fixing.** The cloud-issue instructions (connect.md + the `claim_cloud_issue` tool) now require Claude to print the exact request verbatim ("Fixing locally: …") before any analysis or edits, so you always see what it's about to act on.

package/commands/connect.md

@@ -31,13 +31,17 @@ Either path is fine; pick whichever your runtime has.
    any picks the user made before you attached, summarise them
    ("you picked X but haven't sent a description yet — make sure
    to click Send in the InSitue panel"). Otherwise just say
-   "Connected. Pick something in the browser when you're ready."
+   "Connected — pick something in the browser when you're ready.
+   You can also just type to ask me anything anytime; I'll answer
+   and keep watching, no need to cancel."
 2. Enter the loop: call `mcp__insitue__next_pick`. It long-polls
-   (~25s default — short on purpose so the chat stays responsive
-   to other questions the user might type while you wait). When
-   it returns with `status: "timeout"`, **call it again immediately
-   without announcing it** — the timeout is just a heartbeat, not
-   news. When it returns with `status: "ok"`:
+   (~8s — deliberately short. The user can type at ANY time without
+   cancelling: Claude Code queues their message and delivers it the
+   moment this call returns, so a short poll means they wait at most
+   ~8s to reach you and never need to hit Esc). When it returns with
+   `status: "timeout"` **and the user hasn't said anything**, call it
+   again immediately without announcing it — the timeout is just a
+   heartbeat, not news. When it returns with `status: "ok"`:
    - **Always echo the prompt back first.** Before any action,
      diff, or follow-up question, lead with:
 
@@ -73,10 +77,14 @@ Either path is fine; pick whichever your runtime has.
    again. **Do not narrate the loop** — no "still waiting…", no
    "polling again…". The user sees `[insitue] 📥 pick received`
    on stderr the moment their pick lands; that's the
-   confirmation, not your narration. If the user types another
-   question while you're between calls, answer it first (since
-   the chat is responsive), then resume the loop with
-   `next_pick`.
+   confirmation, not your narration. **The user never has to cancel
+   the watch to talk to you.** When a message from the user arrives
+   while you're watching (it queues during the poll and lands the
+   moment `next_pick` returns), STOP looping, answer it fully, and do
+   whatever they ask — then resume the watch by calling `next_pick`
+   again. Their message is the priority; the watch waits for them, not
+   the other way around. Never tell the user to cancel or re-run
+   `/insitue:connect` just to ask a question.
 4. **End the session properly.** When the user says "stop",
    "done", "quit", "thanks", "exit", "disconnect", "stop
    insitue", or anything else that clearly ends the InSitue

package/dist/mcp-server.js

@@ -204,7 +204,7 @@ function readPackageVersion() {
   return "unknown";
 }
 var MAX_BUFFERED_PICKS = 32;
-var NEXT_PICK_DEFAULT_TIMEOUT_MS = 25 * 1e3;
+var NEXT_PICK_DEFAULT_TIMEOUT_MS = 8 * 1e3;
 var NEXT_PICK_MAX_TIMEOUT_MS = 30 * 60 * 1e3;
 function findSession(projectDir2) {
   const candidate = join3(projectDir2, ".insitue", "session.json");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@insitue/claude-plugin",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Drive Claude (Code AND Desktop) from the InSitue browser overlay — pick an element in your app, claude reads the file and proposes the edit.",
   "keywords": [
     "insitue",