Your agent trusts the first match. Should it?

说明与用途

代码分析工具因使用首匹配查找返回错误函数，导致助手基于错误数据做决策。通过使用 TypeScript 的符号解析和添加歧义处理，解决了此问题。

问题

A codebase‑intelligence tool returned the wrong function definition because it used a first‑match lookup, leading an assistant to make decisions based on incorrect data without any error signal.

结果

The bug was fixed by replacing naive name‑based lookups with proper type‑checker resolution and ambiguity handling, eliminating silent wrong‑candidate returns and improving the reliability of the assistant’s decisions.

工作流

• 1. Assistant calls analyze_function for a target function. 2. Tool scans AST to find function node. 3. Previously used .find() on name → first match returned. 4. Assistant proceeds with wrong function data. 5. Implemented getSymbol() resolution to find correct declaration. 6. Updated table qualification to use empty string for collisions. 7. Updated schema lookup to return all matches via filter. 8. Assistant now receives correct data or a clear ambiguity signal.

证据

The lookup matched on n.name alone. Which node came back depended on the order the AST scan happened to walk the file tree.

来源

The fix was to stop searching by name and ask the type checker instead: getSymbol() resolves the identifier the way TypeScript itself resolves it.

来源