pi-plus-sdk 0.1.5 → 0.1.6

package/CHANGELOG.md

@@ -4,7 +4,7 @@
 
 ### Added
 
-- Runtime settings layering for hub profiles applies to SDK hosts with no environment plumbing (shared `loader/redirects.mjs` entry for `coding-agent/src/core/settings-manager.ts`): whenever the agent dir passed to `SettingsManager.create` is a hub-materialized profile dir (a direct child of `~/.pi/pi-hub/profiles`, honoring `PI_HUB_PI_DIR`/`PI_HUB_DIR`; the pipi-set `PI_PLUS_BASE_AGENT_DIR` marker also still activates it), the global scope reads the base agent `settings.json` deep-merged under the profile `settings.json` with the profile winning, and writes route per top-level key — `defaultProvider`/`defaultModel` to the profile file, everything else to the agent file with any profile shadow cleared. Any other agent dir keeps `SettingsManager.create` behaving exactly as upstream.
+- Runtime settings layering for hub profiles applies to SDK hosts with no environment plumbing (shared `loader/redirects.mjs` entry for `coding-agent/src/core/settings-manager.ts`): whenever the agent dir passed to `SettingsManager.create` is a hub-materialized profile dir (a direct child of `~/.pi/pi-hub/profiles`, honoring `PI_HUB_PI_DIR`/`PI_HUB_DIR`; the pipi-set `PI_PLUS_BASE_AGENT_DIR` marker also still activates it), the global scope reads the base agent `settings.json` deep-merged under the profile `settings.json` with the profile winning, and writes route per top-level key — the profile-scoped `defaultProvider`/`defaultModel`/`defaultThinkingLevel` to the profile file, everything else to the agent file with any profile shadow cleared. Any other agent dir keeps `SettingsManager.create` behaving exactly as upstream.
 - The pi-plus context settings are re-exported from the SDK surface (`packages/plus/src/context/threshold-setting.ts`): `readPlusSettings/writePlusSettings/getPlusSettingsPath` for the pi-plus settings store next to `settings.json`, plus the typed getters/setters and UI formatters behind the pipi `/settings` rows — `get/setAutoCompactThresholdPercent` (default 80%), `get/setContextFloorTokens` (default/built-in minimum 13000), and `get/setContextWindowCapTokens` (undefined = no cap). Embedding hosts get the same knobs the TUI edits, against the same file detection actually reads. `SessionManager.deleteSession` and `SessionManager.search` (new in the re-exported upstream surface) cover transcript deletion and title/content search for history-management UIs.
 - Initial **`pi-plus-sdk`** npm artifact (published from this package): the programmatic pi-plus entry, split out of the `pi-plus` package so library hosts embed pi in-process with zero CLI logic. `import { createPlusAgentSession, createPlusUIContext, plusSdkExtensionFactories } from "pi-plus-sdk"` gives a host application (e.g. a desktop app) the compaction/context/reasoning overrides (baked in at bundle time by the shared redirect plugin) plus the nine non-TUI pi-plus extensions (subagent, tasks, memory, plan, ask-user, hooks, context-guard, /cd, /init). `createPlusAgentSession()` composes the upstream `createAgentSession` with a `DefaultResourceLoader` carrying those factories, reloads it, and binds extensions once (emitting `session_start`); hosts pass dialog handlers via the `ui` option to get working `ask_user` questions (select/confirm/input bridged to native UI), or omit it for a headless session. The staged package has an `exports` map (deep imports closed off), ships a hand-authored `api.d.ts` re-exporting `@earendil-works/pi-coding-agent` types (added as an exact-pinned dependency for type resolution only; the runtime stays self-contained), and has no bin. Hosts without a pi CLI on PATH should pass `excludeTools: ["subagent"]`: the subagent tool launches a pi subprocess and could otherwise relaunch the host app itself.
 - The `/init` extension (shared core, `packages/plus/src/extensions/init/`) is registered by `plusSdkExtensionFactories` too: the `/init` command creates or improves `AGENTS.md` at the cwd root — pi's default project instructions file, loaded automatically by upstream's context loader.
@@ -12,3 +12,4 @@
 - `addProfileModel(name, model)` and `removeProfileModel(name, model)` join the curated profile surface (implemented in `@earendil-works/pi-hub`): append a model without selecting it (bounded by the same three-models-per-profile limit) and remove one with the `pipi` CLI delete semantics — the default promotes to the next remaining model, and removing the last clears `models`/`model` so the profile inherits. Both return a human-readable message for host UIs, completing the per-profile model editing that `setProfileDefaultModel` started.
 - `setProfileDefaultModel(name, model)` joins the curated profile surface (implemented in `@earendil-works/pi-hub`): selects a profile's default model — the list position 1 that materialization writes as `settings.defaultModel` — moving an existing model or adding a new one (bounded by the same three-models-per-profile limit the `pipi` CLI enforces), and returns a human-readable message for host UIs. This is the library entry for the "select model" behavior that previously lived only in the CLI command layer.
 - The SDK build redirects the upstream `main.ts` to a stub that throws — the CLI entry graph (startup UI, session picker, auth command, …) stays out of `api.js`, and calling `main()` is a clear error instead of silently running un-layered upstream pi. The re-exported `parseArgs`/`SettingsSelectorComponent` resolve to upstream pi (no pipi help text or CLI settings rows leak into the library surface).
