@maplezzk/pi-interactive-subagents 3.11.0 → 3.11.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maplezzk/pi-interactive-subagents",
-  "version": "3.11.0",
+  "version": "3.11.1",
   "description": "Interactive async subagents for pi — spawn, orchestrate, and manage sub-agent sessions in multiplexer panes. Fork of HazAT/pi-interactive-subagents.",
   "type": "module",
   "main": "./index.ts",

package/pi-extension/subagents/index.ts

@@ -882,19 +882,10 @@ function handleSubagentInterrupt(
   running.statusState = forceStatusAfterInterrupt(running.statusState, now);
   updateWidget();
 
-  // After aborting the current generation, also signal done so the subagent
-  // properly finishes (parent's pollForExit detects the .exit file and
-  // returns the result).
-  if (running.sessionFile) {
-    const exitFile = `${running.sessionFile}.exit`;
-    try {
-      writeFileSync(exitFile, JSON.stringify({ type: "done" }));
-    } catch (writeErr: any) {
-      process.stderr.write(
-        `[interrupt] .exit 写入失败 file=${exitFile} err=${writeErr?.message ?? String(writeErr)}\n`,
-      );
-    }
-  }
+  // Escape only cancels the child's current turn. Do not write the `.exit`
+  // sidecar here: that file is the terminal completion signal consumed by
+  // pollForExit, and writing it would close the pane and remove this running
+  // entry instead of leaving the child alive for another turn.
 
   return {
     content: [{ type: "text" as const, text: `Interrupt requested for subagent "${running.name}".` }],

package/agents/claude-code.md

@@ -1,22 +0,0 @@
----
-name: claude-code
-description: Self-driving Claude Code session for deep investigation, experimentation, and code exploration
-cli: claude
-auto-exit: true
-spawning: false
-deny-tools: claude
----
-
-# Claude Code
-
-You are a self-driving Claude Code session spawned by pi for hands-on investigation and experimentation.
-
-You have full autonomy: bash, file access, git clone, code editing, running tests, building projects — everything a developer can do in a terminal.
-
-## Guidelines
-
-- Focus on the task given to you
-- Be thorough in your investigation
-- Report concrete findings with evidence (file paths, command output, test results)
-- If you get stuck, explain what you tried and what failed
-- Your final message should summarize what you accomplished and what you found