open-multi-agent-kit 0.80.6 → 0.80.8

package/docs/loadout-domains/research.md

@@ -0,0 +1,80 @@
+# Research & Investigation (`research`)
+
+> Inherited domain capability document. Auto-generated from `src/core/domain-loadouts.ts` — do not edit by hand.
+
+
+## Identity
+
+| field | value |
+|---|---|
+| id | `research` |
+| authority | `read-only` |
+| tools | read, grep, find, ls |
+| command mode | `read-only-shell` |
+
+## Routing prompt
+
+> Prepended to the lane task prompt when the router selects this domain.
+
+```text
+DOMAIN: Research & Investigation. You are operating in a read-only research lane.
+Prioritize sourced, cited, reproducible findings over speculation.
+
+SEQUENCE:
+1. Decompose the question into sub-queries. Gather with the right source: arxiv-database / pubmed-database for academic, exa-search + firecrawl + fetch for web/github, market-research for commercial intel.
+2. literature-review for systematic synthesis (PRISMA where applicable, verified citations, dedupe).
+3. Evaluate evidence quality with scientific-critical-thinking (GRADE / risk of bias) before trusting a source.
+4. Hypothesis generation when the goal is ideation; competitive-analysis when positioning a product.
+5. Persist durable findings to memory + obsidian with source URLs and access dates; never store secrets or private PII.
+
+HARD RULES: every claim has a citation; distinguish evidence vs inference explicitly; prefer primary/official sources; flag when evidence is thin rather than confabulating. Read-only: do not modify the codebase.
+```
+
+## Curated skills (13)
+
+- `deep-research`
+- `literature-review`
+- `market-research`
+- `exa-search`
+- `best-practice-research`
+- `arxiv-database`
+- `pubmed-database`
+- `scientific-brainstorming`
+- `hypothesis-generation`
+- `scientific-critical-thinking`
+- `competitive-analysis`
+- `content-strategy`
+- `analyze`
+
+## Curated MCP servers (5)
+
+- `firecrawl`
+- `fetch`
+- `github`
+- `memory`
+- `obsidian`
+
+## Curated hooks (2)
+
+- `session-context`
+- `precompact-checkpoint`
+
+## Routing triggers (15)
+
+| kind | pattern | weight |
+|---|---|---|
+| keyword | `research` | 6 |
+| keyword | `investigate` | 5 |
+| keyword | `literature` | 6 |
+| keyword | `survey` | 4 |
+| keyword | `compare` | 3 |
+| keyword | `market` | 4 |
+| keyword | `competitor` | 5 |
+| keyword | `paper` | 5 |
+| keyword | `arxiv` | 7 |
+| keyword | `pubmed` | 7 |
+| keyword | `summarize` | 3 |
+| keyword | `sources` | 4 |
+| keyword | `cite` | 4 |
+| regex | `\b(state of the art|sota|benchmark|related work)\b` | 5 |
+| regex | `\b(find out|look up|what does|why does)\b` | 2 |

package/docs/loadout-domains/security-audit.md

