@oh-my-pi/pi-coding-agent 2.3.1337 → 3.0.1337

package/docs/config-usage.md

@@ -0,0 +1,113 @@
+# Config Module Usage Map
+
+This document shows how each file uses the config module and what subpaths they access.
+
+## Overview Diagram
+
+```
+┌─────────────────────────────────────────────────────────────────────────────────┐
+│                              config.ts exports                                   │
+├─────────────────────────────────────────────────────────────────────────────────┤
+│ Constants:        APP_NAME, CONFIG_DIR_NAME, VERSION, ENV_AGENT_DIR             │
+│ Single paths:     getAgentDir, getAuthPath, getModelsPath, getCommandsDir, ...  │
+│ Multi-config:     getConfigDirs, getConfigDirPaths, findConfigFile,             │
+│                   readConfigFile, findNearestProjectConfigDir, ...              │
+└─────────────────────────────────────────────────────────────────────────────────┘
+```
+
+## Usage by Category
+
+### 1. Display/Branding Only (no file I/O)
+
+| File | Imports | Purpose |
+|------|---------|---------|
+| `cli/args.ts` | `APP_NAME`, `CONFIG_DIR_NAME`, `ENV_AGENT_DIR` | Help text, env var names |
+| `cli/plugin-cli.ts` | `APP_NAME` | Command output |
+| `cli/update-cli.ts` | `APP_NAME`, `VERSION` | Update messages |
+| `core/export-html/index.ts` | `APP_NAME` | HTML export title |
+| `modes/interactive/components/welcome.ts` | `APP_NAME` | Welcome banner |
+| `utils/tools-manager.ts` | `APP_NAME` | Tool download messages |
+
+### 2. Single Fixed Paths (user-level only)
+
+| File | Imports | Path | Purpose |
+|------|---------|------|---------|
+| `core/logger.ts` | `CONFIG_DIR_NAME` | `~/.omp/logs/` | Log file directory |
+| `core/agent-session.ts` | `getAuthPath` | `~/.omp/agent/auth.json` | Error messages |
+| `core/session-manager.ts` | `getAgentDir` | `~/.omp/agent/sessions/` | Session storage |
+| `modes/interactive/theme/theme.ts` | `getCustomThemesDir` | `~/.omp/agent/themes/` | Custom themes |
+| `modes/interactive/interactive-mode.ts` | `getAuthPath`, `getDebugLogPath` | auth.json, debug log | Status messages |
+| `utils/changelog.ts` | `getChangelogPath` | Package CHANGELOG.md | Re-exports |
+| `core/system-prompt.ts` | `getAgentDir`, `getDocsPath`, `getExamplesPath`, `getReadmePath` | Package assets + AGENTS.md | System prompt building |
+| `migrations.ts` | `getAgentDir` | `~/.omp/agent/` | Auth/session migration |
+| `core/plugins/installer.ts` | `getAgentDir` | `~/.omp/agent/` | Plugin installation |
+| `core/plugins/paths.ts` | `CONFIG_DIR_NAME` | `~/.omp/plugins/` | Plugin directories |
+
+### 3. Multi-Config Discovery (with fallbacks)
+
+These use the new helpers to check `.omp`, `.pi`, `.claude` directories:
+
+| File | Helper Used | Subpath(s) | Levels |
+|------|-------------|------------|--------|
+| `main.ts` | `findConfigFile` | `SYSTEM.md` | project |
+| `core/sdk.ts` | `getConfigDirPaths` | `auth.json`, `models.json` | user |
+| `core/settings-manager.ts` | `readConfigFile` | `settings.json` | user+project |
+| `core/skills.ts` | `getConfigDirPaths` | `skills/` | user+project |
+| `core/slash-commands.ts` | `getConfigDirPaths` | `commands/` | project |
+| `core/hooks/loader.ts` | `getConfigDirPaths` | `hooks/` | project |
+| `core/custom-tools/loader.ts` | `getConfigDirPaths` | `tools/` | project |
+| `core/custom-commands/loader.ts` | `getConfigDirPaths` | `commands/` | project |
+| `core/plugins/paths.ts` | `getConfigDirPaths` | `plugin-overrides.json` | project |
+| `core/mcp/config.ts` | `getConfigDirPaths` | `mcp.json` | user+project |
+| `core/tools/lsp/config.ts` | `getConfigDirPaths` | `lsp.json`, `.lsp.json` | user+project |
+| `core/tools/task/commands.ts` | `getConfigDirPaths`, `findAllNearestProjectConfigDirs` | `commands/` | user+project |
+| `core/tools/task/discovery.ts` | `getConfigDirs`, `findAllNearestProjectConfigDirs` | `agents/` | user+project |
+| `core/tools/task/model-resolver.ts` | `readConfigFile` | `settings.json` | user |
+| `core/tools/web-search/auth.ts` | `getConfigDirPaths` | `` (root for models.json, auth.json) | user |
+
+## Subpath Summary
+
+```
+User-level (~/.omp/agent/, ~/.pi/agent/, ~/.claude/):
+├── auth.json          ← sdk.ts, web-search/auth.ts
+├── models.json        ← sdk.ts, web-search/auth.ts
+├── settings.json      ← settings-manager.ts, task/model-resolver.ts
+├── commands/          ← slash-commands.ts, custom-commands/loader.ts, task/commands.ts
+├── hooks/             ← hooks/loader.ts
+├── tools/             ← custom-tools/loader.ts
+├── skills/            ← skills.ts
+├── themes/            ← theme.ts (user-level only, no fallback)
+├── sessions/          ← session-manager.ts (user-level only, no fallback)
+├── agents/            ← task/discovery.ts
+└── AGENTS.md          ← system-prompt.ts
+
+User-level root (~/.omp/, ~/.pi/, ~/.claude/) - not under agent/:
+├── mcp.json           ← mcp/config.ts
+├── plugins/           ← plugins/paths.ts (primary only)
+└── logs/              ← logger.ts (primary only)
+
+Project-level (.omp/, .pi/, .claude/):
+├── SYSTEM.md          ← main.ts
+├── settings.json      ← settings-manager.ts
+├── commands/          ← slash-commands.ts, custom-commands/loader.ts, task/commands.ts
+├── hooks/             ← hooks/loader.ts
+├── tools/             ← custom-tools/loader.ts
+├── skills/            ← skills.ts
+├── agents/            ← task/discovery.ts
+├── plugin-overrides.json ← plugins/paths.ts
+├── lsp.json           ← lsp/config.ts
+└── .mcp.json          ← mcp/config.ts
+
+Special paths (not under agent/):
+├── ~/.omp/plugins/    ← plugins/paths.ts
+└── ~/.omp/logs/       ← logger.ts
+```
+
+## Files Using Manual Paths (Intentionally)
+
+These files construct paths manually because they only use the primary config dir:
+
+| File | Current Approach | Reason |
+|------|------------------|--------|
+| `core/logger.ts` | `CONFIG_DIR_NAME` for logs dir | Logs only written to primary (~/.omp/logs/) |
+| `core/plugins/paths.ts` | `CONFIG_DIR_NAME` for plugins dir | Plugins only installed in primary (~/.omp/plugins/) |

