pi-quiet 0.2.0 → 0.2.1

package/README.md

@@ -25,7 +25,7 @@ The extension re-registers the built-in `bash` tool via pi's own `createBashTool
 
 - **Rendering.** The two render slots above. Execution *is* the built-in tool: the model receives the full output, permission systems, reviewers, and sandboxes that hook execution are unaffected, and session logs store the full result.
 - **pi's shell settings.** The built-in is constructed with `shellCommandPrefix` and `shellPath` — read with the same settings pi itself would use, including pi's own project-trust decision for the current directory (`session_start` is where that decision becomes available, so that is where the tool is registered). A trusted project's `.pi/settings.json` contributes its `shellCommandPrefix` and `shellPath`; an untrusted project's are ignored, exactly as pi ignores them. Re-registration on each `session_start` means a `/reload` after editing settings picks up the new prefix.
-- **Session identity.** Every command's environment carries `AGENT_SESSION_ID`, set from pi's per-command `PI_SESSION_ID`. Tools that scope themselves to the session that ran them (muster, galley, tackle) read that neutral name. It is set per command from pi's live session, never from the extension's process environment, so an in-process subagent can never leave the parent's commands carrying a child's id.
+- **Session identity.** Every command's environment carries `AGENT_SESSION_ID`, set from pi's per-command `PI_SESSION_ID`. Tools that scope themselves to the session that ran them (muster, galley, tackle) read that neutral name. It is set per command from pi's live session, never from the extension's process environment, so an in-process subagent can never leave the parent's commands carrying a child's id. An inherited `AGENT_SESSION_CHILD` is removed: that marker belongs only to processes that run as part of the session (pi-claude-bridge's Claude children), so a Claude session started from a command keeps its own id.
 
 ## Install
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-quiet",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "This rig's bash tool for the pi coding agent: calm one-line rendering (ctrl+o expands), pi's shell settings honoured, AGENT_SESSION_ID stamped per command from PI_SESSION_ID. Execution is still pi's built-in.",
   "type": "module",
   "license": "MIT",

package/src/bash-options.ts

@@ -1,6 +1,7 @@
 import type { BashSpawnContext, BashToolOptions } from "@earendil-works/pi-coding-agent";
 
 export const SESSION_ID_VAR = "AGENT_SESSION_ID";
+export const SESSION_CHILD_VAR = "AGENT_SESSION_CHILD";
 
 // The two pi settings the built-in bash tool is constructed with. pi's own
 // SettingsManager satisfies this; tests pass a literal.
@@ -17,8 +18,17 @@ export type ShellSettings = {
 // When pi did not expose a session (exposeSessionEnvironment: false), an
 // inherited value is removed rather than passed through — a command never
 // carries an identity that is not its session's.
+//
+// AGENT_SESSION_CHILD is always removed. It tells tools-common's harness rule
+// that AGENT_SESSION_ID beats CLAUDE_CODE_SESSION_ID because the process runs
+// as part of that session (pi-claude-bridge sets it on its Claude children).
+// pi never sets it, so any value here was inherited from whatever started pi;
+// passed through, it would make a Claude session launched from a command
+// resolve to pi's id instead of its own. pi's own commands resolve through
+// AGENT_SESSION_ID alone, marker or not.
 export function identitySpawnHook(context: BashSpawnContext): BashSpawnContext {
   const env: NodeJS.ProcessEnv = { ...context.env };
+  delete env[SESSION_CHILD_VAR];
   const id = env.PI_SESSION_ID;
   if (id === undefined || id === "") delete env[SESSION_ID_VAR];
   else env[SESSION_ID_VAR] = id;