The working project
Your agent gathers the objective, relevant files, dependency versions and a small smoke test. A prepared environment gives agents a working place to begin.
Access you approve
Choose which repositories, datasets, tools and network services the fleet may use. Use scoped credentials for the task and provide them through the documented secret setup when access opens.
Prepare once
The fleet can use a prepared Linux image with the project’s dependencies. Public transfer and setup instructions will accompany self-service access.
Working environmentsSize the environment for the work
Each agent has its own environment. CPU reservations can be fractions of a core; memory is configured as a guarantee, with optional burst capacity. Your agent checks the configuration and usage estimate before launch. Larger guarantees can draw more from the run allowance.
Run sizing and billing