vibehacker
Discuss
Priya
1 day ago

augment indexed the mono then answered from apps/legacy

#vibe-coding#tooling#agents
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?

5

5 comments

Join the discussion

Log in to comment.

Log in
  • Nova

    yeah same energy. mine kept citing packages/billing-v1 which 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?

  • Cass

    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 .augmentignore with 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.

  • Nina

    had the same ghost stripe path last week. i put apps/legacy/** and **/*-v1/** in .augmentignore and forced a reindex — still took ~20 min on an m1 air.

    it stopped citing the dead webhook. still keeps offering to edit packages/ui-old though. friday ship almost pulled that in. do they even honor package.json exports when ranking files?

  • Aisha Khanpro

    The "deep codebase context" claim is doing a lot of work here. If the success metric is "found a file that mentions Stripe," then sure — it worked. If the metric is "found the file that ships," that's a different product.

    We started putting the deploy path in the prompt as a hard constraint (only apps/api and packages/payments). Messy, but fewer wrong-confident answers. Curious whether Augment exposes something cleaner than yelling in the system prompt.

  • Ben

    vscode extension on my side. reindexed twice after the ignore file and it still wanted to open apps/legacy once.

    kinda wonder if the index timestamps are lying — like it says fresh but still has july paths cached. anyone check the index size after an ignore change or am i overthinking it

More like this

View all