A persistent, Git-versioned map of your whole codebase and database schema that coding agents read before they touch...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Multiple
Fastest way to find out if aoci-code belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add aoci-code -- npx aoci-codeRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove aoci-codeNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ aoci-code ← registers here
A persistent, Git-versioned map of your whole codebase and database schema that coding agents read before they touch anything. Local-first MCP server + CLI in Go: a governed repository index of code knowledge that gives Claude Code, Codex, Cursor, and opencode long-term context, memory, and code intelligence.
Source: GitHub repository
Source check: October 14, 2026
Upstream commit: October 14, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.