Architecture

API-first. Event-driven. Host-aware.

The WebUI and TUI consume the same versioned control-plane contract. Remote workspace execution does not require a Harness installation on the target host.

Resource state through REST

Clients fetch sessions, contacts, hosts, workspaces, models, engines, artifacts, analytics and jobs from /api/v1.

Transitions through events

The WebSocket stream carries run, inference, tool, host, model, creative, artifact and benchmark transitions.

Bindings remain inspectable

Turn, session, Contact, role and system configuration resolve into a snapshot before inference begins.

Capabilities describe reality

Adapters expose supported controls and explicit limitations instead of pretending every provider or engine is identical.

WebUIResponsive mission control and bearer-authenticated API client

TUIKeyboard-first client on the same contract

CLIScriptable operator commands

Static PagesDocumentation only, never the runtime

Harness API + event stream

authentication · resources · jobs · approvals · correlation IDs

Agent runtime

Control plane

Persistence

Context compiler

Analytics

Language providersLocal runtimes and cloud APIs

Execution hostsAgentless SSH or optional Node

Creative enginesNative or compatible APIs

MCP + toolsLazy capability discovery