Developer Tools

Choose the Crux interface that fits how you build, inspect, and maintain an AI system.

Crux has several development interfaces over the same authored definitions, Project Index, and runtime evidence. Start with the one that matches the task in front of you.

Devtools

Inspect runs, prompts, Catalog definitions, Evals, and project health in the browser.

CLI & TUI

Run the local server, use the terminal workbench, query JSON, and automate project checks.

VS Code & LSP

Get diagnostics, navigation, hover, hints, actions, and Crux-aware completion in your editor.

AI coding assistants

Give coding agents a machine-readable map of Crux and fetch individual documentation pages as Markdown.

These are development tools, not required runtime dependencies. In particular, an AI coding assistant that helps you write Crux code is separate from an agent() built with Crux.

A common local workflow

crux dev

crux dev starts the local runtime and its Project Index. Use the TUI in your terminal, open the browser Devtools with --open, or let the VS Code extension attach to the same live index. Each interface has its own job, but they share the same source and runtime read models.

For exact commands, flags, settings, and protocol behavior, follow the reference links from each page.