Download and install Agent Studio
Choose a Windows or Linux setup, verify the download, then finish the first-run steps in Studio.
Release availability is checked during each website build. Download controls appear only when both installers and SHA256SUMS are published.
First release pending
No verified installer release is available yet. The download links stay hidden until the release contains both installers and SHA256SUMS and the website is republished.
View release historyVerify the release files
Download the executable and SHA256SUMS from the same latest release. Compare the file hash before running setup. The Linux one-line command does this check automatically.
On Windows, compare the printed hash with the agent-studio-setup.exe line in SHA256SUMS. Run the executable only if they match.
The Windows exe is currently unsigned. SmartScreen may show “Windows protected your PC”; check the release source and matching SHA-256 first, then choose More info → Run anyway only if you trust this release.
Linux: grep ' agent-studio-setup$' SHA256SUMS | sha256sum -c -Windows PowerShell: (Get-FileHash .\agent-studio-setup.exe -Algorithm SHA256).HashCheck your machine
The default installation runs a one-box Docker stack with Studio, Task Server, Engine and one Linux runner. The installer itself needs no host .NET or Node.js.
- Windows x64: Docker Desktop running with the WSL 2 backend and hardware virtualization enabled.
- Linux x64: Docker Engine running with Compose v2. Check docker compose version and docker info before starting.
- Have at least 20 GiB free for one-box or runner-host journeys. The installer preflight checks the selected journey and reports a recovery action for failed prerequisites.
Choose where Studio and agents run
A one-box installation is the shortest path to the browser. A separate Linux agent host joins an existing Task Server and needs its own repository and provider access.
Windows only
Run the Windows setup executable with Docker Desktop and WSL 2. The default Docker journey starts Studio and a Linux runner on this machine.
Linux only
Run the verified Linux setup binary on a Docker Engine host. The default journey starts the same one-box stack.
Windows Studio + Linux agent host
Use a remote Task Server, attach Windows Studio with a server URL and protected token file, then join the Linux runner with its join token. Follow the multi-machine guide for network and authority setup.
What setup asks and why
The executable presents the journey, prerequisites, storage, pinned release, human identity, project origin, first runner and budgets before it changes services. For a remote connection it also needs the authority URL and a protected token file.
- Choose one-box for one machine, join-host for a Linux runner, or attach-studio for a Windows client. Preflight checks only the prerequisites for that journey.
- Set the canonical Git repository origin so a runner can fetch the project you intend to use. Give that host access with a suitable Git credential, such as a scoped token or repository deploy key; Studio does not create those credentials for you.
- Choose finite coding and review budgets. Provider CLI login is completed on the execution host, outside the installer, before a real coding task can run.
- The first owner account is created in Studio using the installer owner code while bootstrap is open. Do not put secrets in command arguments or answer files.
Finish the first run in Studio
A healthy browser page is the starting point, not proof that an agent can work. Open the local URL printed by setup (normally http://127.0.0.1:4011) and complete these checks.
- Create the first owner account with the one-time owner code, then sign in.
- Register the project’s canonical Git origin. Confirm that the assigned host can fetch it with the configured token or deploy key.
- Install and sign in to the chosen coding-agent CLI on the runner host. Check its provider access outside Studio.
- In Workspace Settings → Execution Hosts, check installation checkpoints, host connection and capability readiness. Then try one small task and inspect its recorded result.
Use the named preflight failure
Keep the first failed check and its recovery action. Rerun the same installer version after fixing the cause; interrupted installs resume without replacing the installation identity.
- Windows: if Docker or WSL 2 is unavailable, start Docker Desktop with its WSL 2 backend and run docker info again. The Docker path does not ask for administrator rights.
- Linux: if Compose or the daemon is missing, install or start Docker Engine and Compose v2. Check permissions for the user running setup.
- Remote setup: an invalid join token fails before preflight. A mismatched server URL, unreachable authority or untrusted HTTPS certificate must be corrected before joining.
- If a release asset is reported missing, check the requested version against a published release; a mistyped version is not pinned by setup.
- Token files must be readable only by their owner. Move them off Windows-mounted /mnt/c paths when Linux permissions cannot be enforced, then set mode 0600.