Devtools
Inspect Crux runs, authored definitions, Evals, and project health in the browser.
The browser Devtools is the visual workspace for understanding what Crux authored and what actually ran. It combines runtime traces with Project Index source evidence so you can move between a prompt, its code, and the runs that used it.
Start it locally:
crux dev --openUse Devtools when you want to:
- inspect the exact messages, contexts, tools, and model settings used by a run;
- browse prompts, agents, tools, flows, and their source relationships in Catalog;
- run and compare Evals and review their evidence; or
- see Project Health diagnostics and lint findings.
Devtools guide
Set up local observability and learn the browser workflow.
Project Health
Understand Catalog coverage, source evidence, diagnostics, and lints.
Cloud runtimes
Send development telemetry back from remote and serverless runtimes.
Devtools API
Configure the Core plugin and runtime bridge.
The Devtools UI is distinct from the terminal TUI and from the VS Code extension. They can all connect to the same local process without becoming runtime requirements for your application.