A good fit for
- → Developers who want agent work inside an editor
- → Coordinating repository changes across isolated workers
- → Teams connecting code review to deployment telemetry
Know the limits
- → Projects beta access and enterprise features are not universal.
- → Self-hosted execution does not automatically make model inference local.
- → Rollouts can propose a revert but does not autonomously merge or roll back in the reviewed release.
Your first useful workflow
Choose the environment
Decide between local, cloud and self-hosted execution; list what each may access.
Start with one change
Give an agent a small issue with a failing test and acceptance criteria before trying parallel delegation.
Connect evidence
For Rollouts, confirm that deploy events and actual telemetry support the monitoring plan.
The practical take
Choose where tools execute before asking a coordinator to delegate work.
Sources & evidence
Capabilities above are summarized from these official documents. Workflow suggestions are editorial guidance, not a claim of measured product superiority.