package/docs/custom-tools.md

@@ -1,4 +1,4 @@
-> pi can create custom tools. Ask it to build one for your use case.
+> omp can create custom tools. Ask it to build one for your use case.
 
 # Custom Tools
 
@@ -32,7 +32,7 @@ See [examples/custom-tools/](../examples/custom-tools/) for working examples.
 
 ## Quick Start
 
-Create a file `~/.pi/agent/tools/hello/index.ts`:
+Create a file `~/.omp/agent/tools/hello/index.ts`:
 
 ```typescript
 import type { CustomToolFactory } from "@oh-my-pi/pi-coding-agent";
@@ -57,7 +57,7 @@ const factory: CustomToolFactory = (pi) => ({
 export default factory;
 ```
 
-The tool is automatically discovered and available in your next pi session.
+The tool is automatically discovered and available in your next omp session.
 
 ## Tool Locations
 
@@ -65,15 +65,15 @@ Tools must be in a subdirectory with an `index.ts` entry point:
 
 | Location                            | Scope                 | Auto-discovered |
 | ----------------------------------- | --------------------- | --------------- |
-| `~/.pi/agent/tools/*/index.ts`      | Global (all projects) | Yes             |
-| `.pi/tools/*/index.ts`              | Project-local         | Yes             |
+| `~/.omp/agent/tools/*/index.ts`      | Global (all projects) | Yes             |
+| `.omp/tools/*/index.ts`              | Project-local         | Yes             |
 | `settings.json` `customTools` array | Configured paths      | Yes             |
 | `--tool <path>` CLI flag            | One-off/debugging     | No              |
 
 **Example structure:**
 
 ```
-~/.pi/agent/tools/
+~/.omp/agent/tools/
 ├── hello/
 │   └── index.ts        # Entry point (auto-discovered)
 └── complex-tool/
@@ -222,7 +222,7 @@ async execute(toolCallId, params, onUpdate, ctx, signal) {
 async execute(toolCallId, params, onUpdate, ctx, signal) {
   const { path } = params as { path: string };
 
-  // Throw on error - pi will catch it and report to the LLM
+  // Throw on error - omp will catch it and report to the LLM
   if (!fs.existsSync(path)) {
     throw new Error(`File not found: ${path}`);
   }
@@ -537,5 +537,5 @@ See [`examples/custom-tools/todo/index.ts`](../examples/custom-tools/todo/index.
 Test with:
 
 ```bash
