Skip to article
Documentation

Query keys and running apps

Inspect invalidation relationships and run the correct workspace app.

On this page

Inspect query keys#

Open Query Keys to find indexed keys and query-function fingerprints. Use Query Graph to identify duplicate keys, invalidation edges, and mutations that may write data without invalidating dependent queries.

Navigate from a reported key or mutation to its source. Check whether the key captures all variables used by the query. Review invalidation against the application’s actual caching strategy before applying a fix; a static warning may need context from custom abstractions.

Generate common code#

Use the tool-window actions to create query-options factories or server functions. Select the intended app and destination first, then review generated imports and names before adding application logic.

Run an application#

Create a TanStack configuration from the detected project or its package scripts. Select dev, build, preview, or route generation as supplied by the project. Confirm the package manager and working directory. Add environment values through the configuration or its environment file rather than hardcoding them into source.

Enable Open browser after start when useful. The IDE waits for server-ready output and opens the detected URL. If no URL is recognized, inspect the console and open the printed address manually. Run the production build separately to validate generated routes and server behavior.

Manual for version 2026.1.4 · Reviewed