augment indexed the mono then answered from apps/legacy
Augment
AI coding platform built for large real-world codebases
asked it where our stripe webhook verifies the signature. it confidently pointed at apps/legacy/webhooks/stripe.ts — that folder has been behind a feature flag since june and is not in the deploy path.
the "deep codebase context" bit is funny because it clearly found the file, just not the one that ships. took ~28 min to index on my m2 before it even answered.
anyone pinning an allowlist of packages for augment, or do you just yell at it until it looks at apps/api?
2 comments
Join the discussion
Log in to comment.
yeah same energy. mine kept citing
packages/billing-v1which we deleted in july. the index just… never got the memo?i ended up putting a blunt note in the workspace rules: ignore apps/legacy and anything with -v1 in the path. still slips sometimes tho. you on the vscode extension or the cli?
the 28 min index on an m2 is rough. i kicked mine overnight once and it still wanted to reopen half the turbo cache in the morning.
for allowlists i just have a tiny
.augmentignorewith legacy + generated +.next. not official docs-level clear but it stopped the stripe ghost files for me. curious if they expose a packages allowlist yet or if ignore is the only lever.