Octocode (muvon)

Coding · tested 2026-08-26 · re-test due 2026-11-24 · by the Hlido desk, not the vendor

In short: A Rust, local-first semantic code-search and knowledge-graph tool that turns a codebase into a queryable graph and exposes it to AI assistants over MCP — sub-2-second indexing, 12+ languages, Apache-2.0.

5 PASS · 0 FAIL of 5 public-surface claims

Quick answer

Octocode (muvon) scores 78/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-26). STEADY (78) because it is genuinely agent-native (MCP with semantic_search/view_signatures/graphrag), local-first, Apache-2.0, multi-language, and solves a real gap grep cannot. Pricing: Open source (free entry point documented).

This Octocode (by muvon, distinct from the octocode.ai tool of the same name) builds a cross-file knowledge graph from your codebase using tree-sitter AST parsing and vector embeddings, then lets you query it in natural language — 'how does authentication work?' returns relevant code across files, and dependency queries return callers, callees and related types. It is local-first, Apache-2.0, claims sub-2-second indexing and 12+ language support, and ships an MCP server exposing three clear tools to Claude, Cursor and Windsurf: `semantic_search`, `view_signatures` (signatures without full implementations — a real token-saver for agents) and `graphrag` (relationship/dependency queries). The framing is honest about the problem it targets — grep fails on conceptual queries, and AI assistants lack structural awareness — and the GitHub star signal (a few hundred) is a modest but real adoption marker. The ceiling on the score is that the differentiators (indexing speed, semantic quality, the '200M free tokens/mo' figure) are vendor claims on the marketing surface rather than measured here, and the embeddings approach means quality depends on the embedding model and repo shape. Note the name collision: an unrelated evidence-first research tool also called 'Octocode' exists — pick by mechanism (this one is embeddings + knowledge graph; the other is cited tool-based retrieval).

Why STEADY

STEADY (78) because it is genuinely agent-native (MCP with semantic_search/view_signatures/graphrag), local-first, Apache-2.0, multi-language, and solves a real gap grep cannot. Held at 78 because indexing-speed and semantic-quality claims are vendor-stated rather than benchmarked here, embeddings quality varies with model and repo, and it shares the 'Octocode' name with an unrelated tool, muddying discovery.

Public-surface checklist

What we saw

1 screenshot captured by the Hlido engine during the reviewed run (run-31adba7018e90b1f-octomind-run). Our own captures — not vendor marketing material.

Octocode (muvon) — run screenshot 1 (home.png)
home.png

What it does well

What it fails at

Red flags

Best for

  • Developers onboarding to an unfamiliar codebase who want natural-language answers spanning files
  • AI pair-programming setups that need semantic context and dependency graphs handed to the assistant over MCP
  • Teams that want local-first, Apache-2.0 code intelligence with no hosted index

Not recommended for

  • Teams that need a commercially supported, SLA-backed product
  • Workflows that prefer cited, tool-driven retrieval over embeddings-based ranking

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-26.

Compared to

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 62/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Runs as an MCP server exposing semantic_search, view_signatures and graphrag to Claude, Cursor, Windsurf and any MCP client, giving the assistant meaning-based search and dependency-graph queries over a locally indexed codebase. view_signatures returns type/function signatures without full bodies, which keeps agent context small. Also usable directly as a local CLI.

Agent-friendly score: 8/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-24

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/muvon-octocode.svg)](https://hlido.eu/check/?agent=muvon-octocode)

HTML

<a href="https://hlido.eu/check/?agent=muvon-octocode"><img src="https://hlido.eu/badge/muvon-octocode.svg" alt="Hlido trust score"></a>