Open Kioku vs Pantheon

Open Kioku and Pantheon are both cli coding agents 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.

Open Kioku

Open Kioku indexes a repository into a local SQLite and Tantivy store, then exposes that index to MCP clients — Claude Code, Cursor, Codex — so agents build structured, evidence-backed plans before touching a single file. The pre-edit plan names exact file ranges, affected symbols, caller graphs, and validation candidates. The post-edit verify step checks that changes stayed inside the declared boundary. No source leaves the machine; write tools stay gated unless you explicitly unlock them. The ceiling arrives when the repo or language falls outside what the local indexer can parse — at that point the graph edges simply are not there, and the agent falls back to inference.

Pantheon

The harness follows a fixed pipeline: plan, then N parallel implementations, then adversarial verification, then a judge that decides which survives. A companion pair — pantheon-gap and pantheon-gap-x — runs the same shape as a reviewer against an existing codebase, surfacing what's missing rather than building something new. The cross-model variant (pantheon-x, pantheon-gap-x) routes the verification step through GPT-5.5, so the reviewer isn't the same model family as the builder. This is a Claude Code skill, not a standalone app — it lives inside your Claude Code environment, which means setup assumes that context and breaks outside it. The repo is early-stage, with ten commits and no open issues, so production edge cases land entirely on you.

Attribute	Open Kioku	Pantheon
Pricing	Free	Free
Free trial	No	No
Open source	Yes	Yes
Has API	No	No
Self-hosted option	Yes	Yes
Platforms	npm, local CLI	Claude Code with Workflows
Pros	Local SQLite and Tantivy index with no source upload, so repositories under data-residency constraints or containing unreleased code never leave the machine — the class of hosted-index compliance problems does not arise. Symbol-resolution and graph-edge tracing replace text-match inference for impact analysis, which means an agent planning a token-expiration change gets the actual callers and affected modules instead of a list of files that contain the string. Pre-edit plans include explicit allowed and forbidden file boundaries, so the agent is told what is out of scope before it starts — reducing the drift where an edit intended for two files touches six. Validation candidates are selected before the edit begins rather than after, so the agent runs the right tests against the right change instead of discovering the gap in the CI failure. MCP stdio transport connects to Claude Code, Cursor, and Codex without a dedicated plugin per client, so one local index serves multiple agent surfaces from a single install.	Parallel independent implementations with adversarial review, so logic bugs that a single model self-certifies get surfaced before they ship. Cross-model verification path (GPT-5.5 as reviewer against Claude as builder), which means the agent breaking the implementation has no stake in defending it — something a same-model loop structurally cannot offer. Gap-analysis variants apply the same harness to existing codebases, so you get a structured missing-feature report without manually auditing the project. MIT license with self-hosted option, so there is no vendor dependency on the infrastructure layer — you control where the pipeline runs. Tasks expressible as tests get a repeatable correctness loop, which means you can re-run the harness after changes without rebuilding the review process from scratch.
Cons	Language coverage determines graph completeness: repositories mixing a supported language with an unsupported one produce incomplete impact traces for the unsupported files, and the agent reverts to text-match inference for those paths — which is the same baseline the tool exists to replace. Teams with polyglot monorepos check the language support list before committing to the workflow. There is no API and no hosted option, which means teams building CI pipelines or cloud-based agent workflows that cannot run a local process have no path to integrate Open Kioku — those teams evaluate hosted code intelligence services that accept repository uploads instead. The index must be rebuilt or re-run after significant repository changes; the docs describe no incremental or watch-mode indexing, so teams with high-commit-velocity repositories that need fresh graph edges before every agent run carry a re-index step as an explicit pipeline cost.	The entire pipeline requires a paid Claude Code plan — teams without it have no supported entry point, and there is no documented workaround or alternative invocation method. Correctness gains are scoped to tasks you can express as tests; tasks with subjective outputs, ambiguous requirements, or no clear verification condition get no benefit from the adversarial loop, because there is nothing for the reviewer to break against. The cross-model path depends on GPT-5.5 access — teams without that access cannot run pantheon-x or pantheon-gap-x, and there is no documented fallback to a different external model. At ten commits with no issues filed, production edge cases have no community triage path and no maintained issue history — teams hitting unexpected behavior are on their own, and teams with a reliability bar that requires a maintained issue tracker will move to a more established code-review automation tool instead.

Bottom line

Open Kioku and Pantheon 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 Open Kioku and Pantheon?

Open Kioku is Free and open source, while Pantheon is Free and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Open Kioku better than Pantheon?

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.