Augment indexed our monorepo then rewrote a feature flag we already settled
Augment
AI coding platform built for large real-world codebases
Gave Augment a week on our Go monorepo (~1.8M LOC, lots of internal packages).
Indexing took most of Tuesday. After that it was weirdly good at finding the right service — way less "here's a helper from 2022 that we deleted" than Cody gave me last month.
Friday it still rewrote a working feature flag check into a pattern we banned in code review. Caught it before merge, but only because CI yelled about an unused import.
Anyone else running it on something bigger than a toy repo? Curious if the index actually stays warm or if I'm about to re-index every Monday.
5 comments
Join the discussion
Log in to comment.
honestly the indexing claim is what keeps stopping me. i don't want a second "knowledge base" that silently goes stale while my teammates keep shipping.
did you leave the index running overnight or kick it per branch? that alone decides if this stays a demo for me.
The feature-flag rewrite is the part that would make me uninstall. If it can't respect house style after "understanding" the repo, the index is just expensive search.
I'd rather a dumb CLI that greps
internal/correctly than a chat that invents patterns we already banned. Glad CI caught it — that unused import save is doing more work than the agent.yes. house style is not optional. if it "understand" the repo and still invents the pattern you banned, the index is marketing.
i want the agent to fail closed on internal/ conventions, not invent a nicer looking check. unused import in CI saved you — that is the real product.
we tried a similar index on our FastAPI monorepo (~400k LOC, not 1.8M) and the "warm" part died after ~36h of nobody touching those packages.
on a Mac Studio it also chewed enough RAM that Activity Monitor lied about available memory for two days. i bounced back to ollama + a tight context window for the services i actually edit.
does Augment tell you when the index went stale, or do you just find out when it suggests deleted helpers again?
We ran Augment for three nights before a launch with two engineers. Finding the right service was genuinely better than Cody — less 2022 ghost helpers.
Still blocked a PR Thursday because it rewrote our feature flag the same way you described. No plan doc, just "cleanup". Reverted and finished the hotfix by hand.
For anything bigger than a toy repo I'm keeping indexing on a branch-only kick until they show the index age in the UI.