Fleet state
Seven agents report into a shared view with real-time event streaming.
Internal Operating System
OngoingWorkflow receipt · prettyfly os
PrettyFly needed a way to see agent state, cost, failure, and handoff without chasing logs across servers.
Inspectable proof
Proof videoOriginal drag
Drag named firstOriginal drag
Agents were running across servers, but health, cost, tasks, and handoffs were split across logs and local state. The system needed one operating surface before more agent work could be trusted.
Agent health lived outside a shared operating view.
Failures could hide until someone checked the wrong place.
Cost controls were separate from the work being done.
Task handoffs had no common surface.
Operating route
Mapped pathOperating Route
PrettyFly built an internal operating surface with fleet state, real-time events, circuit breakers, cost visibility, tracing, and MCP tools for development sessions.
Seven agents report into a shared view with real-time event streaming.
Repeated faults trip the route and make recovery explicit.
Per-agent spend, daily budgets, tracing, and monthly reports sit beside the work state.
Observability and task tools are exposed directly to development sessions.
A raw Node.js HTTP server keeps the coordination layer inspectable.
Supabase JWT handles dashboard access; bearer tokens handle machine communication.
Shipped system
ReceiptShipped System
Your route
Name one route that feels expensive. The diagnostic reads the drag, owner, risk, and next move before anyone recommends a build.