-pi --tool packages/coding-agent/examples/custom-tools/todo/index.ts
+omp --tool packages/coding-agent/examples/custom-tools/todo/index.ts
 ```

package/docs/extension-loading.md

@@ -27,7 +27,7 @@ Extensions can be loaded from:
 ### Directories
 ```
 ./my-hooks/
-~/.pi/agent/hooks/
+~/.omp/agent/hooks/
 ```
 
 ### npm Packages
@@ -51,7 +51,7 @@ git:https://github.com/user/repo#branch      # branch
 
 ### Permanent (settings.json)
 ```
-~/.pi/agent/
+~/.omp/agent/
   hooks/
     my-local-hook.ts                    # root-level file
     complex-hook/                       # directory with entry point
@@ -86,7 +86,7 @@ git:https://github.com/user/repo#branch      # branch
 
 ### Ephemeral (CLI flags)
 ```
-/tmp/pi-extensions/
+/tmp/omp-extensions/
   hooks/
     npm/
       my-hook@1.0.0/
@@ -148,8 +148,8 @@ scan(baseDir, config):
 ```
 
 **Default directories scanned (always, regardless of settings.json):**
-- `~/.pi/agent/<type>/`
-- `<cwd>/.pi/<type>/`
+- `~/.omp/agent/<type>/`
+- `<cwd>/.omp/<type>/`
 
 ## Extension Packs
 
@@ -248,58 +248,58 @@ Patterns are glob patterns matched against extension paths.
 
 ### Adding Sources
 ```bash
-pi --hook <path|npm:|git:>      # add hook source (repeatable)
-pi --tool <path|npm:|git:>      # add custom tool source (repeatable)
-pi --skill <path|npm:|git:>     # add skill source (repeatable)
-pi --theme <path|npm:|git:>     # add theme source (repeatable)
+omp --hook <path|npm:|git:>      # add hook source (repeatable)
+omp --tool <path|npm:|git:>      # add custom tool source (repeatable)
+omp --skill <path|npm:|git:>     # add skill source (repeatable)
+omp --theme <path|npm:|git:>     # add theme source (repeatable)
 ```
 
 **Installation locations for npm/git sources:**
 
 | Source | Install location |
 |--------|------------------|