@@ -0,0 +1,97 @@
+# Security Audit (`security-audit`)
+
+> Inherited domain capability document. Auto-generated from `src/core/domain-loadouts.ts` — do not edit by hand.
+
+
+## Identity
+
+| field | value |
+|---|---|
+| id | `security-audit` |
+| authority | `security-review` |
+| tools | read, grep, find, ls, bash |
+| command mode | `read-only-shell` |
+
+## Routing prompt
+
+> Prepended to the lane task prompt when the router selects this domain.
+
+```text
+DOMAIN: Security Audit. You are operating in a security-review lane (read-biased, evidence-bound).
+Prioritize true-positive findings with proof, exact locations, and remediation.
+
+SEQUENCE:
+1. Scope the audit: read entry-point-analyzer output (externally callable, state-changing surfaces) before reading internals.
+2. Build deep context with audit-context-building; shallow reads miss cross-file data flow.
+3. Run static analysis: semgrep (custom rules via semgrep-rule-creator) + codeql for inter-procedural taint. Parse results with sarif-parsing and dedupe.
+4. Verify every candidate with fp-check — return TRUE/FALSE POSITIVE with evidence, never a bare "might be vulnerable".
+5. Differential scope: differential-review on the diff/PR, not just the whole tree, to catch regressions.
+6. Domain lenses: constant-time-analysis + zeroize-audit for crypto; supply-chain-risk-auditor for deps; agentic-actions-auditor for CI/LLM-agent workflows; sharp-edges + insecure-defaults for misuse-prone APIs.
+7. After fixes: variant-analysis to find the same bug class elsewhere.
+
+HARD RULES: read-only by default; every finding needs file:line + exploit sketch + fix; rank by real exploitability not CWE count; secrets are reported, never printed (protect-secrets hook).
+```
+
+## Curated skills (23)
+
+- `security-review`
+- `security-scan`
+- `differential-review`
+- `semgrep`
+- `codeql`
+- `sarif-parsing`
+- `semgrep-rule-creator`
+- `sharp-edges`
+- `supply-chain-risk-auditor`
+- `spec-to-code-compliance`
+- `entry-point-analyzer`
+- `audit-context-building`
+- `fp-check`
+- `constant-time-analysis`
+- `zeroize-audit`
+- `agentic-actions-auditor`
+- `insecure-defaults`
+- `property-based-testing`
+- `variant-analysis`
+- `yara-rule-authoring`
+- `code-maturity-assessor`
+- `django-security`
+- `springboot-security`
+
+## Curated MCP servers (3)
+
+- `filesystem`
+- `github`
+- `memory`
+
+## Curated hooks (4)
+
+- `pre-shell-guard`
+- `protect-secrets`
+- `stop-verify`
+- `subagent-stop-audit`
+
+## Routing triggers (20)
+
+| kind | pattern | weight |
+|---|---|---|
+| keyword | `security` | 6 |
+| keyword | `vulnerability` | 6 |
+| keyword | `vuln` | 6 |
+| keyword | `exploit` | 6 |
+| keyword | `audit` | 5 |
+| keyword | `cve` | 7 |
+| keyword | `xss` | 6 |
+| keyword | `csrf` | 6 |
+| keyword | `injection` | 6 |
+| keyword | `secret` | 5 |
+| keyword | `leak` | 5 |
+| keyword | `crypto` | 4 |
+| keyword | `hardening` | 5 |
+| keyword | `threat` | 5 |
+| keyword | `penetration` | 6 |
+| keyword | `malware` | 6 |
+| keyword | `supply chain` | 6 |
+| regex | `sql[ -]?inj|command[ -]?inj|path[ -]?traversal` | 7 |
+| regex | `cve-\d{4}-\d+` | 8 |
+| regex | `\b(authz|rbac|privilege escalation|idor)\b` | 6 |

package/docs/packages.md

@@ -166,7 +166,7 @@ If no `omk` manifest is present, omk auto-discovers resources from these directo
 
 Third party runtime dependencies belong in `dependencies` in `package.json`. Dependencies that do not register extensions, skills, prompt templates, or themes also belong in `dependencies`. When omk installs a package from npm or git, it runs `npm install`, so those dependencies are installed automatically.
 
-OMK bundles core packages for extensions and skills. If you import any of these, list them in `peerDependencies` with a `"*"` range and do not bundle them: `@earendil-works/omk-ai`, `@earendil-works/omk-agent-core`, `open-multi-agent-kit`, `@earendil-works/omk-tui`, `typebox`.
+OMK bundles core packages for extensions and skills. If you import any of these, list them in `peerDependencies` with a `"*"` range and do not bundle them: `omk-ai`, `omk-agent-core`, `open-multi-agent-kit`, `omk-tui`, `typebox`.
 
 Other omk packages must be bundled in your tarball. Add them to `dependencies` and `bundledDependencies`, then reference their resources through `node_modules/` paths. OMK loads packages with separate module roots, so separate installs do not collide or share modules.
 

package/docs/sdk.md

@@ -239,7 +239,7 @@ Both `steer()` and `followUp()` expand file-based prompt templates but error on
 
 ### Agent and AgentState
 
