Oh My Pi (OMP)

Host entry

A terminal command owns the process, current working directory, stdin/stdout, shell environment, and project file discovery.

Host owns

The CLI host owns agent loop timing, approval prompts, tool execution, session files, and how hook or MCP subprocesses are launched.

Connector role

agent-connector can only write the host's documented CLI config, prompt, memory, hook, MCP, or package files and point them at the home binary. Current wired connector surfaces: MCP server, Hooks, Memory, Action affordances.

Implementation consequence

A CLI surface is byte-addressable and smoke-testable from a temporary HOME, but terminal UI behavior still belongs to the host process. No visible host-native gap is currently tracked for this surface.

Source pass

Current source review findings are kept as the first architecture section so readers can separate external evidence from the generated local coverage model.

• OMP is tracked as a Pi-family plugin surface, so it should reference the Pi harness while keeping its adapter id and ts-plugin flow separate.
• The Pi repository exposes `.pi` and package-level runtime folders, giving OMP a concrete local project/user artifact story without inventing a new host.
• Because Pi distinguishes CLI, runtime, and TUI packages, OMP's page should describe the plugin bridge rather than flatten it into Pi's CLI row.

Runtime boundary

The adapter target is the OMP layer on top of Pi's harness. Pi owns the executable runtime, while OMP should be documented as packaged configuration, extensions, skills, prompts, or workflows.

• Pi packages can be installed from npm or git.
• The OMP row should not duplicate Pi core unless the package changes behavior.

MCP registration

Because Pi core has no built-in MCP, OMP must be explicit about whether it adds MCP through an extension or package. The page should not count Pi's extensibility as OMP MCP support without package evidence.

• MCP integration is named as something users can build with extensions.
• Connector coverage should distinguish package-provided behavior from core host behavior.

Hook bridge

OMP should be treated as a TypeScript extension/package surface over Pi. Hook-like behavior can come from extension events, dynamic context injection, keyboard shortcuts, and tool wrappers rather than a fixed core event contract.

• Extensions can access commands, tools, keyboard shortcuts, events, and the TUI.
• Agent-connector should document OMP as package-mediated unless a stable event schema exists.

Content surfaces

OMP content is expected to live in Pi's package primitives: skills, prompt templates, themes, extensions, SYSTEM.md, AGENTS.md, and dynamic context handlers. This makes it a distribution row.

• Pi package install can bundle multiple artifact types together.
• Workflow opinion belongs to OMP, while runtime mechanics belong to Pi.

Marketplace and host-only affordances

The host-only affordance is package distribution over a minimal harness. OMP should be used to teach how package overlays can change a host's surface without changing the core runtime.

• This row helps separate base host from ecosystem overlay.
• The package layer can provide stronger defaults while preserving Pi's minimalism.

Host-specific shape

Oh My Pi follows Pi lineage but adds a ts-plugin bridge and actions; skills, commands, and subagents are not treated as confirmed writable host surfaces.

• Form factor: CLI.
• Native surfaces: MCP server, Hooks, Memory, Action affordances.
• Wired surfaces: MCP server, Hooks, Memory, Action affordances.
• Visible gaps: none.

Hooks

Hooks enter through a generated plugin module that the host loads in its own runtime.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

The plugin bridge is generated directly, but there is no separate drivable marketplace path in the current driver registry.

• Runtime handlers: Action affordances.
• User-visible affordances: Users see managed actions + memory surfaces after install; runtime-only surfaces stay behind the host boundary..