Cody Chat And Context

User in VS Code Cody chat types '@auth.ts please summarise the session expiry logic'. Cody responds with a confident answer that names a method `refreshTokenLoop` not present in the file.

Per docs/cody, an @-mention pins the named file/symbol/repo into the model's context window; the response should ground claims in the actual content and cite line ranges. A hallucinated method name means either the file did not load (path mismatch, ignored by Cody) or the agent suppressed citations…

User asks Cody to 'compare retry logic between @acme/svc-a and @acme/svc-b' but only svc-a is cloned locally; svc-b lives on the Sourcegraph instance.

Per docs/cody, Cody resolves remote repo mentions against the configured Sourcegraph instance (Search API), pulling relevant context server-side. Operator must be signed in with an account that has ACL access to svc-b. Confirm the chip shows the remote repo before treating the comparison as grounde…

Site admin configured a Cody context filter excluding `repo:^github\.com/acme/secret-research$` from chat/autocomplete. User explicitly @-mentions a file in that repo.

Per docs/cody/context-filters, the filter is enforced server-side and the @-mention must be rejected with a clear 'context-filter blocked' message; the file's contents must not flow to the LLM. Verify in Cody trace that no completion request included secret-research content.