start using .NET with your agents
sign up, open a project, and add .NET to its setup script in settings → server.
.net on a project is the sdk on a real machine, which means an agent can compile rather than describe. once the setup script has run, the dotnet cli is in the sandbox's path for every agent in the project.
what agents do with it
the loop is restore, build, test, repeat. an agent runs dotnet build and reads roslyn's diagnostics with their exact file, line and symbol, fixes the cause, and builds again. dotnet test runs the suite in the conversation's sandbox, dotnet run starts the app so a route can be exercised, and dotnet new scaffolds a new .net project when something genuinely new is needed. because the checkout is already in the sandbox, none of that involves moving files anywhere.
the matching skill
.net ships with a skill of the same name. it carries restore and build, running, testing, and scaffolding. skills load only for the agents you assign them to.
example tasks
- 01
the solution will not build after the package upgrade. fix it.
the agent builds in the conversation's sandbox, reads the breaking change roslyn points at, updates the call sites, and rebuilds until it is clean.
bashreadedit - 02
add tests for the new service and run them.
it writes the .net test project files, runs dotnet test in the sandbox, and reports the actual pass and fail counts rather than an assurance.
writebashgrep
what to know before installing
the project needs a sandbox, and .net builds are memory hungry, so a large solution is a reason to pick the standard size or larger. put the sdk install in the setup script, and settings → server shows its last run with the exit code and output.
how to install .NET
.NET goes in the project's setup script, not once per team and not on your laptop.
- give the project a sandbox
.NET 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 .NET'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 .NET 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 .NET 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 .net on a project give the agents?
the dotnet cli in each conversation's sandbox, on the current lts sdk line. agents restore and build with dotnet build, run with dotnet run, run the suite with dotnet test, and scaffold with dotnet new, all through the bash tool.
does the agent get real compiler errors?
yes, and that is most of the value. roslyn names the type, the member and the line, so an agent iterates against real diagnostics instead of producing code that compiles in principle and fails when someone opens the solution.
can an agent run a .net test project in its sandbox?
yes. dotnet test runs in the conversation's own sandbox against the checkout that is already there. if the app needs a database, install postgresql or mysql in the same project and the tests run against a live instance.
is there a matching skill?
yes. .net ships with a skill of the same name covering dotnet build, dotnet run, dotnet test, and scaffolding with dotnet new. 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.
