aoci-code
AOCI-CODE keeps a persistent, Git-versioned index of your whole codebase inside the repository, written by your coding agent and governed by a local MCP server. The idea in the README is that the agent reads the index once and knows the system, instead of searching and re-reading files for every task. Each file gets one line: what it is responsible for (F), what must be read with it (R), what callers depend on (A) and what cannot be inferred from code but must not be gotten wrong (S), plus a short tag for layer, domain, importance and size. A few hundred lines are meant to cover a whole system.
The first index is built by your agent file by file, in resumable batches, and the README estimates about an hour per 200,000 lines, depending on the model. It claims a project of about 500,000 lines can be indexed, and says a 700,000-line commercial system is developed this way with an index of about 300K tokens. After that, the MCP server detects code changes and issues entries to update, and the agent fills them in as it finishes tasks. MySQL and PostgreSQL schemas (and constrained openGauss 6.0.5) can be indexed too, using table structure only.
The README says it is local only: it reads source code and database table structure, never business data, uploads nothing, opens no Internet connection, and keeps database credentials as environment-variable names. Setup is done by pasting an instruction into your agent that downloads a release, runs `init` and `scan`, then restarting the agent and asking it to build the index; an `aoci ui` panel shows status. The license is FSL-1.1-MIT (Functional Source License), which is source-available rather than open source. Last push was 2026-10-13. This review is based on the README and repository data; we have not run it ourselves.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-06
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 26
- Latest release
- v0.2.0-rc1 (2026-11-05)
- Open issues
- 11
- Recent issues with at least one comment
- 19/21
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #54 支持多 git 仓库容器目录、灵活选择索引范围与渐进式建立索引12 comments · 2026-09-15
- #84 Windows Defender aoci.exe 下载后移除 - 检测到病毒,导致无法安装4 comments · 2026-09-26
- #135 Feature: index MongoDB data models — extend `database source` (currently PostgreSQL/MySQL/openGauss) to MongoDB2 comments · 2026-10-17
- #34 Port the product-code parts of #28 after v0.1.02 comments · 2026-09-07
- #155 [Feature] 支持将索引与运行状态集中到单个 .aoci 目录,并提供安全迁移流程1 comments · 2026-10-27
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- Your codebase or database schema is large and complex, causing coding agents to burn tokens and lose context across sessions.
- You want a local-first, Go-based, Git-versioned architectural knowledge map that coding agents read before touching any files.
- Your project is a simple small repo or script where agents can easily fit the whole tree in context without an index map.
- You need general conversational memory for chat logs or personal tasks rather than software architecture topology (use Mem0 or mcp-memory-service).
How it differs
aoci-code maintains a Git-versioned structural map of symbols and schemas; codebase-memory-mcp indexes codebases into vector embeddings for semantic search.
aoci-code emphasizes Git-governed agent architecture contracts; code-graph-rag focuses on AST graph-database construction and graph traversal.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!