Project Health
Use Devtools health and Index Lint to understand whether Crux can see, connect, and check your authored AI system.
Project Health shows whether Crux can understand your authored AI system well enough to help you debug it.
It answers practical questions:
- Can Devtools see my prompts, agents, tools, flows, memory, workspaces, and evals?
- Are those pieces connected the way I intended?
- Can runtime traces link back to the source that authored them?
- Is Crux warning me about missing schemas, invisible handoffs, uncovered definitions, or unsafe writes?
You usually do not call the indexer directly. Run local tooling and open Devtools:
crux devCrux builds the Project Index underneath. Most users only need the health view and lint findings; the raw index contract is reference material.
What Crux Checks
Crux checks authored definitions such as prompts, contexts, tools, agents, flows, memory, workspaces, quality suites, guardrails, routing primitives, and compositions.
For each definition, Devtools can show:
- where it is authored
- which other definitions it uses
- whether runtime traces can link back to it
- whether Crux only partially understood it
- whether Index Lint found a design issue
Diagnostics vs Lints
Diagnostics and lints are intentionally separate.
| Signal | Meaning | Example |
|---|---|---|
| Diagnostic | Crux could not fully understand or process something. | A file failed to parse, a package import failed, or semantic enrichment was unavailable. |
| Lint finding | Crux understood the authored graph and found an actionable design issue. | A tool has no inspectable input schema, or a handoff target is not visible. |
Treat diagnostics first when they prevent Crux from seeing the project clearly. Treat lint findings as product-quality feedback about the AI system Crux could see.
Why The View Can Change After Startup
During crux dev, Crux shows a fast first view quickly, then enriches it with deeper TypeScript understanding when available. A snapshot may briefly include an index.source_only diagnostic while that deeper pass is unavailable or still running.
That is expected. When enrichment succeeds, Crux clears the marker and updates Devtools with richer source refs and relations.
Next Step
Read Index Lint to configure, fix, and suppress authored-graph findings.
For Authors And Tooling
Most projects do not need these pages. Use them when you are building tooling, Devtools surfaces, or a package that teaches Crux about custom wrapper APIs.
- Reference: Project Index
- Reference: @crux/indexer
- Advanced: Writing an Indexer Extension