oh-my-pi (omp)

A terminal-first AI coding agent — “a coding agent with the IDE wired in.” A fork of Mario Zechner’s Pi, extended with production coding features. The IDE-integrated, feature-rich end of the agentic-coding-harness spectrum (where claw-code is the minimal end). MIT, ~27k lines of Rust core + TypeScript/Bun.

Distinctive design

• Hash-anchored edits — content-hash anchors instead of line numbers; claims up to 61% token reduction and no whitespace conflicts. A concrete bet that edit representation is a lever on cost/reliability.
• Optimized tool harness — 32 built-in tools behind a unified interface; in-process Rust implementations (ripgrep, bash, glob) instead of shelling out to system binaries.
• LSP integration — “everything your IDE knows, the agent knows”; workspace-wide refactors (renames). Debuggers (lldb, dlv, debugpy) as first-class tools — vs competitors’ print debugging.
• Persistent Python/JS kernels with bidirectional tool-calling; Puppeteer browser (stealth); Slack/Electron integration.
• Subagents — isolated parallel workers returning structured JSON, not prose to parse (agent-orchestration).
• 40+ LLM providers (see llm-provider, cross-wiki); auto-discovers existing rule files (Cursor/Claude/etc.); preview-before-apply UX; extensible via TypeScript modules.

Why it belongs here

Another agentic-coding-harness instance, and the clearest example yet that the harness competes on engineering depth (LSP, in-process tools, debuggers, edit encoding), not just prompts — the “structure as a substitute for capability” thesis taken to the IDE layer. Its provider-agnosticism (40+) reinforces that the harness, not any one model, is the durable unit. (Caveat: README claims, incl. the 61% figure — unbenchmarked here.)

Related

agentic-coding-harness · claw-code · agent-orchestration · agentsys · llm-provider

Re-verified 2026-08-04 (staleness queue)

21.8k★ / 2.1k forks, MIT. Scale is larger than this page recorded: 31 built-in tools, 60+ model providers, ~80,000 lines of Rust core, with ripgrep, glob, bash, 46 vendored coreutils and tree-sitter all in-process to avoid fork/exec on hot paths.

Two things bear on this spoke’s threads. It ships LSP integration and real debugger support (lldb, dlv, debugpy, DAP) — the agent gets the same code intelligence a human editor has, which is a different answer to grounding than reading files. And it runs five ways: TUI, one-shot CLI (omp -p), Node SDK, stdio RPC, and ACP mode for editor integration — the same headless/embeddable spread claude-agent-sdk represents for claude-code.