The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Neuromesh
The Biomimetic Context Engine & Neural Runtime for AI Coding Assistants
Install
git clone https://github.com/pinoox/neuromeshInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →NeuroMesh
Ship less context. Ship the right code.
Local-first MCP context engine for Cursor, VS Code, Claude, Codex, and every MCP client. NeuroMesh indexes your repo into a graph, routes your prompt to the right symbols, and sends a folded evidence packet — not thousand-line file dumps.
Cursor · VS Code · Claude · Codex · OpenCode · MiMo CLI · Antigravity · Kilo · Trae · Windsurf · Zed
The pain · Fold · Galaxy · Measured · Install · Connect · Docs · Site
The pain
You ask a simple question in a large project. The editor copies two or three thousand-line files and ships them to the model.
What you pay for:
- Tokens you never needed — dollar cost on every turn
- Seconds of fake loading while the window fills with helpers you will not touch
- Lost in the middle — the model drowns in unrelated bodies and invents bugs
Today’s workarounds all leak in a different place:
| Approach | What goes wrong |
|---|---|
| Vector RAG | Chunks smash functions. The shape of the code disappears. |
| “Just attach the files” | The model sees everything and understands nothing. |
| A static code graph | Better map — then it still pastes full files into the prompt. |
NeuroMesh is the missing step: route first, then fold. The graph is for finding the path. The packet is what the model actually reads.
Don’t delete. Fold.
Don’t delete the extra code. Fold it.
How does nature pack two metres of DNA into a nucleus without deleting a single letter?
Not by throwing genes away — by folding.
Nature does not delete DNA to fit a nucleus. It supercoils.
NeuroMesh treats the syntax tree like a genetic strand in RAM:
- Functions you need stay expressed (exons) — real body, real lines
- The rest collapse to a one-line reversible intron:
/* [neuromesh:fold:fold_unused_helper_1 | 12 lines folded | fn unused_helper()] */
The agent still sees the shape of the file — signatures, imports, neighbors — without paying for every private helper. When a folded body is required, neuromesh_expand_fold unsplices it from a registry in memory. Nothing was deleted. Nothing needs a second grep of the disk.
Structure stays. Tokens sleep. Wake a fold when you need it.
Why it feels different
| What you get | What it means for you |
|---|---|
| Smart folding | Relevant functions stay open; everything else collapses to one-line markers you can expand on demand. |
| Shortest path routing | Only the files your task needs — not the whole repo neighborhood. |
| Learns from your edits | Call record_feedback after a good fix; similar tasks route faster next time. |
| Safety modes | Balanced by default; auth and payment tasks automatically get more context. |
| Live code graph | Your repo indexed in RAM — functions, imports, and calls, not shredded text chunks. |
Curious about the biology metaphor? docs/nature.md
Install
Similar plugs
Reverse engineer anything with agents, from app behavior down to native binaries.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)