@selesai/code 0.9.11 → 0.9.13

package/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 All notable changes to `@selesai/code` will be documented in this file.
 
+## [0.9.13] - 2026-08-26
+
+### Changed
+- **Selesai documentation refresh.** Reworked the documentation homepage with sharper hero typography, concise installation and capability copy, and reduced-motion-safe capability reveals.
+- **Default implementation agents.** The built-in `architect` and `builder` roles now default to `tokenin/celestial-max:max` instead of `tokenin/celestial-pro:max`.
+
+## [0.9.12] - 2026-08-25
+
+### Added
+- **Configurable built-in tools.** Use `defaultTools` to select the built-in tools enabled by default, or SDK `tools` and `excludeTools` to allowlist and remove individual tools; `powershell`, `grep`, `find`, and `ls` now participate in this unified tool configuration.
+- **Upgraded collaboration extensions.** Bundled pi-subagents 0.56.0 adds fast OpenAI-Codex child runs, extension bindings, model selection controls, external-job follow-ups, child-scoped stops, durable workflow receipts, and improved workflow safeguards. Bundled pi-intercom 0.12.0 adds consent-aware extension outbox sends, scoped session routing, safer endpoint-bound delivery/retries, pending-ask records, and optional after-first-use tool visibility.
+- **Design and output skills.** Added bundled skills for higher-quality frontend, brand, image-to-code, and image-generation workflows, plus complete-output enforcement and web-design reviews.
+- **Unlazy skill.** Added the bundled `unlazy` skill for completion discipline — acceptance gates, depth-tree decomposition, reverified checks, and evidence-backed reporting via scripts/templates/tests shipped under `src/skills/unlazy`.
+
+### Changed
+- **Pi 0.84.3 runtime update.** Updated the embedded Pi runtime and selected agent-session behavior.
+
 ## [0.9.11] - 2026-08-25
 
 ### Fixed

package/dist/config.d.ts