+- The session recap extension (`pi-plus-session-recap`, shared core `packages/plus/src/extensions/recap/`) joins `plusSdkExtensionFactories`: after the first prompt is answered and after every compaction, a one-off LLM call distills a ≤8-word recap applied as the session name via `setSessionName`, so embedding hosts' session lists/titles read meaningfully without manual naming. Manual renames lock the session against further recaps; failures are logged and never surface.

package/README.md

@@ -25,9 +25,9 @@ await session.prompt("Review this repository");
 ```
 
 - The full pi-plus layer is included: the compaction/context/reasoning overrides are
-  baked into `api.js` by the shared bundle-time redirect plugin, and the nine
+  baked into `api.js` by the shared bundle-time redirect plugin, and the ten
   non-TUI pi-plus extensions (subagent, tasks, memory, plan, ask-user, hooks,
-  context-guard, `/cd`, `/init`) are registered exactly as the CLI wrapper registers them. No CLI
+  context-guard, recap, `/cd`, `/init`) are registered exactly as the CLI wrapper registers them. No CLI
   logic ships in this artifact: no hub command dispatch (`pipi profile ...`), no
   completion, no pipi help text, no banner/vim/tab-title/plain-tools.
 - Profile management ships as a library: the curated `@earendil-works/pi-hub`
@@ -49,10 +49,14 @@ await session.prompt("Review this repository");
   `SessionManager.deleteSession(path)` to remove a transcript.
 - Provider login ships as a library (`src/auth.ts`): `loginProvider(providerId, { agentDir?, interaction?, signal?, method? })`
   runs pi's model-runtime login flow (OAuth login page / API-key setup — the same
-  flow `pipi profile add <name> -p <provider>` triggers) and persists the credential
+  flow `pipi profile add <name> -p <provider>` and the `--sign-in` flag on
+  `pipi profile add`/`profile update` trigger) and persists the credential
   to `<agentDir>/auth.json`; `createTerminalAuthInteraction()` provides the readline
   terminal UI for CLI use, and hosts pass their own `AuthInteraction` to drive the
-  prompts from a custom UI. pi-plus disables the TUI `/login` (the `interactive-mode`
+  prompts from a custom UI. To mirror the CLI's sign-in token overwrite, write the
+  returned credential's `key` into `Profile.token` via `updateProfile` (and clear
+  the field for OAuth logins, whose credential only lives in the profile's
+  `auth.json` — a stored token would overwrite it at the next launch). pi-plus disables the TUI `/login` (the `interactive-mode`
   and `slash-commands` core redirects are baked in here too), so this is the login
   entry for the whole product.
 - `createPlusAgentSession()` extends the upstream `createAgentSession` (re-exported,

package/api.d.ts

@@ -16,13 +16,48 @@ import type {
 	CreateAgentSessionResult,
 	DefaultResourceLoaderOptions,
 	ExtensionCommandContextActions,
+	ExtensionContext,
 	ExtensionError,
 	ExtensionUIContext,
 	InlineExtension,
+	ToolCallEvent,
+	ToolCallEventResult,
 } from "@earendil-works/pi-coding-agent";
 
 export declare const plusSdkExtensionFactories: InlineExtension[];
 
+// --- pi-plus-permissions (bypass | acceptEdits | plan tool-call gate) ------
+
+export type PermissionMode = "bypass" | "acceptEdits" | "plan";
+
+/** Canonical order; hosts cycle forward through this list on their shortcut. */
+export declare const PERMISSION_MODES: PermissionMode[];
+
+export declare const PERMISSION_MODE_LABELS: Record<PermissionMode, string>;
+
+/** Mutable holder shared between the host and the extension. */
+export interface PermissionModeState {
+	mode: PermissionMode;
+}
+
+export interface PermissionsExtensionOptions {
+	/** Host-owned state; a fresh bypass-on holder is created when omitted. */
+	state?: PermissionModeState;
+	/** Called after every mode change, including host-side writes. */
+	onModeChange?: (mode: PermissionMode) => void;
+}
+
+export declare function parsePermissionMode(arg: string): PermissionMode | undefined;
+
+export declare function gatePermissionToolCall(
+	event: ToolCallEvent,
+	mode: PermissionMode,
+	ctx: ExtensionContext,
+): Promise<ToolCallEventResult | undefined>;
+
+/** Build the pi-plus-permissions inline extension for a host. */
+export declare function createPermissionsExtension(options?: PermissionsExtensionOptions): InlineExtension;
+
 export interface PlusUIDialogHandlers {
 	select(title: string, options: string[]): Promise<string | undefined>;
 	confirm(title: string, message: string): Promise<boolean>;