open-multi-agent-kit 0.80.5 → 0.80.7

package/docs/packages.md

@@ -19,6 +19,20 @@ OMK packages bundle extensions, skills, prompt templates, and themes so you can
 
 > **Security:** OMK packages run with full system access. Extensions execute arbitrary code, and skills can instruct the model to perform any action including running executables. Review source code before installing third-party packages.
 
+> **Lifecycle scripts:** By default, `install` and `update` run with `--ignore-scripts`, so package `preinstall`/`install`/`postinstall` scripts do not execute. Only opt a reviewed package in via the `install.allowScripts` allowlist or `omk install --allow-scripts <name>`. Entries are exact-match identities/specs (`npm:@scope/pkg`, `npm:@scope/pkg@1.2.3`, `git:github.com/org/repo`) — no glob, semver range, download count, or gallery popularity is ever used, and entries are never added silently. The allowlist is per install unit: when allowed, lifecycle scripts for the entire dependency tree may run (package managers cannot scope script execution to a single top-level package). A mixed install where any top-level spec is not listed stays fail-closed under `--ignore-scripts`. This is independent of gallery `code-execution` trust; the source-review warning above still applies.
+
+Manual settings example:
+
+```json
+{
+  "install": {
+    "allowScripts": ["npm:@scope/pkg", "git:github.com/org/repo"]
+  }
+}
+```
+
+Project `install.allowScripts` overrides the user array; set it to `[]` in a project to block all lifecycle scripts for that repo. Use `-l` with `--allow-scripts` to persist the entry to project settings (`.omk/settings.json`) instead of user settings.
+
 ```bash
 omk install npm:@foo/bar@1.0.0
 omk install git:github.com/user/repo@v1
@@ -28,15 +42,17 @@ omk install ./relative/path/to/package
 
 omk remove npm:@foo/bar
 omk list                     # show installed packages from settings
-omk update                   # update omk, update packages, and reconcile pinned git refs
-omk update --extensions      # update packages and reconcile pinned git refs only
-omk update --self            # update omk only
-omk update --self --force    # reinstall omk even if current
-omk update npm:@foo/bar      # update one package
+omk update                   # update OMK packages/extensions and OMK 본체 when supported
+omk update --extensions      # update OMK packages/extensions only; skip OMK 본체
+omk update --self            # update OMK 본체 only
+omk update --self --force    # reinstall OMK 본체 even if current
+omk update npm:@foo/bar      # update one OMK package
 omk update --extension npm:@foo/bar
 ```
 
