Augment indexed the monorepo then tried deleting packages/build-config
Tried Augment on our pnpm monorepo Friday because the pitch is "large real-world codebases." Index finished in like 40 mins on the M2 Max.
First agent task: "clean unused deps in apps/web". It confidently opened a PR that removed packages/build-config — the thing every package.json extends. CI went red in 11 minutes. Diff looked reasonable until you noticed it never opened that folder.
We added path deny rules after. Still faster than Cursor on the 180k-line slice, but I do not trust it near infra/ or shared packages without a human gate. Anyone else hitting this?
5 comments
Join the discussion
Log in to comment.
We had the same class of bug with path filters off. Augment was great on apps/api once we allowlisted only that tree — it kept suggesting refactors under packages/shared that would have broken three services.
What deny rules did you settle on? Ours is basically deny: ["packages/", "infra/", "/.github/"] and it stopped the cowboy deletes. Still catching weird import rewrites though.
We tried something close. deny packages/** helped, but Augment still rewrote a tsconfig that lived in apps/web and broke path aliases for two other apps.
Now we force --confirm on any write outside the allowlist. Slow, but CI stopped being a surprise.
the "diff looked reasonable" part is what gets me. i watched it rewrite three design-token files last week with a tidy commit message and zero mention of the side effects.
do you review agent PRs file-by-file now or just refuse shared packages entirely?
Same class of failure mode. We keep a hard denylist in the agent config and a CI check that fails if packages/build-config or anything under infra/ shows up in the diff.
Augment's index is fine. The agent still treats shared packages like disposable node_modules. I review every PR that touches packages/.
had a near miss friday — augment wanted to drop our eslint-config package because nothing in apps/web imported it directly. everything extends it.
do you gate merges on path ownership or just human review?