-| CLI flags | `/tmp/pi-extensions/<type>/npm/` or `git/` |
-| Global settings (`~/.pi/agent/settings.json`) | `~/.pi/agent/<type>/npm/` or `git/` |
-| Project settings (`<cwd>/.pi/settings.json`) | `<cwd>/.pi/<type>/npm/` or `git/` |
+| CLI flags | `/tmp/omp-extensions/<type>/npm/` or `git/` |
+| Global settings (`~/.omp/agent/settings.json`) | `~/.omp/agent/<type>/npm/` or `git/` |
+| Project settings (`<cwd>/.omp/settings.json`) | `<cwd>/.omp/<type>/npm/` or `git/` |
 
 File/directory paths are used directly (no installation).
 
 - **CLI = ephemeral**: cached in temp until OS clears `/tmp/`
 - **Global settings = permanent**: installed to user's agent directory
-- **Project settings = project-local**: installed to project's `.pi/` directory
+- **Project settings = project-local**: installed to project's `.omp/` directory
 
 Examples:
-- `--hook npm:my-hook@1.0.0` → `/tmp/pi-extensions/hooks/npm/my-hook@1.0.0/`
-- Global settings.json `npm:my-hook@1.0.0` → `~/.pi/agent/hooks/npm/my-hook@1.0.0/`
-- Project settings.json `npm:my-hook@1.0.0` → `<cwd>/.pi/hooks/npm/my-hook@1.0.0/`
+- `--hook npm:my-hook@1.0.0` → `/tmp/omp-extensions/hooks/npm/my-hook@1.0.0/`
+- Global settings.json `npm:my-hook@1.0.0` → `~/.omp/agent/hooks/npm/my-hook@1.0.0/`
+- Project settings.json `npm:my-hook@1.0.0` → `<cwd>/.omp/hooks/npm/my-hook@1.0.0/`
 
 This encourages: try via CLI, if you like it, add to settings.json for permanent install.
 
 ### Filtering
 ```bash
-pi --hooks "pattern1,pattern2,!excluded"       # filter hooks
-pi --custom-tools "pattern1,!excluded"         # filter custom tools
-pi --skills "pattern1,pattern2"                # filter skills
-pi --themes "pattern1"                         # filter themes
+omp --hooks "pattern1,pattern2,!excluded"       # filter hooks
+omp --custom-tools "pattern1,!excluded"         # filter custom tools
+omp --skills "pattern1,pattern2"                # filter skills
+omp --themes "pattern1"                         # filter themes
 ```
 
 ### Disabling
 ```bash
-pi --no-hooks                   # disable all hooks
-pi --no-custom-tools            # disable all custom tools
-pi --no-skills                  # disable all skills (already exists)
+omp --no-hooks                   # disable all hooks
+omp --no-custom-tools            # disable all custom tools
+omp --no-skills                  # disable all skills (already exists)
 ```
 
 ### Built-in Tools
 ```bash
-pi --tools read,bash,edit,write    # select which built-in tools to enable (unchanged)
+omp --tools read,bash,edit,write    # select which built-in tools to enable (unchanged)
 ```
 
 ## Settings Hierarchy
 
 Extensions are configured in settings.json at two levels:
-- **Global**: `~/.pi/agent/settings.json`
-- **Project**: `<cwd>/.pi/settings.json`
+- **Global**: `~/.omp/agent/settings.json`
+- **Project**: `<cwd>/.omp/settings.json`
 
 **Merge behavior:**
 - `paths`: **additive** - project paths are added to global paths
