Agent efficiency
Read-only aggregate: how AI OS routes agents (exam permissions + ledger success). No per-task detail.
Coverage
Connected modules / total
Refresh
Ticker freshness (0–15m window)
AI utilization
Model runtime metrics (offline)
Cache hit
Edge cache ratio (offline)
Self-improving loop
AI OS continuously adjusts agent routing based on exam scores and real-world outcomes.
1
Exam
Agent takes offline exam → gets score per category
→
2
Score → Routing
Score determines which tasks the agent can handle
→
3
LLM Router
Router picks cheaper or better backend based on cost/quality
→
4
Effectiveness Ledger
Real outcomes tracked: success rate, blocker rate, cost
→
5
Learning → RAG
Next session starts with context from previous results
Effectiveness ledger offline — aggregates shown only where available.
Generated 2026-06-06T00:58:42.789586+00:00
- Agents tracked
- 0
- Tasks recorded
- 0
- Overall success
- —
- Tests pass rate
- —
- Avg est. cost
- —
| Agent |
Exam total |
Success rate |
Blocker rate |
Recommended lane |