Built on Fedora CoreOS, SodaOS integrates the infrastructure for continuing AI development. People authorize objectives and operating policy; the factory automatically picks up ready, authorized issues and coordinates planning, coding, review, corrections, checks and native merge. The normal loop is fully autonomous under standing policy; human approval gates are optional. Forgejo owns repositories, issues, pull requests, reviews and CI records. Humans and factory roles share persistent Podman Projects with separate accounts, checkouts and executions. Familiar editors, terminals and SSH support development and intervention.
Start with your task
| You want to… | Start here |
|---|---|
| Understand the factory and human projects | Product model |
| Install on hardware from an ISO | Install on premises |
| Install in a compatible VM | Deploy to a cloud or VM |
| Prepare a Docker deployment | Run Soda OS with Docker |
| Configure private access and the factory | Operator setup |
| Authorize and inspect the first agent task | Software factory walkthrough |
| Review a candidate and govern its merge | Collaboration |
| Manage runs, capacity or interruption | Administration |
| Manage human and agent access | People and access |
| Develop or intervene manually | Projects and workspaces |
| Connect an editor and use Git | Connect and develop |
| Protect persistent data and retained results | Backups and restoration |
Your first authorized task
- Deploy Soda and configure private access, Forgejo and the selected agent profile.
- Choose a private repository and write an issue with a clear expected outcome.
- Establish standing repository policy, appliance capacity and provider sponsorship. Soda picks up issues created by authorized maintainers automatically; objectives without trusted authorization need adoption.
- Observe the bounded attempt and inspect its pull request, CI and current review.
- If a repair produces another commit, check its new verification.
- Supply human approval where policy requires it, then confirm the policy-governed native merge or resolve the intervention request.
- Confirm the run's recorded cleanup independently of its terminal outcome.
Follow the factory walkthrough for the workflow and operator commands. An issue, label or successful process exit alone is insufficient authorization or verification.
Choose the right interface
Forgejo owns code, permissions and collaboration. The factory coordinator owns automatic progress under the accepted requirements and grants. The operator command inspects recorded runs, stops one run and reconciles outstanding execution; it does not admit or launch work. The Soda Dashboard provides repository and human project access. Cockpit is for host administration. The CI runners supply Forgejo verification capacity.
For manual development, follow First connection, join a persistent project explicitly and use its displayed account and connection details. A human project account is separate from a factory execution identity.
Platforms
Choose x86-64 hardware or a matching VM. Run Soda on hardware you control or a compatible private cloud VM with a documented boot path and private client access. WSL2 support for x86-64 Windows gaming PCs is planned for a future release, with no WSL2 download. Use the full hardware or VM paths at launch.