On this page
Assign work with clear boundaries
Start with one concrete outcome and split it into tasks that can be checked independently. One agent might inspect a failure, another prepare a small fix, and another review the result. Avoid simultaneous edits to the same files unless the agents coordinate their changes.
- Give each task an owner, a file scope and an acceptance check.
- Keep shared contracts small and agree on them before parallel implementation.
- Use isolated branches or worktrees when changes need independent review.
- Have one person integrate the changes and run checks on the combined result.
Connect the tools you actually have
Crux supports configured API providers and installed coding CLIs. The desktop app uses Rust commands to run local processes and terminals. A browser session does not automatically have the same filesystem or process access as the desktop app.
Each provider needs its own valid configuration. Model availability, tool support, pricing and usage limits depend on the account and provider. A missing CLI or exhausted account should produce a clear state instead of a simulated response.
For a single local model, see using Ollama with a code editor. Start with one working provider before adding routing or more agents.
Integrate and verify the combined result
Inspect the diff from each task, resolve overlapping assumptions and run checks after integration. Concurrent text merging does not prove the application works. Watch for changed APIs, missing migrations, secrets in generated files and scripts that modify more than their assigned scope.
Keep long-running work cancellable. Record which provider performed each attempt and whether it emitted output or used tools. A failed response can still have changed files or started a process; replaying the task elsewhere may duplicate those effects.
Treat usage limits as account boundaries
Automatic fallback should be opt-in, bounded and visible. Changing providers can change cost, privacy handling, model capability and tool behavior. Only retry a quota failure automatically when the failed attempt has not produced output or performed work that could be repeated.
A teammate's subscription is not a transferable token balance. An owner may authorize supported execution on their own account, subject to the provider's terms, with explicit budgets and a way to revoke permission. Crux's shared editing channel alone does not authorize that spending.
During the private alpha, join the waitlist to request access. No particular provider or quota-sharing arrangement is guaranteed by joining.
BUILD SOMETHING TOGETHER
Your team.
Your agents.
One workspace.
Bring your people, code and context together in Crux.
Join the waitlist