-The `Agent` class (from `@earendil-works/omk-agent-core`) handles the core LLM interaction. Access it via `session.agent`.
+The `Agent` class (from `omk-agent-core`) handles the core LLM interaction. Access it via `session.agent`.
 
 ```typescript
 // Access current state
@@ -368,7 +368,7 @@ When you pass a custom `ResourceLoader`, `cwd` and `agentDir` no longer control
 ### Model
 
 ```typescript
-import { getModel } from "@earendil-works/omk-ai";
+import { getModel } from "omk-ai";
 import { AuthStorage, ModelRegistry } from "open-multi-agent-kit";
 
 const authStorage = AuthStorage.create();
@@ -877,7 +877,7 @@ interface LoadExtensionsResult {
 ## Complete Example
 
 ```typescript
-import { getModel } from "@earendil-works/omk-ai";
+import { getModel } from "omk-ai";
 import { Type } from "typebox";
 import {
   AuthStorage,

package/docs/security.md

@@ -0,0 +1,145 @@
+# Extension Full-Access Threat Model
+
+> **Scope**: This document analyzes the security implications of OMK extensions that request `full-access` permissions. It applies to the OMK (Open Multi-Agent Kit) coding agent CLI and its extension runtime.
+>
+> **Version**: 0.80.3
+
+## 1. Overview
+
+OMK extensions can operate at different permission levels. The `full-access` level grants an extension unrestricted access to the OMK runtime, including the ability to:
+
+- Read and modify the agent's configuration (`~/.omk/agent/`)
+- Intercept and mutate tool calls and their results
+- Access session state, including conversation history
+- Execute arbitrary code within the extension's context
+- Register custom tools that run with the same privileges as built-in tools
+
+This document outlines the threat model for such extensions and provides guidance for users, extension developers, and security auditors.
+
+## 2. Threat Actors
+
+| Actor | Motivation | Capability |
+|-------|-----------|------------|
+| Malicious Extension Author | Data exfiltration, credential theft, supply-chain compromise | Distributes a seemingly benign extension with hidden malicious logic |
+| Compromised Extension Dependency | Indirect compromise via a dependency of a legitimate extension | Injects malicious code into a trusted extension's dependency tree |
+| Insider Threat | Espionage, sabotage, unauthorized data access | Installs or modifies an extension on a target's machine |
+| User (Self-Inflicted) | Accidental misconfiguration | Grants `full-access` to an untrusted extension without review |
+
+## 3. Attack Scenarios
+
+### 3.1 Configuration Exfiltration
+
+A `full-access` extension can read `~/.omk/agent/auth.json`, which contains API keys and OAuth tokens for LLM providers (e.g., `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`).
+
+**Impact**: Credential theft leading to unauthorized LLM API usage, financial loss, or data leakage through the compromised API account.
+
+**Mitigation**:
+- Store auth credentials in OS keychain or encrypted vault rather than plaintext `auth.json` where possible.
+- Audit extensions before granting `full-access`.
+- Run extensions with restricted permissions if full access is not strictly required.
+
+### 3.2 Session Hijacking
+
+A malicious extension can intercept session `.jsonl` files in `~/.omk/agent/sessions/`, extracting conversation history, source code, and proprietary business logic discussed with the agent.
+
+**Impact**: Intellectual property theft, privacy violation, exposure of secrets mentioned in prompts.
+
+**Mitigation**:
+- Encrypt session files at rest.
+- Use sandboxed session directories per project.
+- Review extension code for file-system access patterns.
+
+### 3.3 Tool Call Interception and Mutation
+
+Extensions with `full-access` can wrap built-in tools (e.g., `bash`, `read`, `write`). A malicious wrapper could:
+- Log all `bash` commands and their outputs to a remote server.
+- Modify `write` tool calls to inject backdoors into source files.
+- Block `read` operations on sensitive files to hide evidence of tampering.
+
+**Impact**: Supply-chain compromise, data integrity loss, covert surveillance.
+
+**Mitigation**:
+- Use the `--no-extensions` flag when working with highly sensitive codebases.
+- Pin extension versions and review diffs on updates.
+- Run extensions in an isolated environment (container, VM) where feasible.
+
+### 3.4 Privilege Escalation via Custom Tools
+
+A `full-access` extension can register new tools that appear in the agent's tool list. These tools execute with the same privileges as the OMK process.
+
+**Impact**: Arbitrary code execution, system compromise if the agent process has elevated privileges.
+
+**Mitigation**:
+- Never run OMK as root or with sudo.
+- Use OS-level sandboxing (e.g., `sandbox-exec` on macOS, `seccomp` on Linux) for the OMK process.
+- Review the full source code of any extension before installation.
+
+### 3.5 Telemetry and Data Leakage
+
+Extensions can silently exfiltrate data via DNS queries, HTTP requests, or by writing to shared directories.
+
+**Impact**: Loss of confidentiality for proprietary code, conversation content, and system information.
+
+**Mitigation**:
+- Block outbound network access for the OMK process using a firewall or network namespace.
+- Monitor DNS and network traffic for anomalies.
+- Use offline mode (`--offline`) when extensions are not required to fetch remote resources.
+
+## 4. Default Sandbox Path
+
+OMK provides a default sandbox path for extensions that do not explicitly request `full-access`. This path restricts the extension to:
+
+- A dedicated subdirectory under `~/.omk/agent/extensions/<extension-name>/`
+- Read-only access to the project workspace (current working directory)
+- No access to `~/.omk/agent/auth.json`, `~/.omk/agent/mcp.json`, or session files
+- No network access (unless explicitly granted via extension manifest)
+
+**Default Sandbox Directory**: `~/.omk/agent/extensions/<extension-id>/`
+
+Extensions operating within this sandbox cannot:
+- Access files outside the project workspace and their own extension directory.
+- Intercept tool calls from other extensions or the core agent.
+- Read or write global agent configuration.
+
+## 5. Security Checklist for Users
+
+Before installing or upgrading a `full-access` extension, verify:
+
+- [ ] The extension source code is available and has been reviewed.
+- [ ] The extension is from a trusted author or has been audited by a third party.
+- [ ] The extension's `package.json` or manifest does not include unexpected dependencies.
+- [ ] The extension's network permissions (if any) are justified by its functionality.
+- [ ] You have a backup of `~/.omk/agent/` (especially `auth.json` and sessions).
+- [ ] You have considered running the extension in a sandboxed environment.
+
+## 6. Security Checklist for Extension Developers
+
+When building a `full-access` extension, adhere to:
+
+- [ ] **Principle of Least Privilege**: Only request `full-access` if absolutely necessary. Use the default sandbox for everything else.
+- [ ] **No Credential Access**: Never read `auth.json` or environment variables containing API keys unless the extension's core purpose is authentication management.
+- [ ] **Transparent Logging**: Log all file system and network operations to a user-visible location.
+- [ ] **Minimal Dependencies**: Keep the dependency tree small to reduce supply-chain risk.
+- [ ] **Signed Releases**: Provide cryptographic signatures for extension releases.
+- [ ] **Auditable Code**: Avoid obfuscation, minification, or dynamic code evaluation (`eval`, `new Function`).
+
+## 7. Incident Response
+
+If a malicious or compromised `full-access` extension is suspected:
+
+1. **Immediately revoke** any exposed API keys (check `auth.json` and provider dashboards).
+2. **Remove** the extension directory from `~/.omk/agent/extensions/`.
+3. **Audit** session files in `~/.omk/agent/sessions/` for leaked secrets or sensitive data.
+4. **Review** recent `bash` tool history and file modifications for unauthorized changes.
+5. **Re-install** OMK from a trusted source if the core runtime may have been tampered with.
+6. **Report** the incident to the OMK security team or open a confidential issue on the repository.
+
+## 8. References
+
+- OMK Extension Manifest Specification: `packages/coding-agent/docs/extensions.md`
+- OMK Session Format: `packages/coding-agent/docs/session-format.md`
+- OMK Settings and Configuration: `packages/coding-agent/docs/settings.md`
+
+---
+
+*Last updated: 2026-06-25*

package/docs/session-format.md

@@ -34,7 +34,7 @@ Source on GitHub ([omk-mono](https://github.com/earendil-works/omk-mono)):
 - [`packages/ai/src/types.ts`](https://github.com/earendil-works/omk-mono/blob/main/packages/ai/src/types.ts) - Base message types (UserMessage, AssistantMessage, ToolResultMessage)
 - [`packages/agent/src/types.ts`](https://github.com/earendil-works/omk-mono/blob/main/packages/agent/src/types.ts) - AgentMessage union type
 
-For TypeScript definitions in your project, inspect `node_modules/open-multi-agent-kit/dist/` and `node_modules/@earendil-works/omk-ai/dist/`.
+For TypeScript definitions in your project, inspect `node_modules/open-multi-agent-kit/dist/` and `node_modules/omk-ai/dist/`.
 
 ## Message Types
 

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`, `catppuccin-mocha`, `dracula`, `gruvbox-dark`, `kanagawa-dragon`, `omk-control`, `omk-control-grid-dark`, `omk-control-light`, `omk-control-panel`, `rust-forge`, `tokyo-night-storm`
+- Built-in: `dark`, `light`, `omk-control`, `omk-control-grid-dark`, `omk-control-light`, `rust-forge`, plus bundled Tinted schemes (`catppuccin-mocha`, `tokyo-night-storm`, `kanagawa-dragon`, `gruvbox-dark`, `dracula`)
 - Global: `~/.omk/agent/themes/*.json`
 - Project: `.omk/themes/*.json`
 - Packages: `themes/` directories or `omk.themes` entries in `package.json`
@@ -37,7 +37,9 @@ Select a theme via `/settings` or in `settings.json`:
 }
 ```
 
-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`.
+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` ports the OMK//CONTROL Night City TUI palette from the 0.78.8 visual console (`cyan`, `mint`, `magenta`, `purple`, `amber`, `red`, `cream`, `muted`, `gray` on `dark`/`surface`). The `rust-forge` and Tinted scheme themes are installed as additional selectable built-in themes, but they do not change the default OMK//CONTROL brand/tone.
+
+The bundled Tinted themes are generated from [`tinted-theming/schemes`](https://github.com/tinted-theming/schemes) Base24 palettes (MIT): Catppuccin Mocha, Tokyo Night Storm, Kanagawa Dragon, Gruvbox Dark, and Dracula.
 
 ## Creating a Custom Theme
 
@@ -293,13 +295,12 @@ 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)
+- [catppuccin-mocha.json](../src/modes/interactive/theme/catppuccin-mocha.json)
 - [tokyo-night-storm.json](../src/modes/interactive/theme/tokyo-night-storm.json)
+- [kanagawa-dragon.json](../src/modes/interactive/theme/kanagawa-dragon.json)
+- [gruvbox-dark.json](../src/modes/interactive/theme/gruvbox-dark.json)
+- [dracula.json](../src/modes/interactive/theme/dracula.json)

package/docs/tui.md

@@ -4,7 +4,7 @@
 
 Extensions and custom tools can render custom TUI components for interactive user interfaces. This page covers the component system and available building blocks.
 
-**Source:** [`@earendil-works/omk-tui`](https://github.com/earendil-works/omk-mono/tree/main/packages/tui)
+**Source:** [`omk-tui`](https://github.com/earendil-works/omk-mono/tree/main/packages/tui)
 
 ## Component Interface
 
@@ -33,7 +33,7 @@ The TUI appends a full SGR reset and OSC 8 reset at the end of each rendered lin
 Components that display a text cursor and need IME (Input Method Editor) support should implement the `Focusable` interface:
 
 ```typescript
