Indexing code outside the repo: how to save tokens without throwing the project into context
Indexar o código fora do repo: como economizar tokens sem jogar o projeto no contexto Pessoal, o agent precisava achar um símbolo. Trabalho de um minuto. Na prática, ele abria arquivo atrás de arquivo, colava dump de teste no papo e a janela sumia. Às vezes a fatura também. Não era o modelo burro. Era eu pagando o monorepo inteiro pra responder a pergunta errada. A pergunta mudou. Deixei de ser…
A developer shares their experience of optimizing their coding agent's performance by separating the layers of domain memory and code-reading costs. They moved the symbol index outside of the repository and Git, to a local cache, to reduce token costs and improve the agent's efficiency. This change allows the agent to quickly look up information without having to re-read the entire monorepository.
The developer provides guidelines for setting up an indexer, including considering where the index lives, who reads it, and how to revoke access.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
