have to explicitly ask it to check codegraph, otherwise no results

[hkbb2014]

I have to explicitly ask it to check codegraph, otherwise no results

I am using windows 11, opencode with dsv4 flash.

codegraph init -i
codegraph status

Index Statistics:
Files: 28
Nodes: 474
Edges: 922
DB Size: 1.56 MB
Backend: node:sqlite - built-in (full WAL)
Journal: wal

Nodes by Kind:
function 157
import 139
variable 67
route 33
method 28
file 27
class 15
constant 8

Files by Language:
python 26
javascript 1
yaml 1

[OK] Index is up to date

---

In opencode,

If I do not mention about codegraph, it know it should read codegraph index, but there is no results.

I have to explicity ask it to check codegraph, otherwise it will check, but no results

[colbymchenry]

Thanks for the very clear repro and screenshots — those made this a quick diagnosis.

Root cause. Indexed file paths in CodeGraph are stored as project-relative POSIX (e.g. src/foo.py), but the codegraph_files path filter used a plain path.startsWith(pathFilter). When your agent (Gemini Flash, reasonably) decided path="/" meant "project root", startsWith("/") matched nothing — so the tool returned "No files found matching the criteria.", the agent took that as a dead end, and fell back to Read/Glob. That's exactly the contrast between your two screenshots: the case that "explicitly mentioned codegraph" succeeded because the agent happened to omit the path arg there.

Fix (merged in #466, will ship in the next release). The path filter now normalizes the inputs an agent might guess for "project root" ("/", ".", "./", "", "\\") into "no filter", and tolerates leading-/, leading-./, trailing-/, and Windows-style backslashes on subpaths ("src\\components" → "src/components"). Matching is also stricter on the inner boundary (<filter> or <filter>/), so a filter "src" no longer accidentally bleeds into sibling "src-utils/...".

Validated across macOS, Linux (Docker), and Windows (Parallels VM), plus end-to-end through an opencode TUI session — codegraph_files [path=/] now returns the full project tree and the agent answers without touching Read/Glob.

I'll leave this closed via the merge; if you still see the symptom after the next release lands on npm, please re-open with the new version and we'll dig in further.