Runtime
Runtime UI tour
The operator-facing map of the runtime UI and which section owns each part of setup and routing review.
The runtime UI is the main operator surface for bringing role-model to life on a machine.
The core sections
The current shell is organized around:
- Connect for the first-run entry point into local and remote setup
- Local for local backends and local model state
- Remote for provider accounts and remote execution posture
- Models for benchmark and model-level routing context
- Router for candidate, config, and decision views
- Observe for request, telemetry, and evidence review
- System for runtime and readiness diagnostics
Setup surfaces
Connect
Onboarding entry point that links operators into the local and remote setup paths.
Local
Local runtimes, local models, and local endpoint readiness.
Remote
Provider accounts and remote execution posture.
Models
Model inventory, role activation, and benchmark operations.
Decision review surfaces
Router
Candidate sets, strategy posture, scored decisions, and fallbacks.
Observe
Request history, telemetry, usage, logs, and endpoint evidence.
System
Readiness, runtime health, and diagnostics that explain whether the shell itself is healthy.
Who owns what
| Section | Primary responsibility |
|---|---|
Connect | onboarding handoff into local and remote setup paths |
Local | local runtime connectivity and local model inventory |
Remote | provider accounts and remote execution availability |
Models | benchmark workflow and model-facing routing quality |
Router | candidates, strategy context, decisions, and fallbacks |
Observe | request history, telemetry analytics, and investigation |
System | readiness and runtime health context |
First-time setup path
The canonical operator path is:
- connect local or remote models
- assign roles
- run the full benchmark
- review results
- choose and save routing strategy
- validate with a real request