Pi Omniagent Extensions vs Yorishiro

Pi Omniagent Extensions and Yorishiro are both coding assistants tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Pi Omniagent Extensions

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.

Yorishiro

Yorishiro is a macOS terminal built in Tauri (Rust + web frontend) that gives the AI a persistent visual presence inside the shell — reactions, personality, and pack-based self-modification that changes how the environment looks and behaves based on conversation. The target workflow is Claude Code or Codex running inside a terminal that reads and writes to its own surroundings. Packs let the AI modify its space; character guidelines ship in the repo so personality stays consistent. The project has 4 stars and 2 open pull requests, which means the community is tiny and you are close to the edge of what the maintainer has tested.

Attribute	Pi Omniagent Extensions	Yorishiro
Pricing	Free	Free
Free trial	No	No
Open source	Yes	Yes
Has API	No	No
Self-hosted option	Yes	Yes
Platforms	—	macOS
Pros	ACP-based agent handoff inside a single Pi session, so you route work to Cursor, Codex, Claude Code, or Rovo without rebuilding workspace context in a separate terminal. All four agent wrappers are in plain TypeScript with no abstraction layer, so reading exactly what the shim does — and patching it when a CLI changes — takes minutes rather than filing a support ticket with a vendor. Fully local execution with no hosted backend, which means no additional data leaving your machine beyond what each agent's own CLI already sends. Free and open-source under no stated proprietary license, so there is no paywall blocking access to any of the four integrations.	Pack-based self-modification lets the AI alter its own terminal environment through conversation, so the workspace reflects what the session has become rather than staying frozen at launch state. MIT license with a public contributing guide, so teams can fork and extend without waiting for upstream approval when the base behavior doesn't fit their workflow. Built on Tauri rather than Electron, which means the binary stays small and the Rust backend handles native system calls directly — avoiding the memory overhead that Electron-based terminal wrappers accumulate under sustained sessions. Bundled character guidelines (English and Japanese) ship in the repo, so personality configuration is version-controlled and auditable rather than hidden in a vendor dashboard. Targets Claude Code and Codex at the integration layer, so developers already using those tools get presence feedback without rewiring their existing AI coding setup.
Cons	When any of the four wrapped CLIs updates its interface — Cursor, Codex, Claude Code, or Rovo — the corresponding shim silently breaks or throws until the repo author pushes a fix. A two-star, zero-contributor project has no SLA for that fix. Teams with a dependency on uptime switch to maintaining their own fork immediately. There is no routing logic inside the tool: deciding which agent handles which task is entirely manual, via the Pi model picker. Teams wanting rule-based or cost-optimized routing across agents hit this ceiling on the first attempt to automate distribution and end up writing their own dispatch layer outside the tool. The tool only works inside Pi — it provides zero value to developers not already using Pi as their primary coding agent host, which means any team evaluating a different primary agent surface abandons this entirely rather than adapting it.	macOS-only with no stated plan for Linux or Windows support — teams with mixed-OS engineering environments cannot standardize on this tool, and the moment a Windows developer joins the workflow, they are excluded entirely. No API surface means the terminal presence cannot be driven programmatically — any attempt to integrate Yorishiro into an automated pipeline requires forking the codebase and building the integration layer yourself, at which point you are maintaining a custom fork of a 4-star project. The maintainer base is one person with 4 stars and no evidence of production deployments at scale — when you hit a bug at the boundary of pack logic or character state, there is no community to search and no support queue to file against; teams with reliability requirements will abandon this for a conventional terminal multiplexer plus a Claude Code integration that has more active maintenance.

Bottom line

Pi Omniagent Extensions and Yorishiro are closely matched on pricing model, openness, and API availability — pick by feature set and platform support in the table above.

Frequently asked questions

What is the difference between Pi Omniagent Extensions and Yorishiro?

Pi Omniagent Extensions is Free and open source, while Yorishiro is Free and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Pi Omniagent Extensions better than Yorishiro?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.