Graph-visible delegation
Follow contacts, jobs and tools through queued, active, waiting, done and failed states.
CHAT · GRAPH · APPROVALSLocal-first agent control plane · Alpha
One room for every agent and machine.
Harness OS gives local and cloud models stable identities, bounded workspaces, observable delegation, and a shared interface for language and creative compute.
REST + WebSocket client · deterministic demo · no external telemetry by default
SEEDED DEMORepeatablenetwork-free evidence
Dense when it matters. Quiet when it doesn't.
The production WebUI is an API client, not a static dashboard. It reads versioned Harness resources, follows the event stream, and sends user actions back through the control plane. A deterministic mode provides network-free evaluation and repeatable visual checks.
Compute without conflation
See inference, execution, creative and Harness hosts as distinct resources with their own pressure.
HOSTS · MODELS · TELEMETRYBounded workspace work
Browse files, inspect worktree state, review output and submit changes through the workspace API.
FILES · GIT · ARTIFACTSSchema-shaped models
Inspect load state and history, then apply runtime settings through instance endpoints.
LOAD · UNLOAD · SETTINGSCreative compute is first-class
Track engine capability levels, reusable profiles, generation jobs, batch comparisons and provenance.
ENGINES · QUEUE · ASSETSCapabilities stay lazy
Skills and MCP tools expose compact indexes until the user or runtime chooses what to activate.
SKILLS · MCP · PERMISSIONSA stable team, flexible compute
Delegate by name. Bind at run time.
A Contact remains recognizable while its model, provider, inference host and execution host can change. Every run can preserve the resolved binding snapshot for review and benchmarking.
1
Mention contactsCompose a parallel or sequential workflow in plain language.
2
Review the live graphInspect delegation, tool activity and infrastructure events.
3
Approve consequential workAllow once or deny at the point of execution.
@planner and @reviewer inspect the sync flow independently. If the plan holds, have @builder implement it and @tester run the focused checks.
Repository checkpoint · August 2026
Broad alpha. Strong test surface. Real-world proof comes next.
The one-shot build covers most of its specification in typed source, API routes, two clients, deterministic fixtures, and CI. The specification's Definition of Done is still a requirements document—not a signed-off live acceptance record.
- Built
Control-plane foundation
Versioned FastAPI and events, SQLite, Contacts and bindings, providers, SSH workspaces, permissions, artifacts, creative adapters, analytics, optional Node, WebUI, TUI, demo mode, and packaging.
- Now
Validate outside the fixtures
Exercise supported providers, SSH hosts, creative runtimes, node telemetry, authentication, and the full phone-to-workspace journey on real infrastructure.
- Next
Turn findings into release gates
Record a checked acceptance matrix, harden install and upgrade paths, document adapter limits, and keep the API, generated client, WebUI, and TUI aligned.
- Later
Deepen, do not sprawl
Expand provider and creative support only from measured capability evidence; preserve the future mobile-compute hook without claiming a native mobile node.
Mission control from desk to phone.
The responsive WebUI keeps three panels on desktop, at least two useful panes in iPhone landscape, and a fully actionable chat with slide-over sheets in portrait.
Inspect the implementation
A real client for a local runtime.
The Pages site documents the project. It does not impersonate the Harness server. Run the WebUI beside Harness on a deliberately configured private network, with authentication enabled for non-loopback access.