About CRUX and the beta
CRUX is built by one founder, with CRUX's own workflow. Every change starts as a task in the tracker and goes through the same steps you would set up for your team.
Why CRUX
Most of what a coding agent needs to know about a project is already in the tracker: the task, its parent and the decisions already on it. Yet every agent session starts from zero, and each person writes their own prompt. CRUX lets the agent read that context over MCP and gives each status in your workflow its own instructions, so nobody writes a prompt. A person approves the result at the checkpoints that matter.
What the beta means
- Billing is off. Nothing is charged and no card is asked for. Every organization gets an email at least 30 days before billing starts. The prices are on the Pricing page.
- Things may change. Screens, steps and the plugin can change between releases. The plugin's changes are in its changelog.
- Found a bug? Click the bug icon in the bottom-right corner of any page, write to [email protected], or, for the plugin, open an issue on GitHub. I usually answer within one working day.
What comes next
- Step-by-step guides for connecting each tracker, and a quickstart from sign-up to your first pipeline run.
Follow and ask
- Live state of CRUX: the status page.
- Questions and ideas: GitHub Discussions or the contact page.
- CRUX on X and GitHub.