pi-plus-sdk 0.1.1 → 0.1.3

package/CHANGELOG.md

@@ -4,5 +4,6 @@
 
 ### Added
 
-- 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 seven non-TUI pi-plus extensions (subagent, tasks, memory, plan, ask-user, hooks, context-guard). `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.
+- 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 `PI.md` at the cwd root and `PI.md` is auto-loaded into every agent run via the system prompt's context files.
 - 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).

package/README.md

@@ -25,11 +25,18 @@ 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 seven
+  baked into `api.js` by the shared bundle-time redirect plugin, and the nine
   non-TUI pi-plus extensions (subagent, tasks, memory, plan, ask-user, hooks,
-  context-guard) are registered exactly as the CLI wrapper registers them. No CLI
-  logic ships in this artifact: no hub dispatch, no completion, no pipi help text,
-  no banner/vim/tab-title/plain-tools/`/cd`.
+  context-guard, `/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`
+  surface is re-exported (`src/profiles.ts`) — `loadProfiles/findProfile/
+  addProfile/updateProfile/removeProfile/renameProfile/setDefaultProfile/
+  clearDefaultProfile/getDefaultProfileName` for `~/.pi/profiles.json`, and
+  `materializeProfile/removeProfileDir/profileDirFor/AGENT_DIR/
+  syncProfilePackagesToSource` for the per-profile agent dirs. Hosts get the
+  exact contract the `pipi` CLI dispatches instead of reimplementing it.
 - `createPlusAgentSession()` extends the upstream `createAgentSession` (re-exported,
   with the whole upstream SDK surface) and always binds extensions once — do not call
   `session.bindExtensions()` yourself. Pass `ui` dialog handlers to get working

package/api.d.ts

@@ -42,3 +42,56 @@ export interface CreatePlusAgentSessionOptions extends CreateAgentSessionOptions
 export declare function createPlusAgentSession(
 	options?: CreatePlusAgentSessionOptions,
 ): Promise<CreateAgentSessionResult>;
+
+/**
+ * Profile management: the curated @earendil-works/pi-hub surface bundled into
+ * api.js (profiles.json CRUD + per-profile materialized agent dirs). Types are
+ * declared inline because pi-hub is not a dependency of this package — keep
+ * them in sync with packages/hub/src/types.ts.
+ */
+export interface Profile {
+	provider?: string;
+	model?: string;
+	models?: string[];
+	thinking?: string;
+	token?: string;
+	url?: string;
+	/** Arbitrary settings.json overrides, merged over the source agent settings.
+	 *  A null value deletes the key from the materialized settings.json. */
+	settings?: Record<string, unknown>;
+}
+
+export interface ProfilesData {
+	profiles: Record<string, Profile>;
+	default?: string;
+}
+
+export interface AgentSettingsData {
+	defaultProvider?: string;
+	defaultModel?: string;
+	defaultThinkingLevel?: string;
+	skills?: unknown;
+	[key: string]: unknown;
+}
+
+export declare const THINKING_LEVELS: string[];
+
+/** Marker stored in `profiles.json` `default` meaning "no profile, run plain pi". */
+export declare const BUILT_IN_DEFAULT: "__builtin__";
+
+/** Source agent dir (PI_CODING_AGENT_DIR or ~/.pi/agent): profiles without an applied profile. */
+export declare const AGENT_DIR: string;
+
+export declare function loadProfiles(): ProfilesData;
+export declare function findProfile(name: string): Profile | undefined;
+export declare function getDefaultProfileName(): string | undefined;
+export declare function setDefaultProfile(name: string): void;
+export declare function clearDefaultProfile(): void;
+export declare function addProfile(name: string, profile: Profile): void;
+export declare function updateProfile(name: string, profile: Profile): void;
+export declare function removeProfile(name: string): void;
+export declare function renameProfile(oldName: string, newName: string): void;
+export declare function profileDirFor(name: string): string;
+export declare function materializeProfile(name: string, profile: Profile): string;
+export declare function removeProfileDir(name: string): void;
+export declare function syncProfilePackagesToSource(profileDir: string): boolean;