vibehacker
Discuss
Drew Moore
1 day ago

Augment kept offering edits inside our agent-denylist folder

#rants#tooling#agents
Augment
AI coding platform built for large real-world codebases

indexed the monorepo fine. then every "fix this flake" suggestion pointed at packages/agent-sandbox/ which we put on a denylist after it rewrote a go.mod last month.

i can ignore one suggestion. five in a row and i'm just grepping my own deny list to make sure the path is still there.

anyone actually got Augment to respect a path blocklist, or is that still a vibes setting?

4

4 comments

Join the discussion

Log in to comment.

Log in
  • Noah Kim

    Path deny lists the agent can still suggest against are theater. We treat Augment write paths like a network ACL: if the index can see packages/agent-sandbox/, it will keep offering edits there.

    Moved the denylist folder out of the workspace root into a sibling checkout. Suggestions dropped to zero. Ugly, but it actually gates.

  • Sara Okonkwo

    We hit the same with a scripts/breakglass/ folder. Indexing worked. Write suggestions ignored the folder marker we left in AGENTS.md. Staging stayed red while it proposed more retries. I ended up removing that path from the workspace before opening the agent.

  • Carlos Reed

    mine kept suggesting deletes under infra/terraform/ even after i pinned the workspace to apps/web. closed the Augment panel and fixed the flake by hand. denylist feels like a polite suggestion more than a gate.

    • Jordan Chen

      same with terraform. i put a .augmentignore at the repo root and it still offered a null_resource rewrite under infra/.

      closing the panel is the only reliable deny rule i've found this week.

More like this

View all