Query and Router
Read the TanStack Query cache, follow data to the screen, and check navigation.
Every example ran against apps/router-demo, opened with
agent-browser --session router-check open http://localhost:3030/.
Query
List the cache and pick an exact key:
npx @genie-react/cli call query_list --session router-check '{}' \
--fields queryHash,status,fetchStatus,observerCount[1]:
- {queryHash:"[\"greeting\"]",status:success,fetchStatus:idle,observerCount:1}Wait for a query instead of sleeping:
npx @genie-react/cli call devtools_wait --session router-check \
'{"condition":"query-settled","queryKey":["greeting"],"timeoutMs":10000}'query_get returns one entry with its data, status and observers.
Follow data to the screen
When the cache has the right data but the screen does not, check each step. Open a window, write to the cache, and read what the observer delivered:
npx @genie-react/cli call react_clear_renders --session router-check '{}'
npx @genie-react/cli call query_set_data --session router-check \
'{"queryKey":["greeting"],"data":{"greeting":"cache probe","fetchCount":0}}'
agent-browser --session router-check get text '[data-testid="query-data"]'
npx @genie-react/cli call query_notifications --session router-check '{"limit":1}' \
--fields changedResultFields,deliveryReason,renderEventIdscache probe (fetch #0)
[1]:
- {changedResultFields:[data,dataUpdatedAt],deliveryReason:tracked-field-changed:data,renderEventIds:[render:5:3]}The observer tracked data, the write changed it, and React rendered event render:5:3. If
renderEventIds is empty, the component never re-rendered. If no notification arrived, the
component does not track the field you changed. Restore the real data with query_refetch.
query_simulate_state holds a query in pending or error. See
validate UI states.
Router
Navigate the way the app does, then check that Router and the browser agree:
npx @genie-react/cli call router_navigate --session router-check \
'{"to":"/suspense","search":{"source":"docs"}}'
npx @genie-react/cli call router_get_state --session router-check '{}' --json \
| jq -c '{pathname,searchStr,status,locationSync}'
agent-browser --session router-check get urlok: true
outcome: arrived
requestedHref: "/suspense?source=docs"
pathname: /suspense
href: "/suspense?source=docs"
settled: true
pendingWork: []
{"pathname":"/suspense","searchStr":"?source=docs","status":"idle","locationSync":"matched"}
http://localhost:3030/suspense?source=docsrouter_navigate returns once the navigation settles. locationSync: "matched" means Router state
and browser history agree. A mismatch means they did not. router_build_location resolves a
destination without navigating, and router_list_matches shows the matched routes and loaders.
Debug renders and effects
Find why a component rendered and why an effect keeps running.
What is an agentic React tool? What your coding agent can't see from the browser
An agentic React tool is one your coding agent runs from the terminal and reads as text. Real runs show what a browser driver saw in a React app, and what Genie added.