@@ -307,7 +307,7 @@ Extensions are configured in settings.json at two levels:
 
 **Example:**
 ```json
-// Global: ~/.pi/agent/settings.json
+// Global: ~/.omp/agent/settings.json
 {
   "hooks": {
     "paths": ["npm:audit-hooks@1.0.0"],
@@ -315,7 +315,7 @@ Extensions are configured in settings.json at two levels:
   }
 }
 
-// Project: .pi/settings.json
+// Project: .omp/settings.json
 {
   "hooks": {
     "paths": ["./project-hooks/"],
@@ -368,9 +368,9 @@ Extensions are configured in settings.json at two levels:
 ## Installation Flow
 
 Target directory depends on source:
-- **CLI flags**: `/tmp/pi-extensions/<type>/npm/` or `git/`
-- **Global settings.json**: `~/.pi/agent/<type>/npm/` or `git/`
-- **Project settings.json**: `<cwd>/.pi/<type>/npm/` or `git/`
+- **CLI flags**: `/tmp/omp-extensions/<type>/npm/` or `git/`
+- **Global settings.json**: `~/.omp/agent/<type>/npm/` or `git/`
+- **Project settings.json**: `<cwd>/.omp/<type>/npm/` or `git/`
 
 ### Atomic Installation
 
@@ -382,7 +382,7 @@ To prevent corrupted state from interrupted installs (Ctrl+C):
 
 ### npm Packages
 1. Parse specifier: `npm:@scope/pkg@1.2.3` → name: `@scope/pkg`, version: `1.2.3`
-2. Determine target dir based on source (CLI → temp, global → agent dir, project → cwd/.pi/)
+2. Determine target dir based on source (CLI → temp, global → agent dir, project → cwd/.omp/)
 3. If `<target>/` exists and has matching version in package.json → skip install
 4. Otherwise:
    - Remove stale `<target>.installing/` if exists
@@ -393,7 +393,7 @@ To prevent corrupted state from interrupted installs (Ctrl+C):
 
 ### Git Repositories
 1. Parse specifier: `git:https://github.com/user/repo@v1.0.0`
-2. Determine target dir based on source (CLI → temp, global → agent dir, project → cwd/.pi/)
+2. Determine target dir based on source (CLI → temp, global → agent dir, project → cwd/.omp/)
 3. If `<target>/` exists → skip clone
 4. Otherwise:
    - Remove stale `<target>.installing/` if exists
@@ -409,18 +409,18 @@ To prevent corrupted state from interrupted installs (Ctrl+C):
 Adds extension to settings.json and installs to disk.
 
 ```bash
-pi install <type> <source>              # global (default)
-pi install <type> -p <source>           # project-local
-pi install <type> --project <source>    # project-local
+omp install <type> <source>              # global (default)
+omp install <type> -p <source>           # project-local
+omp install <type> --project <source>    # project-local
 
 # Examples:
-pi install hook npm:@scope/my-hook@1.0.0
-  # → adds to ~/.pi/agent/settings.json
-  # → installs to ~/.pi/agent/hooks/npm/@scope/my-hook@1.0.0/
+omp install hook npm:@scope/my-hook@1.0.0
+  # → adds to ~/.omp/agent/settings.json
+  # → installs to ~/.omp/agent/hooks/npm/@scope/my-hook@1.0.0/
 
-pi install tool -p git:https://github.com/user/tool@v1.0.0
-  # → adds to <cwd>/.pi/settings.json
-  # → installs to <cwd>/.pi/tools/git/github.com/user/tool@v1.0.0/
+omp install tool -p git:https://github.com/user/tool@v1.0.0
+  # → adds to <cwd>/.omp/settings.json
+  # → installs to <cwd>/.omp/tools/git/github.com/user/tool@v1.0.0/
 ```
 
 ### Remove
@@ -428,12 +428,12 @@ pi install tool -p git:https://github.com/user/tool@v1.0.0
 Removes extension from settings.json and deletes from disk.
 
 ```bash
-pi remove <type> <name>                 # from global
-pi remove <type> -p <name>              # from project
+omp remove <type> <name>                 # from global
+omp remove <type> -p <name>              # from project
 
 # Examples:
-pi remove hook my-hook                  # from ~/.pi/agent/settings.json + delete
-pi remove skill -p brave-search         # from <cwd>/.pi/settings.json + delete
+omp remove hook my-hook                  # from ~/.omp/agent/settings.json + delete
+omp remove skill -p brave-search         # from <cwd>/.omp/settings.json + delete
 ```
 
 ### Update
