OMP vs HagiCode: Features and Comparison

IDE-grade tooling inside the terminal

The README lists 14 LSP operations and 28 DAP operations. File renames go through the language server, so imports update before a file moves. Debugger sessions work with lldb-dap, dlv and debugpy.

It also keeps persistent Python and Bun workers that can call the agent's own tools, and drives Chromium tabs for browser work.

Edits that fail safe

Hashline edits anchor each change to a content hash and are rejected if the file has moved on. ast_edit previews a structural change before it is applied.

Stream rules let a regex match abort the stream and inject a rule before the model retries, which is useful for keeping a model on your conventions.

Subagents and model roles

The task tool fans work out to subagents in isolated worktrees and returns schema-validated results. An advisor role lets a second model review each turn.

Models are routed by role (default, smol, slow, plan, commit, vision, task, advisor, tiny), with fallback chains and path-scoped model sets configured in ~/.omp/agent/config.yml.

Many ways in, and your existing rules come along

You can run it as a terminal UI, a one-shot omp -p command, an RPC process over stdio, a Node SDK, or an ACP server for editors such as Zed.

It reads rules and MCP servers from .claude, .cursor, .codex, .cline and other tool folders, so moving to omp does not mean rewriting your project instructions.

Parallel sessions and Agents management

Each omp run in HagiCode is its own session, so you can have one working on the API while another writes tests. Agents management gives every session a name and a visible status instead of a row of terminal tabs.

OpenSpec proposals

A task starts as a proposal and moves through propose, validate, apply and archive. The reasoning behind an omp change stays next to the diff. 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 the file omp changed in a browser editor. omp's own commit command still works in a terminal.

Monospecs and Vault

Monospecs declares your repositories in one file so omp starts a proposal with the full change surface. Vault stores reference projects and notes that new proposals can use as context.

OmniRoute, tool-call view and TokenMonitor

If you configure OmniRoute, omp's model requests can be routed through it. Tool calls from omp are shown in the same format as other agents. An optional status-bar item shows today's tokens and cost from TokenMonitor, off by default.

Interactive questions

When omp 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.