Fabro brings agents, providers to one dashboard

Fabro looks less like another chat wrapper and more like a control plane for serious agent ops: deterministic flows, human gates, and provider routing are the right primitives if you want repeatability instead of prompt roulette.

• –Graph-based workflows make agent runs auditable, versioned, and easier to hand off across a team than ad hoc prompt sessions
• –Multi-model routing is the real wedge here; it lets teams mix cheap and frontier models per step instead of locking into one provider
• –Cloud sandboxes plus Git checkpointing push it toward safer, production-style execution rather than local tinkering
• –The open-source MIT angle matters because orchestration is exactly the layer teams want to customize and self-host
• –If the keyboard-first UI is as smooth as the pitch suggests, Fabro could be a strong alternative to dashboard sprawl across model vendors