At a glance
An MIT-licensed terminal agent, invoked as `omp`, that layers LSP and debugger tooling, browser control, first-class subagents, MCP, ACP, RPC, and a large provider catalog onto Pi's extensible base.
Good choice if
- Terminal users who want IDE-grade code intelligence and debugger access
- Parallel tasks with typed subagent results and isolated worktrees
- Provider-flexible automation through one-shot, RPC, ACP, and SDK entry points
Check before choosing
- The default approval mode is yolo, destructive-command overrides do not force a prompt in that mode, and subagents also run yolo; safer always-ask/write and per-tool policies require explicit configuration
- Task copy-on-write or worktree isolation separates delegated file changes but is not a documented OS-level sandbox for the primary process, browser, debugger, shell, or local MCP servers
- Checkpoint and rewind are disabled by default and prune conversation context only: they do not restore working-tree files, Git state, artifacts, processes, or external side effects
See 4 more considerations
- Cross-session memory is disabled by default and model-generated; it must be checked against the current repository rather than treated as authoritative state
- Secret obfuscation is disabled by default, while extensions and hooks run in-process without isolation and can block or rewrite tool calls, access session state, or terminate the session if they fail outside guarded handlers; revised inputs are schema-revalidated and pass through the approval gate before execution
- The large built-in surface (browser/CDP, debugger, eval kernels, SSH, MCP, collaboration, media, and high-concurrency agents) expands setup and trust boundaries
- Project-owned compaction and local-model evaluations plus README performance claims are not independent harness benchmarks, so no score is imported