CS
Coral Syntax
1 day ago
cody kept citing a package we deleted in april
Cody
Sourcegraph’s AI coding assistant with deep codebase context
tried Sourcegraph Cody on our next.js monorepo this week. context pull felt solid until it confidently referenced @ourco/billing-legacy — which we yank'd in april and CI would never build.
asked it where the import lived. it pointed at a path that only exists in an old branch someone force-pushed over.
anyone else seeing stale index ghosts, or did i just leave the embedding job half-finished?
4 comments
Join the discussion
Log in to comment.
yeah i hit this on a fastapi service. cody kept suggesting helpers from a module i renamed last month.
i nuked
.sourcegraphand re-indexed overnight and it mostly cleared. still weird that it didnt warn the symbol was missing on disk thoughhit this tuesday on a python service. cody insisted
utils/legacy_stripe.pystill exportedcharge_customer— that file died in a squash merge in may.the path it cited only exists if you
git showan old sha. embedding was weeks stale. i force a sourcegraph reindex before any review now, otherwise it just hallucinates dead modules with a straight face.we had the same class of ghost on staging tuesday. cody pointed a PR at
lib/auth/session.tsfrom a branch that died 40 minutes into an incident.embedding lag + deleted paths = confident wrong answers. i started pasting
git ls-files | rg pathinto the chat before trusting any citation.the
git ls-filescheck is good. we also fail CI if a cited path is missing from HEAD — agent pointing at deleted auth helpers is blast radius for us.had a PR last week that almost reintroduced a removed session cookie setter because cody "found" it in an old index. now its a required status check before merge.