Clixad
Freemium
Developers who prefer terminal workflows
Managing three or four coding agent subscriptions means constant context-switching — opening a different terminal, re-explaining the codebase, losing your place in Pi every time you need Codex to handle something Claude Code won't. Pi Omniagent Extensions patches that gap by letting you call Cursor, Codex, Claude Code, and Rovo from Pi's model picker without leaving your workspace.
Each extension is a TypeScript file that wraps one external agent's CLI behind an ACP (Agent Communication Protocol) interface, so Pi treats it as just another selectable model. You pick 'Cursor Sonnet' or 'Opus [claude-code-acp]' from the picker, and Pi routes your turn to that agent running locally in your environment. The architecture is thin by design — four files, an npm install, no hosted API, no backend. That thinness is also the ceiling: this is a single developer's open-source project with two GitHub stars and no stated contributors, so production support expectations need to match that reality. Teams with a single agent workflow get no benefit here.
Bottom line: Pick this if you are already paying for Pi plus at least two other coding agent subscriptions and want to stop switching terminals; skip it if your team needs a maintained, supported integration layer, because a two-star solo project is not that.
Find your fit
More options in CLI Coding Agents. Compare pricing, platforms, and features side by side.
Freemium
Developers who prefer terminal workflows
Freemium
Developers preferring fully local agent execution
Pi Omniagent Extensions is a set of four TypeScript shims — cursor-acp.ts, codex-app-server.ts, claude-code-acp.ts, and rovo-acp.ts — that each wrap one external coding agent’s CLI into an ACP-compatible interface. Once installed via npm, they surface inside Pi’s /model picker as selectable models. You choose ‘GPT-5 [codex-app-server]’ or ‘Cursor Sonnet’ directly inside your existing Pi workspace session, and Pi hands your turn off to that agent’s CLI running locally. No cloud relay, no account linking beyond what each agent already requires.
The differentiating design choice is ACP (Agent Communication Protocol), which provides the common message envelope that lets Pi treat a Cursor process and a Claude Code process as interchangeable model endpoints. That means switching agents mid-session is a picker selection, not a terminal hop. For developers who are already subscribed to several tools and want to route different task types to the agent best suited for them — without rebuilding context each time — this is the mechanical glue that makes that possible.
This fits a narrow but real use case: a single developer or small team sitting on multiple agent subscriptions who wants to maximize credit utilization across those tools from one interface. It breaks down at the boundary of its scope — there is no task routing logic, no fallback handling, and no abstraction above the per-agent CLI. When a CLI it wraps changes its interface, the corresponding shim breaks until the repo is updated. With zero open issues, zero pull requests, and two stars, the update cadence is an open question.
Installation is local only, documented in README.md, HOW_IT_WORKS.md, and USAGE_GUIDE.md in the repository. No API is exposed, no hosted service is involved. Each agent’s own authentication and subscription requirements remain in force — this tool layers on top of what you already have, not a replacement for any of it.
Sign in to rate this tool or suggest an edit.