Back to Vault
Coding Agents
Tier 4
Roo Code
Summary
A fork-descendant of Cline that pushed multi-mode agent UX further: custom modes with per-mode permissions and prompts, letting one agent switch personas (architect, coder, reviewer) with different tool rights.
Key Takeaways
- Per-mode permission sets: the reviewer persona cannot write files
- Custom modes are user-defined harness configurations
Reliability Note
Official repository; URL redirects to the renamed org (RooCodeInc).
Flows informed by this source
1Harness Engineering
Design the Permission Approval UX
Design approval prompts users actually read: diffs, risk framing, scoped grants, and pacing that prevents approval fatigue.
01Audit the current approval moments
02Rebuild the prompt content
03Make friction proportional to risk
+1 more steps to Done
Best forbuilders who have shipped a basic app before
4 steps60-90 minutesIntermediate