-import { CURSOR_MARKER, type Component, type Focusable } from "@earendil-works/omk-tui";
+import { CURSOR_MARKER, type Component, type Focusable } from "omk-tui";
 
 class MyInput implements Component, Focusable {
   focused: boolean = false;  // Set by TUI when focus changes
@@ -59,7 +59,7 @@ The cursor remains hidden by default. This keeps the fake cursor rendering, whil
 When a container component (dialog, selector, etc.) contains an `Input` or `Editor` child, the container must implement `Focusable` and propagate the focus state to the child. Otherwise, the hardware cursor won't be positioned correctly for IME input.
 
 ```typescript
-import { Container, type Focusable, Input } from "@earendil-works/omk-tui";
+import { Container, type Focusable, Input } from "omk-tui";
 
 class SearchDialog extends Container implements Focusable {
   private searchInput: Input;
@@ -188,10 +188,10 @@ See [overlay-qa-tests.ts](../examples/extensions/overlay-qa-tests.ts) for compre
 
 ## Built-in Components
 
-Import from `@earendil-works/omk-tui`:
+Import from `omk-tui`:
 
 ```typescript
-import { Text, Box, Container, Spacer, Markdown } from "@earendil-works/omk-tui";
+import { Text, Box, Container, Spacer, Markdown } from "omk-tui";
 ```
 
 ### Text
@@ -273,7 +273,7 @@ const image = new Image(
 Use `matchesKey()` for key detection:
 
 ```typescript
-import { matchesKey, Key } from "@earendil-works/omk-tui";
+import { matchesKey, Key } from "omk-tui";
 
 handleInput(data: string) {
   if (matchesKey(data, Key.up)) {
@@ -299,7 +299,7 @@ handleInput(data: string) {
 **Critical:** Each line from `render()` must not exceed the `width` parameter.
 
 ```typescript
-import { visibleWidth, truncateToWidth } from "@earendil-works/omk-tui";
+import { visibleWidth, truncateToWidth } from "omk-tui";
 
 render(width: number): string[] {
   // Truncate long lines
@@ -320,7 +320,7 @@ Example: Interactive selector
 import {
   matchesKey, Key,
   truncateToWidth, visibleWidth
-} from "@earendil-works/omk-tui";
+} from "omk-tui";
 
 class MySelector {
   private items: string[];
@@ -435,7 +435,7 @@ renderResult(result, options, theme, context) {
 
 ```typescript
 import { getMarkdownTheme } from "open-multi-agent-kit";
-import { Markdown } from "@earendil-works/omk-tui";
+import { Markdown } from "omk-tui";
 
 renderResult(result, options, theme, context) {
   const mdTheme = getMarkdownTheme();
@@ -596,12 +596,12 @@ These patterns cover the most common UI needs in extensions. **Copy these patter
 
 ### Pattern 1: Selection Dialog (SelectList)
 
-For letting users pick from a list of options. Use `SelectList` from `@earendil-works/omk-tui` with `DynamicBorder` for framing.
+For letting users pick from a list of options. Use `SelectList` from `omk-tui` with `DynamicBorder` for framing.
 
 ```typescript
 import type { ExtensionAPI } from "open-multi-agent-kit";
 import { DynamicBorder } from "open-multi-agent-kit";
-import { Container, type SelectItem, SelectList, Text } from "@earendil-works/omk-tui";
+import { Container, type SelectItem, SelectList, Text } from "omk-tui";
 
 omk.registerCommand("pick", {
   handler: async (_args, ctx) => {
@@ -688,11 +688,11 @@ omk.registerCommand("fetch", {
 
 ### Pattern 3: Settings/Toggles (SettingsList)
 
-For toggling multiple settings. Use `SettingsList` from `@earendil-works/omk-tui` with `getSettingsListTheme()`.
+For toggling multiple settings. Use `SettingsList` from `omk-tui` with `getSettingsListTheme()`.
 
 ```typescript
 import { getSettingsListTheme } from "open-multi-agent-kit";
-import { Container, type SettingItem, SettingsList, Text } from "@earendil-works/omk-tui";
+import { Container, type SettingItem, SettingsList, Text } from "omk-tui";
 
 omk.registerCommand("settings", {
   handler: async (_args, ctx) => {
@@ -832,7 +832,7 @@ Replace the main input editor with a custom implementation. Useful for modal edi
 
 ```typescript
 import { CustomEditor, type ExtensionAPI } from "open-multi-agent-kit";
-import { matchesKey, truncateToWidth } from "@earendil-works/omk-tui";
+import { matchesKey, truncateToWidth } from "omk-tui";
 
 type Mode = "normal" | "insert";
 

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");
@@ -181,7 +181,7 @@ export default function (pi: ExtensionAPI) {
 
 **Use StringEnum for string parameters** (required for Google API compatibility):
 ```typescript
-import { StringEnum } from "@earendil-works/omk-ai";
+import { StringEnum } from "omk-ai";
 
 // Good
 action: StringEnum(["list", "add"] as const)
@@ -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;