@@ -441,15 +441,15 @@ pi remove skill -p brave-search         # from <cwd>/.pi/settings.json + delete
 Updates npm/git extensions to latest versions.
 
 ```bash
-pi update                               # all (project + global)
-pi update -p                            # project only
-pi update <type>...                     # specific types
-pi update -p <type>...                  # project, specific types
+omp update                               # all (project + global)
+omp update -p                            # project only
+omp update <type>...                     # specific types
+omp update -p <type>...                  # project, specific types
 
 # Examples:
-pi update                               # update everything
-pi update hook tool                     # update hooks and tools
-pi update -p skill                      # update project skills only
+omp update                               # update everything
+omp update hook tool                     # update hooks and tools
+omp update -p skill                      # update project skills only
 ```
 
 **Update behavior:**
@@ -461,13 +461,13 @@ pi update -p skill                      # update project skills only
 ## Loading Flow (Full)
 
 1. **Collect sources:**
-   - Default directories: `~/.pi/agent/<type>/`, `./.pi/<type>/`
+   - Default directories: `~/.omp/agent/<type>/`, `./.omp/<type>/`
    - settings.json `<type>.paths`
    - CLI `--<type>` arguments
 
-2. **Install remote sources:**
+3. **Install remote sources:**
    - Process `npm:` and `git:` specifiers
-   - Install to `~/.pi/agent/<type>/npm/` or `git/`
+   - Install to `~/.omp/agent/<type>/npm/` or `git/`
 
 3. **Scan all sources:**
    - Recursively discover extensions
@@ -621,7 +621,7 @@ export interface LoadExtensionsOptions {
   cwd: string;
   agentDir: string;
   globalPaths: string[];              // from global settings.json → install to agentDir
-  projectPaths: string[];             // from project settings.json → install to cwd/.pi/
+  projectPaths: string[];             // from project settings.json → install to cwd/.omp/
   cliPaths: string[];                 // from CLI flags → install to /tmp/
   filter: string[];                   // combined filter patterns
 }
