Debug a Failure
Start with the symptom, not a guessed file:
nbx search "expired session retries after refresh" --intent debugInspect the suspect
Section titled “Inspect the suspect”nbx def refreshToken --include-contentCheck the definition, direct callers, and dependencies before deciding where the fault lives.
Ask a precise graph question
Section titled “Ask a precise graph question”When the returned context leaves one relationship unclear, query it directly:
nbx query "MATCH (caller:CODE_SYMBOL)-[r:CALLS]->(target:CODE_SYMBOL) WHERE target.name = 'refreshToken' RETURN caller.name, type(r) LIMIT 20"Confirm with runtime evidence
Section titled “Confirm with runtime evidence”Noodlbox explains code structure. Use logs, tests, traces, and a reproducer for failures that depend on runtime state.
Ask your agent:
Use Noodlbox to trace this symptom to its entry points and shared dependencies. Then tell me what runtime evidence would confirm the cause.