HEIDES
The code nervous system for AI agents.
A deterministic harness that maps every file, symbol, and call into a persistent graph, then guards every change against it. One binary. CLI and MCP server. No cloud, no model required for the core.
The System
Three layers between your agent and your code.
HEIDES does not compete with coding agents. It is the substrate beneath them.
Spine
Scans the workspace once and keeps a persistent graph of every file, symbol, import, and call. Agents read a map instead of guessing about your code.
Harmony
Guards every proposed change. Security taint, edge cases, and dependency risk are checked against the graph before a patch ever touches disk.
Grounding
Turns a task into a plan anchored to real files and symbols, so the agent works from evidence, not from memory of a training set.
Interfaces
CLI for humans. MCP for agents.
Native commands cover scan, query, describe, export, check, staged, plan, scaffold, deps, watch, and mcp. The MCP server exposes the same spine and harmony tools over stdio, so any MCP aware editor or harness attaches directly.
Listed in the official MCP registry as io.github.AbduljabbarBXR/heides, installable by name from registry aware clients.
$npm install -g heides$heides scan$heides query callers my_function
$heides mcp
Runs where your work runs.
A laptop, a server, a CI runner, or a phone running Termux. One binary for all of them.
Using HEIDES in production ?
We use HEIDES on every system we build. Talk to us about integrating it into your team's workflow.
Talk to Us