AI codebase intelligence
One command gives your AI agent persistent, queryable memory of your entire codebase — before it touches a single file.
$
npx @kopikocappu/mycelium init
Works with Claude Code · Cursor · GitHub Copilot · Any MCP-compatible agent
↓ scroll
70+
Files mapped per project
Without Mycelium
Before writing a single line, your agent opens file after file trying to build a mental model it has never had. By the time it starts, it's read 40 files and lost context on most of them.
app/page.tsx
app/layout.tsx
lib/auth-context.tsx
lib/user.ts
components/Navbar.tsx
components/ProGate.tsx
app/api/stripe/webhook/route.ts
+ 33 more files...
With Mycelium
Before touching anything, your agent calls /preflight and gets back exactly the files it needs — with plain English descriptions of what each one does.
app/api/checkout/route.ts
app/api/stripe/webhook/route.ts
lib/user.ts
app/pro/page.tsx
01 — SCAN
$ mycelium init
Mycelium parses every file, resolves every import, and builds a dependency graph of the entire codebase. Claude Haiku writes a plain English description of what each file does and why it exists.
02 — QUERY
GET /preflight?task=
Your agent calls /preflight with a plain English description of its task. Mycelium returns exactly which files matter and how they connect. Four files, not forty.
03 — TRACK
GET /history
Every file save is logged with a timestamp, a task description, and which agent made the change. You always know what your agents did — and when.
⟳
Describe your task in plain English. Get back exactly the files that matter, with AI-written explanations of what each one does and how they connect.
◈
A browser-based visualization of your entire codebase. Files as nodes, imports as edges, call relationships in orange. Understand any codebase in five minutes.
◎
Every file save logged by task and agent identity — human, Claude Code, Cursor, anything. The full audit trail of what your AI agents actually did.
⌖
Find files by concept, not keyword. "Authentication flow" finds the right files even when none of them have the word "auth" in their name.
⊡
Mycelium writes CLAUDE.md and .mcp.json into your project automatically. Agents discover it and use it without any manual configuration.
⟁
Before modifying a function, ask what calls it. Get the full blast radius — every file and function that depends on what you're about to change.
In practice
An agent about to implement a Stripe checkout calls /preflight and gets back exactly the right context. No guessing. No wasted reads. Just the graph knowing what matters.
The server runs locally at localhost:47821 — your code never leaves your machine.
$ curl "localhost:47821/preflight?task=add+stripe+checkout"
{
"task": "add stripe checkout",
"mode": "semantic",
"tokensSaved": 7000,
"files": [
{ "nodeId": "app/api/checkout/route.ts", "score": 0.94 },
{ "nodeId": "app/api/stripe/webhook/route.ts", "score": 0.91 },
{ "nodeId": "lib/user.ts", "score": 0.87 },
{ "nodeId": "app/pro/page.tsx", "score": 0.82 }
]
}
// 4 files. 7,000 tokens saved. Agent starts writing.
Developers
Stop watching Claude Code open 30 files before writing a single line. Mycelium gives it a map. It reads 4 files and gets it right.
Engineering leads
Every agent session logged. Every file touched, timestamped, attributed. The audit trail that AI coding tools forgot to build.
New engineers
Open the graph viewer. See every file, every dependency, every connection — with plain English explanations on every node. No more codebase spelunking.
Get started
One command. Any project. Your agent never files blind again.
$
npx @kopikocappu/mycelium init
🍄 mycelium
Built by Minh Tran · MIT License · 2026
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。