Pi vs HagiCode: Features and Comparison

A small core you can reshape

Pi's own description is "a minimal, extensible agent harness that you can make your own." Sub-agents, plan mode and permission popups are left out on purpose, so what you run is what you chose to add.

Extensions, skills, prompt templates and themes can be bundled as Pi packages and shared through npm or git.

Sessions stored as trees

A session is a tree kept in a single file. You can return to an earlier point with /tree and branch from there without losing the other branch.

Older messages are summarised automatically as the context limit approaches, and compaction can be customised through extensions. /export writes a session to HTML and /share posts it as a GitHub gist.

Four ways to drive it

Use the interactive terminal UI, print/JSON mode for scripts and event streams, an RPC protocol over stdin/stdout, or the TypeScript SDK to embed Pi in your own app.

That makes Pi easy to wrap, which is exactly how tools such as HagiCode can run it.

Broad provider support with your own accounts

Pi lists more than 15 providers, including Anthropic, OpenAI, Google, Azure, Bedrock and Ollama. Sign in with /login using a subscription or an API key, and add custom providers through models.json.

Pi has no built-in permission system and runs with your user's permissions, so its docs suggest a container when you need stronger isolation.

Parallel sessions and Agents management

Pi leaves sub-agents to extensions. In HagiCode every Pi run is its own session, so one can refactor while another writes tests, and Agents management shows each one's status.

OpenSpec proposals

Pi ships without plan mode, so HagiCode's propose, validate, apply, archive flow gives each Pi task a written plan and a record. Free editions allow 3 concurrent proposals.

AI commit and Code Server

HagiCode writes the commit message from your diff and locks the repository while it commits. The embedded Code Server opens files Pi changed in a browser editor.

Monospecs and Vault

Monospecs lists your repositories in one file so Pi starts a proposal knowing the whole change surface. Vault keeps reference projects and notes that new proposals can use as context.

OmniRoute, tool-call view and TokenMonitor

If you configure OmniRoute, Pi's model requests can be routed through it. Pi's tool calls use the same format as other agents. A TokenMonitor status-bar item shows today's tokens and cost; it is off by default.

Interactive questions

When Pi asks a structured question, HagiCode shows it in the conversation, the session waits for a reply, and your answer continues the same run. If the run already ended, the answer goes in as a normal message in the same session.

• Questions asked at the same time can be answered in one submission;
• A question unanswered after 30 minutes expires and can still be answered by a follow-up message;
• Enabled per CLI by the interactive-control setting.