User Interface — Overview
Mirrored from
docs/design/user-interface/1_overview.md. Edit the source document in the repository, not this generated page.
Orbit UI covers the local dashboard served by orbit-cli and the project-facing web surface. It gives operators a dense, legible way to monitor agents, workflows, telemetry, and audit signals.
1. Motivation
Section titled “1. Motivation”Agent runs produce more state changes, logs, and diagnostics than a human can read linearly. The UI therefore optimizes for scan density, clear status recognition, and quick drill-downs. Canon Refined keeps the pro-tool feel while using readable sans-serif text, subtle rounding, and restrained semantic color [T20260427-29].
2. Core Concepts
Section titled “2. Core Concepts”- Canon Refined and typography: Layered dark surfaces, fine borders, compact spacing, and muted status colors;
Intercarries labels and prose whileJetBrains Monocarries IDs, metrics, timestamps, code, and logs. - Surfaces: The local dashboard lives in
crates/orbit-cli/assets/dashboard/; static docs and project pages should reuse the same visual grammar without importing runtime-only dashboard assumptions.
3. At a Glance
Section titled “3. At a Glance”| Concern | File | Task |
|---|---|---|
| Local dashboard | crates/orbit-cli/assets/dashboard/ | Runtime tabs, tables, tiles, logs, and diagnostics. |
| Theme rules | ./specs/theme.md | Canon Refined tokens and visual invariants. |
| Current mechanisms | ./2_design.md | Layout, telemetry, palette, typography, and known limitations. |
Task References
Section titled “Task References”- [T20260427-29] introduced the Canon Refined UI direction.
- [T20260430-24] tightened the UI design docs against shared conventions.
Resolve any task above with
orbit task show <ID>orgit log --grep=<ID>.