RobOS for Teams
Start here if you are a tech lead or evaluator deciding whether RobOS fits your team. These pages cover what problem RobOS targets, what is built today, and how a team sets it up.
Evaluate
- Why RobOS states the problem, the approach, what exists in the repository, and the limits.
- What sets RobOS apart covers the main RobOS features in more depth.
- PR Review Theater describes the staged pull request review.
- Review & governance is the section on reviewing agent work.
- Walkthroughs and proof of work collects recorded walkthroughs of RobOS apps.
- Architecture shows how the apps and libraries fit together.
Set up a team
- Build apps as a team walks a team through planning, implementing, reviewing and merging with Task Planner, Task Implementer and Agent Code Review.
- Company setup is for a team with existing repositories and a task tracker.
- New company is for a team starting from nothing.
- Personas lists which apps to open first for four common jobs.
- Agent tiers explains which agent CLIs RobOS can run and which model settings do something today.
Check before you adopt
| Question | Short answer | Details |
|---|---|---|
| What platform does it need? | The install scripts use apt and register the Electron apps in the GNOME app launcher. | Get started |
| Is there a shared server for company settings? | No. Setup is stored in files on each machine and in .robos/ folders in your repositories. | Company setup |
| Does it include a model or an agent? | No. RobOS runs agent CLIs you install and sign in to yourself. | Agent tiers |
| Does it read our identity provider? | No. The “Sync Directory” button in Group Manager writes sample data. | Company setup |
| What is planned but not built? | Listed on the roadmap. | Roadmap |