DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to take over an existing codebase with an agent in one pass with Aoci Code

Build a Git-versioned index of a codebase of up to about 500,000 lines so the agent can start working from known context.

  • Top pick
  • Software and DevOps
  • Intermediate
  • 1 hour 30 minutes
  • From the README
  • Codex
  • Claude Code
  • Cursor

Who it is forA developer or team lead who inherits a large existing system and needs an agent to learn it quickly before making changes.

The problemAgents re-read and re-search the repository for every task, and a new project owner has no written map of what each file does or what must not break.

The outcomeAn index with one entry per managed file, a coverage report of how well the agent knows each area, and a link to the AOCI panel for review.

What you need first

  • A verified AOCI-CODE release package for your operating system and CPU, or a checkout of the canonical source repository (source builds also need the Go toolchain declared by go.mod and make)
  • A supported MCP host such as Codex, Claude Code, Cursor, or OpenCode
  • Normal read and write access to the target repository
  • For database indexing: a PostgreSQL or MySQL 5.7.6+ database (or openGauss 6.0.5 with constraints) and a connection-string environment variable set in the host environment

Steps

  1. Download the latest release package for your operating system and CPU from https://github.com/aoci-spec/aoci-code/releases and verify it using the installation guide.
  2. Place aoci (aoci.exe on Windows) at a stable absolute path, then run (inferred) aoci init in the project to set up AOCI and MCP for your host. (inferred, check the README)
  3. Run (inferred) aoci scan and make sure the AOCI cognition files are not ignored by .gitignore or .git/info/exclude. (inferred, check the README)
  4. Restart the agent so the new MCP server loads, then send the build instruction to build the index.
  5. Run aoci ui --detach --json (or ask the agent to) to open the AOCI panel and review coverage by area.

Prompt for your agent

In the repo <project-path>, confirm the AOCI MCP server is connected, then build the AOCI index for the whole project. Report the coverage level for each area and give me the AOCI panel link. Verify that aoci.txt and aoci.code.txt exist after the build.

Caveat. The first index takes about an hour per 200,000 lines of code, depending on the model and agent speed, and the index quality depends on what the agent writes.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page