Status & Roadmap
Agent Studio is in early alpha, built in public. Today you build it from source — a central Task Server, Agent Studio in the browser and Agent Runners on any host — and an early beta is coming to make that setup easier.
- Early alpha
- Early beta upcoming
- Build from source
This page is the honest current state: what early alpha means, what the early beta will change, and where to follow the work. No hosted service, and no release date is promised.
Where the Project Is Today
Agent Studio is an early-alpha, open-source project built in public. It is real and used daily to build itself, but it is not a polished, hosted product yet. The honest picture is simple: you build it from source and run it yourself.
Early alpha
Moving fast in the open. Expect rough edges, breaking changes and manual setup.
Build from source
Clone the repository and build the Task Server, Agent Studio and agent-runner yourself.
Owned execution
No hosted runtime. You control the hosts, credentials and network boundaries.
- Build from source: there is no installer and no hosted account — you clone the repository and build the binaries.
- Three binaries: a central Task Server, the Agent Studio web app in the browser, and an Agent Runner on any host.
- README is the source of truth: setup commands live in the repository and evolve with the code, so the site never promises a release package that does not exist.
- No hosted service: nothing runs on our servers; execution stays inside environments you deliberately configure and operate.
Early Beta: What Will Change
An early beta is on the way. Its focus is making the project easier to adopt without changing what it is: still remote-first, still open source, still your own execution boundary. It will be announced when it is ready — no date is promised, because a date would be a promise the alpha cannot honestly make yet.
- Easier setup: a smoother path from clone to a running Task Server, studio and runner.
- Clearer onboarding: guided first-run steps instead of reading the whole README first.
- Remote hosts as first-class objects: a host registry, per-CLI quota and per-project execution assignment.
- Announced when it is ready: the beta ships when the setup story is genuinely better, not on a marketing schedule.
How to Follow Along
The work happens in the open. The fastest way to track progress, shape direction and know when the early beta lands is to watch the repository and read the news page.
GitHub
Source, issues and releases — the live record of the project.
News
Short posts on product boundaries and notable changes.
Get in touch
Tell me what you are building; it helps prioritize the beta.
- Star and watch the GitHub repository to follow commits, issues and releases as they happen.
- Read the News page for product-boundary thinking and notable changes.
- Building with Agent Studio? Get in touch — real use cases shape what the beta prioritizes.