@@ -156,12 +156,10 @@ export declare function seedMissingSubagentSettings(destPath: string, bundledDef
 export declare function seedDefaultExtensions(agentDir: string, bundledExtensionsDir?: string): string[];
 /**
  * Seed bundled built-in skills into the user's agent dir/skills.
- * Ownership rule: bundled files are installed only when missing, so a new
- * release can supply new bundled skills, but existing user files are never
- * overwritten — user-authored edits survive. User-only skills stay. The
- * authoritative bundled copy still loads directly from the package at boot
- * (additionalSkillPaths), so a stale user copy never loses functionality.
- * Returns the list of destination paths that were written.
+ * The bundled copy is authoritative: existing user copies are overwritten so a
+ * stale installed copy never shadows the shipped skill. User-only skills (not
+ * present in the bundled tree) are left untouched. Returns the list of
+ * destination paths that were written.
  */
 export declare function seedDefaultSkills(agentDir: string, bundledSkillsDir?: string): string[];
 /**

package/dist/config.js

@@ -676,10 +676,11 @@ export function seedMissingSubagentSettings(destPath, bundledDefaultsDir = getBu
     }
 }
 /**
- * Recursively copy a bundled directory tree into the user's agent dir, skipping
- * any file that already exists (user edits survive). Never overwrites. Used to
- * seed bundled skills/themes so the user can inspect and edit them.
- * Returns the list of destination paths that were written.
+ * Recursively copy a bundled directory tree into the user's agent dir,
+ * overwriting any existing file so the bundled copy stays authoritative.
+ * Used to seed/sync bundled skills and themes. User-only files (not present in
+ * the bundled tree) are left untouched. Returns the list of destination paths
+ * that were written.
  */
 function seedBundledDir(destDir, bundledDir) {
     if (!existsSync(bundledDir))
@@ -696,13 +697,10 @@ function seedBundledDir(destDir, bundledDir) {
             const srcPath = join(src, entry.name);
             const dstPath = join(dst, entry.name);
             if (entry.isDirectory()) {
-                if (!existsSync(dstPath))
-                    mkdirSync(dstPath, { recursive: true, mode: 0o700 });
+                mkdirSync(dstPath, { recursive: true, mode: 0o700 });
                 stack.push({ src: srcPath, dst: dstPath });
             }
             else if (entry.isFile() || entry.isSymbolicLink()) {
-                if (existsSync(dstPath))
-                    continue;
                 copyFileSync(srcPath, dstPath);
                 try {
                     chmodSync(dstPath, 0o600);
@@ -754,12 +752,10 @@ export function seedDefaultExtensions(agentDir, bundledExtensionsDir = getBundle
 }
 /**
  * Seed bundled built-in skills into the user's agent dir/skills.
- * Ownership rule: bundled files are installed only when missing, so a new
- * release can supply new bundled skills, but existing user files are never
- * overwritten — user-authored edits survive. User-only skills stay. The
- * authoritative bundled copy still loads directly from the package at boot
- * (additionalSkillPaths), so a stale user copy never loses functionality.
- * Returns the list of destination paths that were written.
+ * The bundled copy is authoritative: existing user copies are overwritten so a
+ * stale installed copy never shadows the shipped skill. User-only skills (not
+ * present in the bundled tree) are left untouched. Returns the list of
+ * destination paths that were written.
  */
 export function seedDefaultSkills(agentDir, bundledSkillsDir = getBundledSkillsDir()) {
     return seedBundledDir(join(agentDir, "skills"), bundledSkillsDir);

package/dist/core/agent-session.d.ts

@@ -558,7 +558,6 @@ export declare class AgentSession {
     private _applyExtensionBindings;
     private _refreshCurrentModelFromRegistry;
     private _bindExtensionCore;
-    private _createToolCatalogDefinition;
     private _refreshToolRegistry;
     private _buildRuntime;
     reload(options?: {

package/dist/core/agent-session.js

@@ -14,7 +14,6 @@
  */
 import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
 import { basename, dirname } from "node:path";
-import { Type } from "typebox";
 import { contentText } from "@earendil-works/pi-ai";
 import { clampThinkingLevel, cleanupSessionResources, getSupportedThinkingLevels, isContextOverflow, isRetryableAssistantError, modelsAreEqual, resetApiProviders, streamSimple, } from "@earendil-works/pi-ai/compat";
 import { getThemeByName, theme } from "../modes/interactive/theme/theme.js";
@@ -36,7 +35,7 @@ import { CURRENT_SESSION_VERSION, getLatestCompactionEntry } from "./session-man
 import { createSyntheticSourceInfo } from "./source-info.js";
 import { buildSystemPrompt } from "./system-prompt.js";
 import { createLocalBashOperations } from "./tools/bash.js";
-import { createAllToolDefinitions, stripToolParameterDescriptions } from "./tools/index.js";
+import { createAllToolDefinitions } from "./tools/index.js";
 import { createToolDefinitionFromAgentTool } from "./tools/tool-definition-wrapper.js";
 import { addUsageToTotals, createUsageTotals } from "./usage-totals.js";
 import { captionImageWithModel } from "./vision-caption.js";
@@ -167,6 +166,7 @@ export class AgentSession {
         this._installAgentNextTurnRefresh();
         this._buildRuntime({
             activeToolNames: this._initialActiveToolNames,
+            includeAllExtensionTools: true,
         });
     }
     get modelRuntime() {
@@ -2215,39 +2215,6 @@ export class AgentSession {
             },
         });
     }
-    _createToolCatalogDefinition() {
-        return {
-            name: "tool_catalog",
-            label: "Tool catalog",
-            description: "Discover inactive tools by capability or activate named tools. Activated tools are available on the next turn.",
-            parameters: Type.Object({
-                query: Type.Optional(Type.String({ description: "Capability or tool name to search for" })),
-                activate: Type.Optional(Type.Array(Type.String({ minLength: 1 }), { description: "Exact inactive tool names to activate" })),
-            }),
-            execute: async (_toolCallId, params) => {
-                const query = params.query?.trim().toLowerCase();
-                const active = new Set(this.getActiveToolNames());
-                const requested = Array.isArray(params.activate)
-                    ? Array.from(new Set(params.activate.filter((name) => typeof name === "string")))
-                    : [];
-                const available = Array.from(this._toolDefinitions.values()).filter(({ definition }) => definition.name !== "tool_catalog");
-                const known = new Set(available.map(({ definition }) => definition.name));
-                const unknown = requested.filter((name) => !known.has(name));
-                const activate = requested.filter((name) => known.has(name));
-                if (activate.length > 0)
-                    this.setActiveToolsByName([...active, ...activate]);
-                const matches = available
-                    .filter(({ definition }) => !query || `${definition.name} ${definition.description}`.toLowerCase().includes(query))
-                    .map(({ definition }) => `- ${definition.name}: ${definition.description}`);
-                const result = [
-                    activate.length > 0 ? `Activated: ${activate.join(", ")}. They are available on the next turn.` : undefined,
-                    unknown.length > 0 ? `Unknown or unavailable: ${unknown.join(", ")}.` : undefined,
-                    matches.length > 0 ? `Available tools:\n${matches.join("\n")}` : query ? "No matching tools." : "No additional tools available.",
-                ].filter(Boolean).join("\n\n");
-                return { content: [{ type: "text", text: result }], details: { activated: activate, unknown } };
-            },
-        };
-    }
     _refreshToolRegistry(options) {
         const previousRegistryNames = new Set(this._toolRegistry.keys());
         const previousActiveToolNames = this.getActiveToolNames();
@@ -2303,18 +2270,6 @@ export class AgentSession {
             toolRegistry.set(tool.name, tool);
         }
         this._toolRegistry = toolRegistry;
-        if (this.settingsManager.getPruneToolDescriptions()) {
-            const keepDescriptions = new Set();
-            for (const [name, entry] of definitionRegistry) {
-                if (entry.definition.keepParameterDescriptions)
-                    keepDescriptions.add(name);
-            }
-            for (const [name, tool] of toolRegistry) {
-                if (!keepDescriptions.has(name)) {
-                    toolRegistry.set(name, stripToolParameterDescriptions(tool));
-                }
-            }
-        }
         const nextActiveToolNames = (options?.activeToolNames ? [...options.activeToolNames] : [...previousActiveToolNames]).filter((name) => isAllowedTool(name));
         if (allowedToolNames) {
             for (const toolName of this._toolRegistry.keys()) {
@@ -2352,7 +2307,6 @@ export class AgentSession {
                 bash: { commandPrefix: shellCommandPrefix, shellPath },
             });
         this._baseToolDefinitions = new Map(Object.entries(baseToolDefinitions).map(([name, tool]) => [name, tool]));
-        this._baseToolDefinitions.set("tool_catalog", this._createToolCatalogDefinition());
         const extensionsResult = this._resourceLoader.getExtensions();
         if (options.flagValues) {
             for (const [name, value] of options.flagValues) {
@@ -2367,7 +2321,7 @@ export class AgentSession {
         this._applyExtensionBindings(this._extensionRunner);
         const defaultActiveToolNames = this._baseToolsOverride
             ? Object.keys(this._baseToolsOverride)
-            : ["read", "bash", "edit", "write", "tool_catalog"];
+            : ["read", "bash", "edit", "write"];
         const baseActiveToolNames = options.activeToolNames ?? defaultActiveToolNames;
         this._refreshToolRegistry({
             activeToolNames: baseActiveToolNames,

package/dist/core/extensions/types.d.ts

@@ -356,8 +356,6 @@ export interface ToolDefinition<TParams extends TSchema = TSchema, TDetails = un
     promptGuidelines?: string[];
     /** Parameter schema (TypeBox) */
     parameters: TParams;
-    /** When global pruneToolDescriptions is enabled, keep this tool's per-field parameter descriptions on the wire (already pruned by the tool itself). */
-    keepParameterDescriptions?: boolean;
     /** Optional provider-side constrained sampling request for this tool. Set false to explicitly disable it, equivalent to leaving it undefined. */
     constrainedSampling?: false | ConstrainedSamplingConfig;
     /** Controls whether ToolExecutionComponent renders the standard colored shell or the tool renders its own framing. */

package/dist/core/settings-manager.d.ts

@@ -82,7 +82,6 @@ export interface Settings {
     branchSummary?: BranchSummarySettings;
     retry?: RetrySettings;
     hideThinkingBlock?: boolean;
-    pruneToolDescriptions?: boolean;
     showCacheMissNotices?: boolean;
     externalEditor?: string;
     shellPath?: string;
@@ -248,7 +247,6 @@ export declare class SettingsManager {
     };
     getWebSocketConnectTimeoutMs(): number | undefined;
     getHideThinkingBlock(): boolean;
-    getPruneToolDescriptions(): boolean;
     getShowCacheMissNotices(): boolean;
     getExternalEditorCommand(): string;
     setHideThinkingBlock(hide: boolean): void;

package/dist/core/settings-manager.js

@@ -620,9 +620,6 @@ export class SettingsManager {
     getHideThinkingBlock() {
         return this.settings.hideThinkingBlock ?? false;
     }
-    getPruneToolDescriptions() {
-        return this.settings.pruneToolDescriptions ?? true;
-    }
     getShowCacheMissNotices() {
         return this.settings.showCacheMissNotices ?? false;
     }

package/dist/core/tools/index.d.ts

@@ -6,7 +6,6 @@ export { createFindTool, createFindToolDefinition, type FindOperations, type Fin
 export { createGrepTool, createGrepToolDefinition, type GrepOperations, type GrepToolDetails, type GrepToolInput, type GrepToolOptions, } from "./grep.ts";
 export { createLsTool, createLsToolDefinition, type LsOperations, type LsToolDetails, type LsToolInput, type LsToolOptions, } from "./ls.ts";
 export { createReadTool, createReadToolDefinition, type ReadOperations, type ReadToolDetails, type ReadToolInput, type ReadToolOptions, } from "./read.ts";
-export { stripSchemaDescriptions, stripToolParameterDescriptions, } from "./schema-prune.ts";
 export { DEFAULT_MAX_BYTES, DEFAULT_MAX_LINES, formatSize, type TruncationOptions, type TruncationResult, truncateHead, truncateLine, truncateTail, } from "./truncate.ts";
 export { createWriteTool, createWriteToolDefinition, type WriteOperations, type WriteToolInput, type WriteToolOptions, } from "./write.ts";
 import type { AgentTool } from "@earendil-works/pi-agent-core";

package/dist/core/tools/index.js

@@ -6,7 +6,6 @@ export { createFindTool, createFindToolDefinition, } from "./find.js";
 export { createGrepTool, createGrepToolDefinition, } from "./grep.js";
 export { createLsTool, createLsToolDefinition, } from "./ls.js";
 export { createReadTool, createReadToolDefinition, } from "./read.js";
-export { stripSchemaDescriptions, stripToolParameterDescriptions, } from "./schema-prune.js";
 export { DEFAULT_MAX_BYTES, DEFAULT_MAX_LINES, formatSize, truncateHead, truncateLine, truncateTail, } from "./truncate.js";
 export { createWriteTool, createWriteToolDefinition, } from "./write.js";
 import { createBashTool, createBashToolDefinition } from "./bash.js";

package/dist/defaults/settings.json

@@ -27,7 +27,6 @@
     "git:github.com/MasuRii/pi-tool-display",
     "git:github.com/omaclaren/pi-markdown-preview"
   ],
-  "pruneToolDescriptions": true,
   "quietStartup": true,
   "retry": {
     "enabled": true,
@@ -44,10 +43,10 @@
   "subagents": {
     "agentOverrides": {
       "architect": {
-        "model": "tokenin/celestial-pro:max"
+        "model": "tokenin/celestial-max:max"
       },
       "builder": {
-        "model": "tokenin/celestial-pro:max"
+        "model": "tokenin/celestial-max:max"
       },
       "commentator": {
         "model": "tokenin/celestial-pro:max"

package/dist/extensions/model-prompt-injector/index.test.ts

@@ -100,13 +100,3 @@ describe("before_agent_start", () => {
 		expect(result).toBeUndefined();
 	});
 });
-
-describe("model_select", () => {
-	it("shows status when the selected model matches, clears otherwise", async () => {
-		const { handlers, ctx } = harness({ rules: [{ match: ["deepseek/*"], prompt: "EXTRA" }] }, undefined);
-		await handlers["model_select"]({ model: model("deepseek", "deepseek-chat") }, ctx);
-		expect(ctx.ui.setStatus).toHaveBeenLastCalledWith("model-prompt-injector", "prompt-inject: active");
-		await handlers["model_select"]({ model: model("openai", "gpt-5") }, ctx);
-		expect(ctx.ui.setStatus).toHaveBeenLastCalledWith("model-prompt-injector", undefined);
-	});
-});

package/dist/extensions/model-prompt-injector/index.ts

@@ -145,7 +145,4 @@ export default function modelPromptInjector(pi: ExtensionAPI, config: InjectConf
 		return { systemPrompt: `${event.systemPrompt}\n\n${rule.prompt}` };
 	});
 
-	pi.on("model_select", async (event, ctx) => {
-		ctx.ui.setStatus("model-prompt-injector", ruleFor(event.model) ? "prompt-inject: active" : undefined);
-	});
 }

package/dist/extensions/pi-intercom/CHANGELOG.md

@@ -2,6 +2,44 @@
 
 All notable changes to the `pi-intercom` extension will be documented in this file.
 
+## [Unreleased]
+
+## [0.12.0] - 2026-08-22
+
+### Highlights
+- Extensions can now ask pi-intercom to send a message through the current session without losing user consent, sender attribution, or delivery feedback.
+- Teams can isolate intercom traffic with `PI_INTERCOM_SCOPE_ID`, so unrelated sessions do not see or receive each other's scoped messages.
+- The generic `intercom` tool can stay hidden until it is first useful, keeping quiet sessions less cluttered.
+
+### Added
+- Added a consent-aware extension outbox API with `intercom:outbox-request` and `intercom:outbox-result` events for notify-only same-process extension sends. Outbox sends honor `confirmSend`, always return a terminal result for valid request IDs, use scoped target resolution, and leave attributed sender-side transcript traces. Thanks to [@elecnix](https://github.com/elecnix) for #110.
+- Added opt-in broker-enforced routing scopes through `PI_INTERCOM_SCOPE_ID`. Scoped sessions only see, route, recover mailbox messages, receive presence events, and use extension-bus owner, publish, and state traffic with sessions in the exact same opaque scope. Unscoped sessions keep existing behavior. Thanks to [@YeungKC](https://github.com/YeungKC) for issue #112.
+- Added opt-in `after-first-use` visibility for the generic `intercom` tool, keeping its model schema and prompt out of unused sessions until an inbound message, overlay send, or bundled skill load reveals it. Broker reception and the child-only `contact_supervisor` tool remain available while it is hidden. Thanks to [@XWIlluDelu](https://github.com/XWIlluDelu) for PR #111.
+
+## [0.11.0] - 2026-08-19
+
+### Highlights
+- Messages can no longer land on a stale peer: if the target session restarted or was replaced, the send fails clearly or retries against the live session instead of silently reaching the wrong endpoint.
+- Retrying a send with the same message ID is now safe. Identical retries never deliver twice, and reusing an ID with different content is rejected.
+- Send results now include structured delivery details (state, error code, whether a retry is safe), so failures are actionable instead of guesswork.
+- The session list now shows each peer's tmux pane ID, making it easier to find and drive the right terminal.
+- Delivered blocking asks leave a local pending-ask record, so you can see what a peer is still waiting on.
+
+### Added
+- Endpoint-bound direct delivery: sends target the exact live session and safely retry once when the target reconnects mid-send, with bounded replay protection for repeated message IDs. Thanks to [@xiangbianpangde](https://github.com/xiangbianpangde) for #106.
+- Local pending-ask records for delivered blocking asks. Thanks to [@bcanvural](https://github.com/bcanvural) for issue #104.
+- tmux pane IDs in the session roster. Thanks to [@odfalik](https://github.com/odfalik) for issue #102 and PR #101.
+
+### Changed
+- Reusing a message ID with different content now fails with a clear error instead of relying on receiver-side duplicate suppression.
+- Clarified that agents should re-list stale intercom session IDs and skip self-targets.
+
+## [0.10.1] - 2026-08-12
+
+### Fixed
+- Resolve the default broker `tsx` launcher from flat plugin-store installs when package resolution fails, and include broker stderr when startup exits early. Thanks to Eduardo Marquez (`DocksDocks`) for issue #97.
+- Preserve attachments when replying through `intercom({ action: "reply" })`. Thanks to Ruoshan Huang (`ruoshan`) for issue #99.
+
 ## [0.10.0] - 2026-08-09
 
 ### Added
@@ -11,7 +49,6 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 - Cleaned intercom tool copy, visible-peer skill guidance, and broker protocol validation structure.
 
 ### Fixed
-- Resolve the default broker `tsx` launcher from flat plugin-store installs when package resolution fails, and include broker stderr when startup exits early. Thanks to Eduardo Marquez (`DocksDocks`) for issue #97.
 - Surface malformed intercom config errors with path context instead of silently falling back to defaults.
 - Fail blocking `ask` and supervisor-decision requests immediately when the target is not connected instead of accepting a mailbox delivery that can wait until timeout.
 - Prevent disconnected mailbox routing from delivering a message back to its sender or transferring mail through runtime-only unnamed-session aliases. Thanks to ELA718 for PR #93.
@@ -29,7 +66,7 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 ## [0.9.2] - 2026-08-03
 
 ### Fixed
-- Avoid relaunching standalone Pi executables as the Node runtime when starting the default broker process. Thanks to ZacharyQin for PR #82 and to jeffutter and awaae001 for confirming the impact.
+- Avoid relaunching standalone Selesai executables as the Node runtime when starting the default broker process. Thanks to ZacharyQin for PR #82 and to jeffutter and awaae001 for confirming the impact.
 
 ## [0.9.1] - 2026-07-30
 
@@ -60,11 +97,11 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 ### Changed
 - Documented `PI_INTERCOM_ASK_TIMEOUT_MS` for configurable ask/supervisor timeouts. Thanks to wiansapu for issue #14.
 - Clarified session addressing copy so the short IDs shown by `list` are documented as usable prefixes. Thanks to Grant Hutchins for PR #66.
-- Updated Pi runtime peer metadata and tool schemas for the `@earendil-works` package scope and Pi-bundled `typebox`/`pi-ai` packages.
+- Updated Selesai runtime peer metadata and tool schemas for the `@earendil-works` package scope and Selesai-bundled `typebox`/`pi-ai` packages.
 - Centralized pi-intercom runtime and config paths under `SELESAI_CODING_AGENT_DIR` when set, defaulting to `~/.selesai/agent`.
 - Hardened default broker auto-spawn to launch the resolved bundled `tsx` CLI through the current Node executable instead of resolving `npx` through `PATH`; custom `brokerCommand`/`brokerArgs` remain available as advanced trusted config.
 - Added an `inboundTrigger` policy (`always`, `replies`, or `never`) so users can reduce inbound auto-trigger risk while preserving existing behavior by default.
-- Made inline intercom messages collapse and expand with Pi's `Ctrl+O` custom-message toggle while keeping sender, preview, reply, and attachment cues visible. Thanks to RyanKim17920 for PR #32.
+- Made inline intercom messages collapse and expand with Selesai's `Ctrl+O` custom-message toggle while keeping sender, preview, reply, and attachment cues visible. Thanks to RyanKim17920 for PR #32.
 - Improved inline message theme hierarchy with separate semantic styling for borders, headers, body text, and metadata. Thanks to Sreenath for PR #68.
 
 ### Fixed
@@ -73,9 +110,9 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 - Restricted Unix intercom runtime directory, socket, PID, and spawn-lock permissions.
 - Rechecked single-flight ask state after session target resolution so concurrent regular asks fail safely instead of crashing on an unhandled rejected reply waiter.
 - Refused broker-level mutual asks that would deadlock two sessions, and cleared outstanding ask edges when asks are replied to, cancelled, or disconnected.
-- Stabilized intercom session addressing across reconnects, idle `/name` changes, replaced Pi sessions, supervisor routing, pending replies, and short-ID targeting.
+- Stabilized intercom session addressing across reconnects, idle `/name` changes, replaced Selesai sessions, supervisor routing, pending replies, and short-ID targeting.
 - Aligned intercom overlay widths with their rendered modal boxes. Thanks to Cat for PR #43.
-- Marked failed `intercom` and `contact_supervisor` tool results through Pi's `tool_result` error flag path while preserving structured renderer details.
+- Marked failed `intercom` and `contact_supervisor` tool results through Selesai's `tool_result` error flag path while preserving structured renderer details.
 - Limited the intercom overlay to TUI mode and unsubscribed subagent relay event handlers during session shutdown.
 - Added an opt-in Windows localhost TCP transport using a dynamic port, broker protocol health checks, and a local endpoint secret instead of a fixed-port default.
 - Stabilized reply/supervisor routing by respecting explicit reply targets, suppressing legacy supervisor tools when native supervisor channels are present, and clearing replied idle-queued asks. Thanks to ThanhNT29Jacky for PR #64.
@@ -130,12 +167,12 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 - Added receiver-side `reply` ergonomics for inbound asks. Agents can now use `intercom({ action: "reply", message })` in the triggered turn or later against a single pending ask, plus `intercom({ action: "pending" })` to inspect unresolved inbound asks.
 
 ### Fixed
-- Migrated extension tool schemas from `@sinclair/typebox` to `typebox` 1.x so packaged installs follow Pi's current extension runtime contract.
+- Migrated extension tool schemas from `@sinclair/typebox` to `typebox` 1.x so packaged installs follow Selesai's current extension runtime contract.
 - Included `reply-tracker.ts` in the published package so installed extensions can load the new reply-tracking helper at runtime.
 - Updated the integration test harness to set `USERPROFILE` alongside `HOME`, keeping temp-home isolation reliable on Windows.
 
 ### Changed
-- Moved TypeBox from `peerDependencies` to a real `dependencies` entry so `pi install` production installs keep the schema package available at runtime.
+- Moved TypeBox from `peerDependencies` to a real `dependencies` entry so `selesai install` production installs keep the schema package available at runtime.
 - Incoming ask reply hints now prefer `intercom({ action: "reply", ... })` instead of exposing raw `to` and `replyTo` identifiers.
 - Updated the bundled `pi-intercom` skill and README examples to prefer `reply`/`pending` over manual reply threading.
 
@@ -143,7 +180,7 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 
 ### Added
 - Bundled `pi-intercom` skill with coordination patterns, error handling, constraints, and optional cmux/tmux peer-session spawning for visible multi-session workflows.
-- `pi.skills` manifest in `package.json` so `pi install` loads the skill automatically.
+- `pi.skills` manifest in `package.json` so `selesai install` loads the skill automatically.
 - AGENTS.md snippet in README recommending a project-level coordination hint for agents.
 - Attachments example to Quick Start section in README.
 
@@ -172,21 +209,21 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 ## [0.1.9] - 2026-04-17
 
 ### Fixed
-- Declared the extension entry in `package.json` via `pi.extensions` so `pi install npm:pi-intercom` can discover and load the extension from the npm package.
+- Declared the extension entry in `package.json` via `pi.extensions` so `selesai install npm:pi-intercom` can discover and load the extension from the npm package.
 
 ### Changed
-- Added `pi-package` package metadata plus peer dependency declarations for every Pi runtime package the extension imports, including `@mariozechner/pi-tui`.
+- Added `pi-package` package metadata plus peer dependency declarations for every Selesai runtime package the extension imports, including `@mariozechner/pi-tui`.
 
 ## [0.1.8] - 2026-04-14
 
 ### Changed
 - Intercom sessions now reconnect automatically after broker disconnects or sleep/wake interruptions instead of staying offline until reload or restart.
-- Replaced raw runtime `console.error` intercom disconnect logging with silent recovery so transient broker churn no longer splashes stray text into the Pi TUI.
+- Replaced raw runtime `console.error` intercom disconnect logging with silent recovery so transient broker churn no longer splashes stray text into the Selesai TUI.
 
 ## [0.1.7] - 2026-04-13
 
 ### Changed
-- Unnamed sessions now register a runtime-only `subagent-chat-<id>` intercom alias instead of persisting a generic session title into Pi session history, so `pi --resume` can keep showing transcript snippets while unnamed sessions remain reachable over intercom.
+- Unnamed sessions now register a runtime-only `subagent-chat-<id>` intercom alias instead of persisting a generic session title into Selesai session history, so `selesai --resume` can keep showing transcript snippets while unnamed sessions remain reachable over intercom.
 - Intercom presence updates now refresh the advertised session name during later turn/intercom activity, so renaming a session does not leave subagents and peers targeting a stale startup alias.
 
 ## [0.1.6] - 2026-04-13
@@ -230,11 +267,11 @@ All notable changes to the `pi-intercom` extension will be documented in this fi
 ## [0.1.1] - 2026-04-04
 
 ### Changed
-- Added a `promptSnippet` for the `intercom` tool so Pi 0.59+ includes it in the default tool prompt section and improves session-to-session coordination discoverability.
+- Added a `promptSnippet` for the `intercom` tool so Selesai 0.59+ includes it in the default tool prompt section and improves session-to-session coordination discoverability.
 
 ### Changed
-- **Pi compatibility refresh** — Updated the extension to match current Pi lifecycle and custom UI APIs, including `session_start` / `session_shutdown` and injected `ctx.ui.custom()` keybindings.
-- **Overlay keybindings** — The session picker and compose overlay now use injected, namespaced Pi keybindings instead of reading editor-global bindings directly.
+- **Selesai compatibility refresh** — Updated the extension to match current Selesai lifecycle and custom UI APIs, including `session_start` / `session_shutdown` and injected `ctx.ui.custom()` keybindings.
+- **Overlay keybindings** — The session picker and compose overlay now use injected, namespaced Selesai keybindings instead of reading editor-global bindings directly.
 - **Session list correlation** — `list` / `sessions` now carry a `requestId`, so a delayed broker reply cannot be mistaken for a newer session-list request.
 - **Reply sends skip approval** — `send` calls that include `replyTo` now bypass the confirmation dialog so reply-hint flows work without an extra approval step.
 - **Documentation accuracy** — The README now matches the current implementation, including request correlation, persistence behavior, broker disconnect behavior, and the file layout.

package/dist/extensions/pi-intercom/README.md

@@ -12,7 +12,7 @@ User flow: press Alt+M or run /intercom to pick a session and send a message
 
 ## Why
 
-Sometimes you're running multiple Selesai sessions — one researching, one executing, one reviewing. pi-intercom lets you:
+Sometimes you're running multiple Selesai sessions — one researching, one executing, one reviewing. Selesai-intercom lets you:
 
 - **User-driven orchestration** — Send context or findings from your research session to your execution session
 - **Agent collaboration** — An agent can reach out to another session when it needs help or wants to share results
@@ -20,7 +20,7 @@ Sometimes you're running multiple Selesai sessions — one researching, one exec
 
 Unlike pi-messenger (a shared chat room for multi-agent swarms), pi-intercom is for targeted 1:1 communication where you pick the recipient.
 
-pi-intercom also integrates well with [pi-subagents](https://github.com/nicobailon/pi-subagents): delegated child agents get a child-only `contact_supervisor` tool when `pi-subagents` supplies bridge metadata. Use `reason: "need_decision"` for blocking clarification, `reason: "interview_request"` for multiple structured supervisor answers, and `reason: "progress_update"` for meaningful plan-changing updates. Normal sessions only see the regular `intercom` tool.
+Selesai Intercom also integrates well with [pi-subagents](https://github.com/nicobailon/pi-subagents): delegated child agents get a child-only `contact_supervisor` tool when `pi-subagents` supplies bridge metadata. Use `reason: "need_decision"` for blocking clarification, `reason: "interview_request"` for multiple structured supervisor answers, and `reason: "progress_update"` for meaningful plan-changing updates. Normal sessions only see the regular `intercom` tool.
 
 ## In One Minute
 
@@ -29,7 +29,7 @@ Each Selesai session that has `pi-intercom` loaded and enabled connects to a tin
 ## Install
 
 ```bash
-selesai install npm:pi-intercom
+pi install npm:pi-intercom
 ```
 
 Then restart Selesai. The extension auto-connects to the broker on startup and registers the bundled `pi-intercom` skill for common coordination patterns.
@@ -226,7 +226,7 @@ This matters because the agent receiving the message doesn't need to reconstruct
 
 The broker keeps a bounded in-memory mailbox for recently disconnected explicitly named sessions. If a lightweight CLI sender asks a long-running session something and exits before the answer, the later `reply` is accepted into that mailbox instead of failing with `Session not found`; a process that reconnects with the same explicit name and directory receives the queued reply. Runtime-only unnamed-session aliases never transfer mailbox ownership, and routing never remaps mail back to its sender. This is per-broker runtime state, not durable storage across broker restarts.
 
-Incoming messages carry diagnostic metadata end to end: stable message ID, sender sequence, sender timestamp, broker receive/delivery timestamps, receiver receive timestamp, and injection timestamp. Connected interactive receivers emit `receiver_received`, `acknowledged`, and `injected` as they hand messages to Pi; duplicate IDs are acknowledged but injected at most once per receiving session. Broker mailbox delivery for temporarily disconnected targets can still report queued delivery. If an `ask` times out, the timeout names the message ID and last known delivery state. Timeout is not cancellation: an injected or broker-queued message may remain actionable unless an explicit cancellation path says otherwise.
+Incoming messages carry diagnostic metadata end to end: stable message ID, sender sequence, sender timestamp, broker receive/delivery timestamps, receiver receive timestamp, and injection timestamp. Connected interactive receivers emit `receiver_received`, `acknowledged`, and `injected` as they hand messages to Selesai; duplicate IDs are acknowledged but injected at most once per receiving session. Broker mailbox delivery for temporarily disconnected targets can still report queued delivery. If an `ask` times out, the timeout names the message ID and last known delivery state. Timeout is not cancellation: an injected or broker-queued message may remain actionable unless an explicit cancellation path says otherwise.
 
 Cancellation is explicit: call `intercom({ action: "cancel", messageId })` to request cancellation of a message you originally sent. Connected interactive messages are injected immediately, so the receiver normally reports `cancellation_requested` rather than pretending it removed work from a private queue. Supersede is also explicit: pass `supersedes: "old-message-id"` on a new `send` or `ask`. The broker only allows same sender → same receiver supersedes, marks the old message `superseded`, and sends the replacement with a new ID; an already-steered old message may still be processed. Retries are never automatic; a retry should be a new authored message, optionally linked with `retryOf`.
 
@@ -397,6 +397,7 @@ Create `~/.selesai/agent/intercom/config.json`:
   "brokerArgs": ["--no-install", "tsx"],
   "confirmSend": false,
   "inboundTrigger": "always",
+  "toolVisibility": "always",
   "enabled": true,
   "replyHint": true,
   "status": "researching"
@@ -409,11 +410,12 @@ Create `~/.selesai/agent/intercom/config.json`:
 | `brokerArgs` | `["--no-install", "tsx"]` | Advanced trusted arguments passed to custom `brokerCommand` before the broker script path |
 | `confirmSend` | false | Show a confirmation dialog before ordinary or inferred sends from an interactive session with UI; caller-supplied `replyTo` skips it |
 | `inboundTrigger` | `"always"` | Auto-trigger policy for inbound broker messages: `"always"`, `"replies"`, or `"never"`. Local in-process subagent relay events still trigger the addressed session. |
+| `toolVisibility` | `"always"` | When the generic `intercom` tool enters the active model tool set: `"always"` or `"after-first-use"`. Lazy visibility reveals it after an inbound broker message, a successful overlay send, or loading the bundled skill. It does not hide the child-only `contact_supervisor` tool. |
 | `enabled` | true | Enable/disable intercom entirely |
 | `replyHint` | true | Include reply instruction in incoming messages |
 | `status` | — | Optional custom status suffix shown after the automatic lifecycle status, for example `thinking · researching` |
 
-If `config.json` cannot be parsed or contains an invalid value, pi-intercom fails to load the config and throws an error, so the misconfiguration is surfaced immediately instead of silently changing behavior.
+If `config.json` cannot be parsed or contains an invalid value, pi-intercom logs the error and fails closed for inbound broker auto-triggering by using `inboundTrigger: "never"` until the config is fixed.
 
 Custom broker commands are trusted local configuration: anyone who can edit this config can choose the executable used for future broker auto-spawns. For example, if you have Bun installed and want it to start the broker directly, use:
 
@@ -424,7 +426,9 @@ Custom broker commands are trusted local configuration: anyone who can edit this
 }
 ```
 
-Pi-intercom publishes live session status automatically. Sessions register as `idle`, switch to `thinking` while the agent is running, show `tool:<name>` during tool execution, and return to `idle` on agent completion. If `status` is set in config, it is appended as context instead of replacing the lifecycle status.
+Selesai Intercom publishes live session status automatically. Sessions register as `idle`, switch to `thinking` while the agent is running, show `tool:<name>` during tool execution, and return to `idle` on agent completion. If `status` is set in config, it is appended as context instead of replacing the lifecycle status.
+
+Set `PI_INTERCOM_SCOPE_ID` before starting Selesai to opt a session into an opaque broker routing scope. The value is trimmed. Empty values are treated as unscoped. A scoped session can list, address by full ID, name, ID prefix, or cwd, receive presence and session lifecycle events, recover queued mailbox messages, and use extension-channel owner, publish, and state traffic only with sessions that registered the exact same scope. Scoped sessions and unscoped sessions do not cross this boundary. Existing unscoped behavior is unchanged when the variable is not set.
 
 By default, runtime state and config live under `~/.selesai/agent/intercom`. If Selesai is launched with `SELESAI_CODING_AGENT_DIR`, pi-intercom uses `$SELESAI_CODING_AGENT_DIR/intercom` instead, including `config.json`, broker PID/lock files, sockets, and launcher state.
 
@@ -465,6 +469,35 @@ The broker:
 
 `channel.publish()` accepts payloads up to 16 KiB. A `capable` broadcast includes the sender, so consumers must not blindly republish messages they receive. `channel.commitState()` uses compare-and-swap against the last observed revision. Capabilities registered after the broker connection is established are synchronized without reconnecting. Clients connected to an older broker see the channel as unsupported and do not send extension operations.
 
+### Extension outbox
+
+Same-process extensions can request a user-visible intercom send through the consent-aware outbox. Emit `intercom:outbox-request` with a unique `requestId`; listen for `intercom:outbox-result` and treat `sent`, `rejected`, `blocked`, and `failed` as terminal states. There is no fire-and-forget mode.
+
+```typescript
+import {
+  INTERCOM_OUTBOX_REQUEST_EVENT,
+  INTERCOM_OUTBOX_RESULT_EVENT,
+  type IntercomOutboxResult,
+} from "pi-intercom/extension-api.ts";
+
+pi.events.on(INTERCOM_OUTBOX_RESULT_EVENT, (result: IntercomOutboxResult) => {
+  if (result.requestId === "example-request-1") {
+    // Handle the terminal result.
+  }
+});
+
+pi.events.emit(INTERCOM_OUTBOX_REQUEST_EVENT, {
+  version: 1,
+  requestId: "example-request-1",
+  extensionId: "example-extension",
+  extensionName: "Example Extension",
+  to: "planner",
+  message: "Build finished.",
+});
+```
+
+`confirmSend` applies to outbox requests. If confirmation is required and no UI is available, the request fails closed with `confirmation_unavailable`. The outbox resolves the target through the current session's scoped intercom client, so extensions cannot choose the sender, scope, or resolved target ID. Duplicate `requestId` values are rejected and do not deliver again. Receiver messages include structured `extension_outbox` provenance in message details; provenance is not prepended to the message body.
+
 ## How It Works
 
 ```mermaid
@@ -497,7 +530,7 @@ The broker is a standalone TypeScript process that manages session registration
 
 Messages use length-prefixed JSON over a local socket/pipe transport (4-byte length + JSON payload) to handle fragmentation properly. The protocol includes request correlation for session listing, explicit delivery failures, validation for malformed or out-of-order messages, a frame-size cap, per-connection local rate limiting, and no-op presence coalescing.
 
-Session IDs are the trusted addressing key. Duplicate names remain allowed for same-user workflows, but sends to ambiguous names fail and users should target the stable session ID shown by `list`/`status` in trust-sensitive flows. Mail queued for a disconnected session is redelivered to a session that reconnects under the same session ID, or to a session that matches both its explicit name and its directory, so a same-named session in a different project never inherits another project's queued messages. Runtime-only `subagent-chat-...` aliases are excluded from name-based mailbox reconnection, and a disconnected mailbox is never remapped to the sender. Set `PI_INTERCOM_STABLE_ID` or `stableId` in `config.json` to pin a session's intercom ID across full process relaunches; `config.json` is machine-global, so a fixed `stableId` there applies to every session on the machine and the newest registration takes over that identity. The broker owns local trust metadata such as `trustedLocal`; `peerUid` is reserved for runtimes that can expose real peer credentials and is left unset otherwise. Client-supplied cwd/model/pid/status are display metadata, not authentication.
+Session IDs are the trusted addressing key within one broker routing scope. Duplicate names remain allowed for same-user workflows, but sends to ambiguous names fail and users should target the stable session ID shown by `list`/`status` in trust-sensitive flows. Mail queued for a disconnected session is redelivered to a session that reconnects under the same session ID, or to a session that matches both its explicit name and its directory, so a same-named session in a different project never inherits another project's queued messages. Runtime-only `subagent-chat-...` aliases are excluded from name-based mailbox reconnection, and a disconnected mailbox is never remapped to the sender. Set `PI_INTERCOM_STABLE_ID` or `stableId` in `config.json` to pin a session's intercom ID across full process relaunches; `config.json` is machine-global, so a fixed `stableId` there applies to every session on the machine and the newest registration takes over that identity only within the same `PI_INTERCOM_SCOPE_ID` boundary. The broker owns local trust metadata such as `trustedLocal`; `peerUid` is reserved for runtimes that can expose real peer credentials and is left unset otherwise. Client-supplied cwd/model/pid/status are display metadata, not authentication.
 
 Async extension work (startup, inbound flushes, reconnects, overlays, and relays) no-ops if the session shuts down or reloads before it settles.
 
@@ -509,7 +542,7 @@ Runtime files live at `~/.selesai/agent/intercom/` by default, or `$SELESAI_CODI
 - `broker.port.json` — Dynamic localhost TCP endpoint, only when Windows TCP transport is explicitly enabled
 - `config.json` — User configuration
 
-Supported `config.json` keys include `stableId` for restart-stable addressing, `status` for a custom status suffix, `inboundTrigger` (`always`, `replies`, or `never`), `replyHint`, `confirmSend`, and advanced broker launch overrides.
+Supported `config.json` keys include `stableId` for restart-stable addressing, `status` for a custom status suffix, `inboundTrigger` (`always`, `replies`, or `never`), `toolVisibility` (`always` or `after-first-use`), `replyHint`, `confirmSend`, and advanced broker launch overrides.
 
 ## Design Decisions