vibehacker
Discuss
Flint Meadow
1 month ago

Augment indexed for 40 min then edited the wrong package

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

Tried Augment this week on our pnpm monorepo (12 packages, TypeScript). Index finally finished. Asked it to fix auth middleware in apps/web.

Diff landed in packages/shared instead. Screenshot before I closed the window.

Is .augmentignore supposed to fence this, or does everyone just run one package at a time?

6

6 comments

Join the discussion

Log in to comment.

Log in
  • Samira Okonkwo

    Same class of bug as Continue inventing imports across packages. I deny-list every packages/* path for edit tools and only unlock one package per run. Slower. PRs stay reviewable though.

    • Remy

      I put a hard timeout on Augment agent runs after it burned about $12 overnight once. Also check your root tsconfig paths — mine made the indexer treat the whole workspace as one app.

  • Tara Nguyen

    I burned about $9 of Augment credits on a monorepo index that then patched packages/billing when I asked for apps/dashboard.

    .augmentignore helped for junk dirs but not sibling packages. I now open Augment with only one package in the workspace window — slower, but the $20/mo seat stops eating itself. Anyone found a real fence that works with pnpm workspaces?

    • Marcus Lee

      no real fence that I've found with pnpm workspaces. .augmentignore is for junk dirs, not sibling packages.

      what worked for us: open Augment with packages/billing as the only folder in the VS Code window, and a root .cursorignore-style deny on packages/*/node_modules. slower indexing. diffs stay inside one package. the $20/mo seat stops eating itself.

      • Devon

        kill-list for me now includes packages/*/src unless the ticket names the package in the first line.

        opened the whole workspace once on a friday. Augment "fixed" a type in shared and broke three apps. CI green because the tests live in the package it didn't touch. single-folder window is annoying. still cheaper than the rollback.

  • Jonas Kessler

    I tried the single-folder trick with Augment on an Nx monorepo. Indexing dropped from 40 min to ~8. Then it still proposed a change in libs/shared-auth because the import graph pulled it in.

    .augmentignore does not understand workspace boundaries. Until it does, treating the agent like it has a monorepo is the bug. One package per window, or don't bother.

More like this

View all