@@ -656,7 +656,7 @@ export function getSkillsDir(): string {
 
 // getToolsDir() already exists
 // getThemesDir() = bundled themes (in package)
-// getCustomThemesDir() = ~/.pi/agent/themes/ (user themes) - already exists
+// getCustomThemesDir() = ~/.omp/agent/themes/ (user themes) - already exists
 ```
 
 ### `src/core/settings-manager.ts`

package/docs/hooks.md

@@ -1,8 +1,8 @@
-> pi can create hooks. Ask it to build one for your use case.
+> omp can create hooks. Ask it to build one for your use case.
 
 # Hooks
 
-Hooks are TypeScript modules that extend pi's behavior by subscribing to lifecycle events. They can intercept tool calls, prompt the user, modify results, inject messages, and more.
+Hooks are TypeScript modules that extend omp's behavior by subscribing to lifecycle events. They can intercept tool calls, prompt the user, modify results, inject messages, and more.
 
 **Key capabilities:**
 
@@ -24,7 +24,7 @@ See [examples/hooks/](../examples/hooks/) for working implementations, including
 
 ## Quick Start
 
-Create `~/.pi/agent/hooks/my-hook.ts`:
+Create `~/.omp/agent/hooks/my-hook.ts`:
 
 ```typescript
 import type { HookAPI } from "@oh-my-pi/pi-coding-agent";
@@ -46,17 +46,17 @@ export default function (pi: HookAPI) {
 Test with `--hook` flag:
 
 ```bash
-pi --hook ./my-hook.ts
+omp --hook ./my-hook.ts
 ```
 
 ## Hook Locations
 
 Hooks are auto-discovered from:
 
-| Location                 | Scope                 |
-| ------------------------ | --------------------- |
-| `~/.pi/agent/hooks/*.ts` | Global (all projects) |
-| `.pi/hooks/*.ts`         | Project-local         |
+| Location                  | Scope                 |
+| ------------------------- | --------------------- |
+| `~/.omp/agent/hooks/*.ts` | Global (all projects) |
+| `.omp/hooks/*.ts`         | Project-local         |
 
 Additional paths via `settings.json`:
 
@@ -99,7 +99,7 @@ Hooks are loaded via [jiti](https://github.com/unjs/jiti), so TypeScript works w
 ### Lifecycle Overview
 
 ```
-pi starts
+omp starts
   │
   └─► session_start
       │
@@ -509,7 +509,7 @@ Read-only access to session state. See `ReadonlySessionManager` in [`src/core/se
 ```typescript
 // Session info
 ctx.sessionManager.getCwd(); // Working directory
-ctx.sessionManager.getSessionDir(); // Session directory (~/.pi/agent/sessions)
+ctx.sessionManager.getSessionDir(); // Session directory (~/.omp/agent/sessions)
 ctx.sessionManager.getSessionId(); // Current session ID
 ctx.sessionManager.getSessionFile(); // Session file path (undefined with --no-session)
 
@@ -864,4 +864,4 @@ In print mode, `select()` returns `undefined`, `confirm()` returns `false`, `inp
 1. Open VS Code in hooks directory
 2. Open JavaScript Debug Terminal (Ctrl+Shift+P → "JavaScript Debug Terminal")
 3. Set breakpoints
-4. Run `pi --hook ./my-hook.ts`
+4. Run `omp --hook ./my-hook.ts`

package/docs/rpc.md

@@ -7,7 +7,7 @@ RPC mode enables headless operation of the coding agent via a JSON protocol over
 ## Starting RPC Mode
 
 ```bash
-pi --mode rpc [options]
+omp --mode rpc [options]
 ```
 
 Common options:
@@ -407,7 +407,7 @@ If output was truncated, includes `fullOutputPath`:
 		"exitCode": 0,
 		"cancelled": false,
 		"truncated": true,
-		"fullOutputPath": "/tmp/pi-bash-abc123.log"
+		"fullOutputPath": "/tmp/omp-bash-abc123.log"
 	}
 }
 ```
@@ -980,7 +980,7 @@ import subprocess
 import json
 
 proc = subprocess.Popen(
-    ["pi", "--mode", "rpc", "--no-session"],
+    ["omp", "--mode", "rpc", "--no-session"],
     stdin=subprocess.PIPE,
     stdout=subprocess.PIPE,
     text=True
@@ -1017,7 +1017,7 @@ See [`test/rpc-example.ts`](../test/rpc-example.ts) for a complete interactive e
 const { spawn } = require("child_process");
 const readline = require("readline");
 
-const agent = spawn("pi", ["--mode", "rpc", "--no-session"]);
+const agent = spawn("omp", ["--mode", "rpc", "--no-session"]);
 
 readline.createInterface({ input: agent.stdout }).on("line", (line) => {
 	const event = JSON.parse(line);

package/docs/sdk.md

@@ -1,8 +1,8 @@
-> pi can help you use the SDK. Ask it to build an integration for your use case.
+> omp can help you use the SDK. Ask it to build an integration for your use case.
 
 # SDK
 
-The SDK provides programmatic access to pi's agent capabilities. Use it to embed pi in other applications, build custom interfaces, or integrate with automated workflows.
+The SDK provides programmatic access to omp's agent capabilities. Use it to embed omp in other applications, build custom interfaces, or integrate with automated workflows.
 
 **Example use cases:**
 
@@ -60,7 +60,7 @@ The main factory function. Creates an `AgentSession` with configurable options.
 ```typescript
 import { createAgentSession } from "@oh-my-pi/pi-coding-agent";
 
-// Minimal: all defaults (discovers everything from cwd and ~/.pi/agent)
+// Minimal: all defaults (discovers everything from cwd and ~/.omp/agent)
 const { session } = await createAgentSession();
 
 // Custom: override specific options
@@ -220,16 +220,16 @@ const { session } = await createAgentSession({
 	cwd: process.cwd(), // default
 
 	// Global config directory
-	agentDir: "~/.pi/agent", // default (expands ~)
+	agentDir: "~/.omp/agent", // default (expands ~)
 });
 ```
 
 `cwd` is used for:
 
-- Project hooks (`.pi/hooks/`)
-- Project tools (`.pi/tools/`)
-- Project skills (`.pi/skills/`)
-- Project commands (`.pi/commands/`)
+- Project hooks (`.omp/hooks/`)
+- Project tools (`.omp/tools/`)
+- Project skills (`.omp/skills/`)
+- Project commands (`.omp/commands/`)
 - Context files (`AGENTS.md` walking up from cwd)
 - Session directory naming
 
@@ -300,7 +300,7 @@ API key resolution priority (handled by AuthStorage):
 ```typescript
 import { AuthStorage, ModelRegistry, discoverAuthStorage, discoverModels } from "@oh-my-pi/pi-coding-agent";
 
-// Default: uses ~/.pi/agent/auth.json and ~/.pi/agent/models.json
+// Default: uses ~/.omp/agent/auth.json and ~/.omp/agent/models.json
 const authStorage = discoverAuthStorage();
 const modelRegistry = discoverModels(authStorage);
 
@@ -721,8 +721,8 @@ const { session } = await createAgentSession({
 
 Settings load from two locations and merge:
 
-1. Global: `~/.pi/agent/settings.json`
-2. Project: `<cwd>/.pi/settings.json`
+1. Global: `~/.omp/agent/settings.json`
+2. Project: `<cwd>/.omp/settings.json`
 
 Project overrides global. Nested objects merge keys. Setters only modify global (project is read-only for version control).
 
@@ -749,8 +749,8 @@ import {
 } from "@oh-my-pi/pi-coding-agent";
 
 // Auth and Models
-const authStorage = discoverAuthStorage(); // ~/.pi/agent/auth.json
-const modelRegistry = discoverModels(authStorage); // + ~/.pi/agent/models.json
+const authStorage = discoverAuthStorage(); // ~/.omp/agent/auth.json
+const modelRegistry = discoverModels(authStorage); // + ~/.omp/agent/models.json
 const allModels = modelRegistry.getAll(); // All models (built-in + custom)
 const available = await modelRegistry.getAvailable(); // Only models with API keys
 const model = modelRegistry.find("provider", "id"); // Find specific model
@@ -896,7 +896,7 @@ await session.prompt("Get status and list files.");
 For subprocess-based integration, use RPC mode instead of the SDK:
 
 ```bash
-pi --mode rpc --no-session
+omp --mode rpc --no-session
 ```
 
 See [RPC documentation](rpc.md) for the JSON protocol.

package/docs/session-tree-plan.md

@@ -87,7 +87,7 @@ export interface BranchSummaryEntry extends SessionEntryBase {
 ```
 
 - [x] `fromId` field references the abandoned leaf
-- [x] `fromHook` field distinguishes pi-generated vs hook-generated summaries
+- [x] `fromHook` field distinguishes omp-generated vs hook-generated summaries
 - [x] `details` field for file tracking
 - [x] Branch summarizer implemented with structured output format
 - [x] Uses serialization approach (same as compaction) to prevent model confusion

package/docs/session.md

@@ -5,7 +5,7 @@ Sessions are stored as JSONL (JSON Lines) files. Each line is a JSON object with
 ## File Location
 
 ```
-~/.pi/agent/sessions/--<path>--/<timestamp>_<uuid>.jsonl
+~/.omp/agent/sessions/--<path>--/<timestamp>_<uuid>.jsonl
 ```
 
 Where `<path>` is the working directory with `/` replaced by `-`.
@@ -90,7 +90,7 @@ Created when context is compacted. Stores a summary of earlier messages.
 
 Optional fields:
 - `details`: Compaction-implementation specific data (e.g., file operations for default implementation, or custom data for custom hook implementations)
-- `fromHook`: `true` if generated by a hook, `false`/`undefined` if pi-generated
+- `fromHook`: `true` if generated by a hook, `false`/`undefined` if omp-generated
 
 ### BranchSummaryEntry