start using Rust with your agents
sign up, open a project, and add Rust to its setup script in settings → server.
rust is the language where a model writing code without a compiler is least useful, and where a project with a toolchain installed helps most. borrow checking is not something to be reasoned about from a distance.
what agents do with it
once the setup script has run, cargo, rustc and rustup are in the sandbox's path. agents type check with cargo check while iterating, build with cargo build, run the suite with cargo test, and run a binary crate with cargo run. rustc's diagnostics often name the exact change to make, so the loop is read the error, apply the change, compile again, until the crate builds for real rather than plausibly.
the matching skill
rust ships with a skill of the same name. it covers building and testing, running a binary crate, checking without a full build, and managing toolchains and components through rustup. skills are versioned documents that load only for the agents you assign them to.
example tasks
- 01
this function will not compile. make it work without cloning everything.
the agent reads the borrow checker's diagnostic in the conversation's sandbox, adjusts the lifetimes, and checks after each change until it compiles cleanly.
bashreadedit - 02
add the feature and prove the test suite still passes.
it writes the code, type checks while iterating, then runs the full suite in the conversation's sandbox and reports the results rather than the intent.
writebashgrep
what to know before installing
the project needs a sandbox, and rust builds are cpu and memory hungry, so a large crate graph is a reason to pick the standard size or larger. the setup script installs cargo, rustc and rustup once on each new sandbox.
how to install Rust
Rust goes in the project's setup script, not once per team and not on your laptop.
- give the project a sandbox
Rust runs in each conversation's sandbox, on your team's own sandbox provider account. an owner or admin connects a provider once on the team's providers page, then picks it and a default size for the project, at creation or later in settings → server. a project with no sandbox has nowhere to run it.
- add it to the setup script
settings → server holds the project's setup script, a bash script that runs once on each new sandbox, in /project, with sudo. add Rust's install commands there and save.
- the next sandbox runs it
the script runs when a conversation's sandbox is created or reused, on the conversation's first turn. settings shows the last run with its exit code and output, and a failed run leaves the sandbox usable rather than blocking the project.
- agents use it through bash
from then on every agent in the project reaches Rust with the bash tool, on the same filesystem as the checkout they are working in. the conversation's sandbox keeps it between turns, sleeping when idle and waking with the next one.
where Rust actually lives
each conversation in a project gets its own sandbox on your team's sandbox provider account, and the project's setup script in settings → server decides what is on it. two projects never share a filesystem, so a version pinned for one client cannot collide with another's.
the sandbox provider bills its machine time to your team's account while it runs, and aldena adds nothing. the sizes are on isolated projects, and what agents may run in the sandbox is governed by the project's tool permissions.
faq
what does installing rust on a project give the agents?
cargo, rustc and rustup in each conversation's sandbox. agents build with cargo build, test with cargo test, type check quickly with cargo check, and manage toolchains and components with rustup, all through the bash tool.
why is rust a good fit for an agent with a compiler?
because rustc's diagnostics are unusually specific, often including the suggested fix. an agent that can compile gets told which lifetime is too short and where, which turns guesswork into a mechanical loop of read the error, apply the change, compile again.
does cargo check help an agent in a project?
yes. cargo check is much faster than a full build, so an agent that type checks while iterating and builds only when it is ready spends less of the project's time and gets answers sooner.
is there a matching skill?
yes. rust ships with a skill of the same name covering cargo build, cargo test, cargo run, cargo check, and managing toolchains with rustup. skills load only for the agents you assign them to.
spin up your first project.
one project per client, product, or piece of work, staffed with intake, requirements, build and code review agents.