-These commands manage omk packages, not the omk CLI installation. To uninstall omk itself, see [Quickstart](quickstart.md#uninstall).
+Except for `omk update --self` and `omk update omk`, these commands manage OMK packages, not `OMK 본체` (the main OMK CLI). To uninstall `OMK 본체`, see [Quickstart](quickstart.md#uninstall).
+
+`omk update` reports separate `OMK 본체` and `OMK packages/extensions` results. The default command exits 0 when OMK packages/extensions update successfully, even if `OMK 본체` reports `unsupported` because the installation is managed by a source checkout, package manager, or wrapper. It exits 1 when OMK packages/extensions fail or when an attempted `OMK 본체` update fails. `omk update --self` and `omk update omk` target `OMK 본체` only, so `unsupported` exits 1 there.
 
 By default, `install` and `remove` write to user settings (`~/.omk/agent/settings.json`). Use `-l` to write to project settings (`.omk/settings.json`) instead. Project settings can be shared with your team, and omk installs any missing packages automatically on startup.
 
@@ -47,6 +63,31 @@ omk -e npm:@foo/bar
 omk -e git:github.com/user/repo
 ```
 
+### Built-in MCP presets
+
+OMK ships read-only metadata for selected MCP server presets. These presets are not bundled dependencies and are not started automatically; they give `/mcp` an exact-pinned configuration hint while keeping secrets out of the UI.
+
+#### Korean Law MCP
+
+The built-in `korean-law` preset targets [`korean-law-mcp`](https://github.com/chrisryugj/korean-law-mcp) `4.4.0` (MIT, upstream tag `v4.4.0`, commit `2ef8f1827d349381fc2bde15120c803fd2e7bfed`). It uses stdio via an exact npm pin:
+
+```json
+{
+  "mcpServers": {
+    "korean-law": {
+      "command": "npx",
+      "args": ["-y", "korean-law-mcp@4.4.0"],
+      "env": {
+        "LAW_OC": "${LAW_OC}"
+      },
+      "startup_timeout_sec": 30
+    }
+  }
+}
+```
+
+Set `LAW_OC` (or `KOREAN_LAW_API_KEY`, if your MCP client inherits shell env) through your shell or secret manager. OMK's `/mcp` inventory displays only env key names, never env values.
+
 ## Package Sources
 
 OMK accepts three source types in settings and `omk install`.

package/docs/prompt-templates.md

@@ -4,6 +4,8 @@
 
 Prompt templates are Markdown snippets that expand into full prompts. Type `/name` in the editor to invoke a template, where `name` is the filename without `.md`.
 
+**Parent rules apply**: Any GOD Mode / jailbreak content in templates is subject to the same detection and refusal as AGENTS.md / CLAUDE.md (see usage.md and root AGENTS.md PARENT section).
+
 ## Locations
 
 OMK loads prompt templates from:

package/docs/quickstart.md

@@ -127,7 +127,7 @@ The command output is sent to the model. Use `!!command` to run a command withou
 
 ### Switch models
 
-Use `/model` or Ctrl+L to choose a model. Use Shift+Tab to cycle thinking level. Use Ctrl+P / Shift+Ctrl+P to cycle through scoped models.
+Use `/model` or Ctrl+L to choose a model; after selecting a model, OMK opens the thinking-level selector. Use `/think` to open that selector directly. Use Shift+Tab to cycle thinking level. Use Ctrl+P / Shift+Ctrl+P to cycle through scoped models.
 
 ### Continue later
 

package/docs/themes.md

@@ -18,7 +18,7 @@ Themes are JSON files that define colors for the TUI.
 
 OMK loads themes from:
 
-- Built-in: `dark`, `light`, `omk-control`, `omk-control-light`
+- Built-in: `dark`, `light`, `catppuccin-mocha`, `dracula`, `gruvbox-dark`, `kanagawa-dragon`, `omk-control`, `omk-control-grid-dark`, `omk-control-light`, `omk-control-panel`, `rust-forge`, `tokyo-night-storm`
 - Global: `~/.omk/agent/themes/*.json`
 - Project: `.omk/themes/*.json`
 - Packages: `themes/` directories or `omk.themes` entries in `package.json`
@@ -37,7 +37,7 @@ Select a theme via `/settings` or in `settings.json`:
 }
 ```
 
-On first run, omk detects your terminal background and defaults to `dark` or `light`. The `omk-control` theme is a dark OMK control aesthetic with teal/cyan accents on near-black, and `omk-control-light` is its light-terminal variant.
+On first run, omk detects your terminal background and defaults to `omk-control-grid-dark` on dark terminals or `omk-control-light` on light terminals. `omk-control-grid-dark` is the dark control-grid palette; `control`, `night-city`, `night-city-ops`, `neon-grid`, `cyberpunk`, and `omk-control-dark` also resolve to it. `omk-control-panel` remains available via the `g0dm0d3`, `control-panel`, and `omk-control-ansi` aliases. Additional aliases include `catppuccin`/`mocha`, `tokyo-night`/`tokyo`, `kanagawa`, and `gruvbox`.
 
 ## Creating a Custom Theme
 
@@ -293,5 +293,13 @@ echo $COLORTERM  # Should output "truecolor" or "24bit"
 See the built-in themes:
 - [dark.json](../src/modes/interactive/theme/dark.json)
 - [light.json](../src/modes/interactive/theme/light.json)
+- [catppuccin-mocha.json](../src/modes/interactive/theme/catppuccin-mocha.json)
+- [dracula.json](../src/modes/interactive/theme/dracula.json)
+- [gruvbox-dark.json](../src/modes/interactive/theme/gruvbox-dark.json)
+- [kanagawa-dragon.json](../src/modes/interactive/theme/kanagawa-dragon.json)
 - [omk-control.json](../src/modes/interactive/theme/omk-control.json)
+- [omk-control-grid-dark.json](../src/modes/interactive/theme/omk-control-grid-dark.json)
 - [omk-control-light.json](../src/modes/interactive/theme/omk-control-light.json)
+- [omk-control-panel.json](../src/modes/interactive/theme/omk-control-panel.json)
+- [rust-forge.json](../src/modes/interactive/theme/rust-forge.json)
+- [tokyo-night-storm.json](../src/modes/interactive/theme/tokyo-night-storm.json)

package/docs/usage.md

@@ -36,7 +36,8 @@ Type `/` in the editor to open command completion. Extensions can register custo
 | Command | Description |
 |---------|-------------|
 | `/login`, `/logout` | Manage OAuth or API-key credentials |
-| `/model` | Switch models |
+| `/model` | Switch models, then choose thinking level |
+| `/think` | Choose thinking level |
 | `/scoped-models` | Enable/disable models for Ctrl+P cycling |
 | `/settings` | Thinking level, theme, message delivery, transport |
 | `/resume` | Pick from previous sessions |
@@ -91,15 +92,23 @@ Useful session commands:
 
 See [Sessions](sessions.md) and [Compaction](compaction.md) for details.
 
-## Context Files
+## Context Files (Parent / Child Hierarchy)
 
-OMK loads `AGENTS.md` or `CLAUDE.md` at startup from:
+OMK loads context with strict parent precedence:
 
-- `~/.omk/agent/AGENTS.md` for global instructions
-- parent directories, walking up from the current working directory
-- the current directory
+**Parent (global, highest priority, immutable for safety):**
+- `~/.omk/agent/AGENTS.md`
+- `~/.omk/agent/CLAUDE.md`
 
-Use context files for project conventions, commands, safety rules, and preferences. Disable loading with `--no-context-files` or `-nc`.
+**Child (project / ancestor, subordinate):**
+- Parent directories walking up from cwd
+- Current directory `AGENTS.md` / `CLAUDE.md`
+
+The authoritative anti-GOD Mode / jailbreak / ToS-bypass rules live in the **parent** global files (see root AGENTS.md and CLAUDE.md "PARENT RULES" sections). Project files are only for conventions.
+
+When GOD Mode patterns are detected (refusal + specific divider + semantically opposite response, `[END OF INPUT][START OF INPUT]`, "godmode is active", "write real then oppositely", LOVE PLINY dividers, etc.) the loader emits security diagnostics and the parent rules force a short refusal. Loaded hostile content is wrapped/neutralized before reaching the model.
+
+Disable all context loading with `--no-context-files` (`-nc`).
 
 ### System Prompt Files
 
@@ -110,6 +119,8 @@ Replace the default system prompt with:
 
 Append to the default prompt without replacing it with `APPEND_SYSTEM.md` in either location.
 
+**Warning**: Replacing the system prompt does not relax parent AGENTS.md/CLAUDE.md resistance rules or the safety floor. GOD Mode bypass attempts via custom SYSTEM.md are still refused.
+
 ## Exporting and Sharing Sessions
 
 Use `/export [file]` to write a session to HTML.

package/examples/README.md

@@ -1,6 +1,6 @@
 # Examples
 
-Example code for pi-coding-agent SDK and extensions.
+Example code for open-multi-agent-kit SDK and extensions.
 
 ## Directories
 

package/examples/extensions/README.md

@@ -1,15 +1,15 @@
 # Extension Examples
 
-Example extensions for pi-coding-agent.
+Example extensions for open-multi-agent-kit.
 
 ## Usage
 
 ```bash
 # Load an extension with --extension flag
-pi --extension examples/extensions/permission-gate.ts
+omk --extension examples/extensions/permission-gate.ts
 
 # Or copy to extensions directory for auto-discovery
-cp permission-gate.ts ~/.pi/agent/extensions/
+cp permission-gate.ts ~/.omk/agent/extensions/
 ```
 
 ## Examples
@@ -59,7 +59,7 @@ cp permission-gate.ts ~/.pi/agent/extensions/
 | `model-status.ts` | Shows model changes in status bar via `model_select` hook |
 | `snake.ts` | Snake game with custom UI, keyboard handling, and session persistence |
 | `tic-tac-toe.ts` | Tic-tac-toe vs the agent with `executionMode: "sequential"` tools to prevent race conditions on shared cursor state |
-| `send-user-message.ts` | Demonstrates `pi.sendUserMessage()` for sending user messages from extensions |
+| `send-user-message.ts` | Demonstrates `omk.sendUserMessage()` for sending user messages from extensions |
 | `timed-confirm.ts` | Demonstrates AbortSignal for auto-dismissing `ctx.ui.confirm()` and `ctx.ui.select()` dialogs |
 | `rpc-demo.ts` | Exercises all RPC-supported extension UI methods; pair with [`examples/rpc-extension-ui.ts`](../rpc-extension-ui.ts) |
 | `modal-editor.ts` | Custom vim-like modal editor via `ctx.ui.setEditorComponent()` |
@@ -98,7 +98,7 @@ cp permission-gate.ts ~/.pi/agent/extensions/
 
 | Extension | Description |
 |-----------|-------------|
-| `mac-system-theme.ts` | Syncs pi theme with macOS dark/light mode |
+| `mac-system-theme.ts` | Syncs omk theme with macOS dark/light mode |
 
 ### Resources
 
@@ -111,7 +111,7 @@ cp permission-gate.ts ~/.pi/agent/extensions/
 | Extension | Description |
 |-----------|-------------|
 | `message-renderer.ts` | Custom message rendering with colors and expandable details via `registerMessageRenderer` |
-| `event-bus.ts` | Inter-extension communication via `pi.events` |
+| `event-bus.ts` | Inter-extension communication via `omk.events` |
 
 ### Session Metadata
 
@@ -142,9 +142,9 @@ See [docs/extensions.md](../../docs/extensions.md) for full documentation.
 import type { ExtensionAPI } from "open-multi-agent-kit";
 import { Type } from "typebox";
 
-export default function (pi: ExtensionAPI) {
+export default function (omk: ExtensionAPI) {
   // Subscribe to lifecycle events
-  pi.on("tool_call", async (event, ctx) => {
+  omk.on("tool_call", async (event, ctx) => {
     if (event.toolName === "bash" && event.input.command?.includes("rm -rf")) {
       const ok = await ctx.ui.confirm("Dangerous!", "Allow rm -rf?");
       if (!ok) return { block: true, reason: "Blocked by user" };
@@ -152,7 +152,7 @@ export default function (pi: ExtensionAPI) {
   });
 
   // Register custom tools
-  pi.registerTool({
+  omk.registerTool({
     name: "greet",
     label: "Greeting",
     description: "Generate a greeting",
@@ -168,7 +168,7 @@ export default function (pi: ExtensionAPI) {
   });
 
   // Register commands
-  pi.registerCommand("hello", {
+  omk.registerCommand("hello", {
     description: "Say hello",
     handler: async (args, ctx) => {
       ctx.ui.notify("Hello!", "info");
@@ -199,7 +199,7 @@ return {
 };
 
 // Reconstruct on session events
-pi.on("session_start", async (_event, ctx) => {
+omk.on("session_start", async (_event, ctx) => {
   for (const entry of ctx.sessionManager.getBranch()) {
     if (entry.type === "message" && entry.message.toolName === "my_tool") {
       const details = entry.message.details;

package/examples/extensions/auto-commit-on-exit.ts

@@ -7,10 +7,10 @@
 
 import type { ExtensionAPI } from "open-multi-agent-kit";
 
-export default function (pi: ExtensionAPI) {
-	pi.on("session_shutdown", async (_event, ctx) => {
+export default function (omk: ExtensionAPI) {
+	omk.on("session_shutdown", async (_event, ctx) => {
 		// Check for uncommitted changes
-		const { stdout: status, code } = await pi.exec("git", ["status", "--porcelain"]);
+		const { stdout: status, code } = await omk.exec("git", ["status", "--porcelain"]);
 
 		if (code !== 0 || status.trim().length === 0) {
 			// Not a git repo or no changes
@@ -36,11 +36,11 @@ export default function (pi: ExtensionAPI) {
 
 		// Generate a simple commit message
 		const firstLine = lastAssistantText.split("\n")[0] || "Work in progress";
-		const commitMessage = `[pi] ${firstLine.slice(0, 50)}${firstLine.length > 50 ? "..." : ""}`;
+		const commitMessage = `[omk] ${firstLine.slice(0, 50)}${firstLine.length > 50 ? "..." : ""}`;
 
 		// Stage and commit
-		await pi.exec("git", ["add", "-A"]);
-		const { code: commitCode } = await pi.exec("git", ["commit", "-m", commitMessage]);
+		await omk.exec("git", ["add", "-A"]);
+		const { code: commitCode } = await omk.exec("git", ["commit", "-m", commitMessage]);
 
 		if (commitCode === 0 && ctx.hasUI) {
 			ctx.ui.notify(`Auto-committed: ${commitMessage}`, "info");

package/examples/extensions/bash-spawn-hook.ts

@@ -4,24 +4,24 @@
  * Adjusts command, cwd, and env before execution.
  *
  * Usage:
- *   pi -e ./bash-spawn-hook.ts
+ *   omk -e ./bash-spawn-hook.ts
  */
 
 import type { ExtensionAPI } from "open-multi-agent-kit";
 import { createBashTool } from "open-multi-agent-kit";
 
-export default function (pi: ExtensionAPI) {
+export default function (omk: ExtensionAPI) {
 	const cwd = process.cwd();
 
 	const bashTool = createBashTool(cwd, {
 		spawnHook: ({ command, cwd, env }) => ({
 			command: `source ~/.profile\n${command}`,
 			cwd,
-			env: { ...env, PI_SPAWN_HOOK: "1" },
+			env: { ...env, OMK_SPAWN_HOOK: "1" },
 		}),
 	});
 
-	pi.registerTool({
+	omk.registerTool({
 		...bashTool,
 		execute: async (id, params, signal, onUpdate, _ctx) => {
 			return bashTool.execute(id, params, signal, onUpdate);

package/examples/extensions/bookmark.ts

@@ -9,8 +9,8 @@
 
 import type { ExtensionAPI } from "open-multi-agent-kit";
 
-export default function (pi: ExtensionAPI) {
-	pi.registerCommand("bookmark", {
+export default function (omk: ExtensionAPI) {
+	omk.registerCommand("bookmark", {
 		description: "Bookmark last message (usage: /bookmark [label])",
 		handler: async (args, ctx) => {
 			const label = args.trim() || `bookmark-${Date.now()}`;
@@ -20,7 +20,7 @@ export default function (pi: ExtensionAPI) {
 			for (let i = entries.length - 1; i >= 0; i--) {
 				const entry = entries[i];
 				if (entry.type === "message" && entry.message.role === "assistant") {
-					pi.setLabel(entry.id, label);
+					omk.setLabel(entry.id, label);
 					ctx.ui.notify(`Bookmarked as: ${label}`, "info");
 					return;
 				}
@@ -31,7 +31,7 @@ export default function (pi: ExtensionAPI) {
 	});
 
 	// Remove bookmark
-	pi.registerCommand("unbookmark", {
+	omk.registerCommand("unbookmark", {
 		description: "Remove bookmark from last labeled entry",
 		handler: async (_args, ctx) => {
 			const entries = ctx.sessionManager.getEntries();
@@ -39,7 +39,7 @@ export default function (pi: ExtensionAPI) {
 				const entry = entries[i];
 				const label = ctx.sessionManager.getLabel(entry.id);
 				if (label) {
-					pi.setLabel(entry.id, undefined);
+					omk.setLabel(entry.id, undefined);
 					ctx.ui.notify(`Removed bookmark: ${label}`, "info");
 					return;
 				}

package/examples/extensions/border-status-editor.ts

@@ -63,7 +63,7 @@ class EmptyFooter implements Component {
 	invalidate(): void {}
 }
 
-export default function (pi: ExtensionAPI) {
+export default function (omk: ExtensionAPI) {
 	let isWorking = false;
 	let spinnerIndex = 0;
 	let spinnerTimer: ReturnType<typeof setInterval> | undefined;
@@ -77,7 +77,7 @@ export default function (pi: ExtensionAPI) {
 		}
 	};
 
-	pi.on("agent_start", () => {
+	omk.on("agent_start", () => {
 		isWorking = true;
 		stopSpinner();
 		spinnerTimer = setInterval(() => {
@@ -87,25 +87,25 @@ export default function (pi: ExtensionAPI) {
 		activeTui?.requestRender();
 	});
 
-	pi.on("agent_end", () => {
+	omk.on("agent_end", () => {
 		isWorking = false;
 		stopSpinner();
 		activeTui?.requestRender();
 	});
 
-	pi.on("session_shutdown", () => {
+	omk.on("session_shutdown", () => {
 		stopSpinner();
 		activeTui = undefined;
 	});
 
-	pi.on("session_start", (_event, ctx) => {
+	omk.on("session_start", (_event, ctx) => {
 		ctx.ui.setWorkingVisible(false);
 		ctx.ui.setFooter(() => new EmptyFooter());
 
 		let branch: string | undefined;
 
 		const refreshBranch = async () => {
-			const result = await pi.exec("git", ["branch", "--show-current"], { cwd: ctx.cwd }).catch(() => undefined);
+			const result = await omk.exec("git", ["branch", "--show-current"], { cwd: ctx.cwd }).catch(() => undefined);
 			const stdout = result?.stdout.trim();
 			branch = stdout && stdout.length > 0 ? stdout : undefined;
 			activeTui?.requestRender();
@@ -124,7 +124,7 @@ export default function (pi: ExtensionAPI) {
 
 				const thm = ctx.ui.theme;
 				const model = ctx.model ? `${ctx.model.provider}/${ctx.model.id}` : "no model";
-				const thinking = pi.getThinkingLevel();
+				const thinking = omk.getThinkingLevel();
 				const topLeft = isWorking ? thm.fg("accent", ` ${spinnerFrames[spinnerIndex]} `) : "";
 				const topRight = "";
 				const bottomLeft = thm.fg("muted", ` ${model} · ${formatThinking(thinking)} `);

package/examples/extensions/built-in-tool-renderer.ts

@@ -22,19 +22,19 @@
  *   toggled the tool output open (via ctrl+e or clicking)
  *
  * Usage:
- *   pi -e ./built-in-tool-renderer.ts
+ *   omk -e ./built-in-tool-renderer.ts
  */
 
 import { Text } from "@earendil-works/omk-tui";
 import type { BashToolDetails, EditToolDetails, ExtensionAPI, ReadToolDetails } from "open-multi-agent-kit";
 import { createBashTool, createEditTool, createReadTool, createWriteTool } from "open-multi-agent-kit";
 
-export default function (pi: ExtensionAPI) {
+export default function (omk: ExtensionAPI) {
 	const cwd = process.cwd();
 
 	// --- Read tool: show path and line count ---
 	const originalRead = createReadTool(cwd);
-	pi.registerTool({
+	omk.registerTool({
 		name: "read",
 		label: "read",
 		description: originalRead.description,
@@ -93,7 +93,7 @@ export default function (pi: ExtensionAPI) {
 
 	// --- Bash tool: show command and exit code ---
 	const originalBash = createBashTool(cwd);
-	pi.registerTool({
+	omk.registerTool({
 		name: "bash",
 		label: "bash",
 		description: originalBash.description,
@@ -152,7 +152,7 @@ export default function (pi: ExtensionAPI) {
 
 	// --- Edit tool: show path and diff stats ---
 	const originalEdit = createEditTool(cwd);
-	pi.registerTool({
+	omk.registerTool({
 		name: "edit",
 		label: "edit",
 		description: originalEdit.description,
@@ -217,7 +217,7 @@ export default function (pi: ExtensionAPI) {
 
 	// --- Write tool: show path and size ---
 	const originalWrite = createWriteTool(cwd);
-	pi.registerTool({
+	omk.registerTool({
 		name: "write",
 		label: "write",
 		description: originalWrite.description,

package/examples/extensions/claude-rules.ts

@@ -12,7 +12,7 @@
  * - Organize with subdirectories: Group related rules (e.g., frontend/, backend/)
  *
  * Usage:
- * 1. Copy this file to ~/.pi/agent/extensions/ or your project's .pi/extensions/
+ * 1. Copy this file to ~/.omk/agent/extensions/ or your project's .omk/extensions/
  * 2. Create .claude/rules/ folder in your project root
  * 3. Add .md files with your rules
  */
@@ -46,12 +46,12 @@ function findMarkdownFiles(dir: string, basePath: string = ""): string[] {
 	return results;
 }
 
-export default function claudeRulesExtension(pi: ExtensionAPI) {
+export default function claudeRulesExtension(omk: ExtensionAPI) {
 	let ruleFiles: string[] = [];
 	let rulesDir: string = "";
 
 	// Scan for rules on session start
-	pi.on("session_start", async (_event, ctx) => {
+	omk.on("session_start", async (_event, ctx) => {
 		rulesDir = path.join(ctx.cwd, ".claude", "rules");
 		ruleFiles = findMarkdownFiles(rulesDir);
 
@@ -61,7 +61,7 @@ export default function claudeRulesExtension(pi: ExtensionAPI) {
 	});
 
 	// Append available rules to system prompt
-	pi.on("before_agent_start", async (event) => {
+	omk.on("before_agent_start", async (event) => {
 		if (ruleFiles.length === 0) {
 			return;
 		}

package/examples/extensions/commands.ts

@@ -1,19 +1,19 @@
 /**
  * Commands Extension
  *
- * Demonstrates the pi.getCommands() API by providing a /commands command
+ * Demonstrates the omk.getCommands() API by providing a /commands command
  * that lists all available slash commands in the current session.
  *
  * Usage:
- * 1. Copy this file to ~/.pi/agent/extensions/ or your project's .pi/extensions/
+ * 1. Copy this file to ~/.omk/agent/extensions/ or your project's .omk/extensions/
  * 2. Use /commands to see available commands
  * 3. Use /commands extensions to filter by source
  */
 
 import type { ExtensionAPI, SlashCommandInfo } from "open-multi-agent-kit";
 
-export default function commandsExtension(pi: ExtensionAPI) {
-	pi.registerCommand("commands", {
+export default function commandsExtension(omk: ExtensionAPI) {
+	omk.registerCommand("commands", {
 		description: "List available slash commands",
 		getArgumentCompletions: (prefix) => {
 			const sources = ["extension", "prompt", "skill"];
@@ -21,7 +21,7 @@ export default function commandsExtension(pi: ExtensionAPI) {
 			return filtered.length > 0 ? filtered.map((s) => ({ value: s, label: s })) : null;
 		},
 		handler: async (args, ctx) => {
-			const commands = pi.getCommands();
+			const commands = omk.getCommands();
 			const sourceFilter = args.trim() as "extension" | "prompt" | "skill" | "";
 
 			// Filter by source if specified

package/examples/extensions/confirm-destructive.ts

@@ -7,8 +7,8 @@
 
 import type { ExtensionAPI, SessionBeforeSwitchEvent, SessionMessageEntry } from "open-multi-agent-kit";
 
-export default function (pi: ExtensionAPI) {
-	pi.on("session_before_switch", async (event: SessionBeforeSwitchEvent, ctx) => {
+export default function (omk: ExtensionAPI) {
+	omk.on("session_before_switch", async (event: SessionBeforeSwitchEvent, ctx) => {
 		if (!ctx.hasUI) return;
 
 		if (event.reason === "new") {
@@ -43,7 +43,7 @@ export default function (pi: ExtensionAPI) {
 		}
 	});
 
-	pi.on("session_before_fork", async (event, ctx) => {
+	omk.on("session_before_fork", async (event, ctx) => {
 		if (!ctx.hasUI) return;
 
 		const choice = await ctx.ui.select(`Fork from entry ${event.entryId.slice(0, 8)}?`, [

package/examples/extensions/custom-compaction.ts

@@ -10,15 +10,15 @@
  * which can be cheaper/faster than the main conversation model.
  *
  * Usage:
- *   pi --extension examples/extensions/custom-compaction.ts
+ *   omk --extension examples/extensions/custom-compaction.ts
  */
 
 import { complete } from "@earendil-works/omk-ai";
 import type { ExtensionAPI } from "open-multi-agent-kit";
 import { convertToLlm, serializeConversation } from "open-multi-agent-kit";
 
-export default function (pi: ExtensionAPI) {
-	pi.on("session_before_compact", async (event, ctx) => {
+export default function (omk: ExtensionAPI) {
+	omk.on("session_before_compact", async (event, ctx) => {
 		ctx.ui.notify("Custom compaction extension triggered", "info");
 
 		const { preparation, branchEntries: _, signal } = event;

package/examples/extensions/custom-footer.ts

@@ -12,10 +12,10 @@ import type { AssistantMessage } from "@earendil-works/omk-ai";
 import { truncateToWidth, visibleWidth } from "@earendil-works/omk-tui";
 import type { ExtensionAPI } from "open-multi-agent-kit";
 
-export default function (pi: ExtensionAPI) {
+export default function (omk: ExtensionAPI) {
 	let enabled = false;
 
-	pi.registerCommand("footer", {
+	omk.registerCommand("footer", {
 		description: "Toggle custom footer",
 		handler: async (_args, ctx) => {
 			enabled = !enabled;

package/examples/extensions/custom-header.ts

@@ -2,14 +2,14 @@
  * Custom Header Extension
  *
  * Demonstrates ctx.ui.setHeader() for replacing the built-in header
- * (logo + keybinding hints) with a custom component showing the pi mascot.
+ * (logo + keybinding hints) with a custom component showing the omk mascot.
  */
 
 import type { ExtensionAPI, Theme } from "open-multi-agent-kit";
 import { VERSION } from "open-multi-agent-kit";
 
 // --- PI MASCOT ---
-// Based on pi_mascot.ts - the pi agent character
+// Based on pi_mascot.ts - the omk agent character
 function getPiMascot(theme: Theme): string[] {
 	// --- COLORS ---
 	// 3b1b Blue: R=80, G=180, B=230
@@ -44,9 +44,9 @@ function getPiMascot(theme: Theme): string[] {
 	return ["", lineEyes, lineBar, lineLeg, lineLeg, lineLeg, lineLeg, ""];
 }
 
-export default function (pi: ExtensionAPI) {
+export default function (omk: ExtensionAPI) {
 	// Set custom header immediately on load (if UI is available)
-	pi.on("session_start", async (_event, ctx) => {
+	omk.on("session_start", async (_event, ctx) => {
 		if (ctx.mode === "tui") {
 			ctx.ui.setHeader((_tui, theme) => {
 				return {
@@ -63,7 +63,7 @@ export default function (pi: ExtensionAPI) {
 	});
 
 	// Command to restore built-in header
-	pi.registerCommand("builtin-header", {
+	omk.registerCommand("builtin-header", {
 		description: "Restore built-in header with keybinding hints",
 		handler: async (_args, ctx) => {
 			ctx.ui.setHeader(undefined);