Web console
The agent shell served directly by ort serve on loopback with its write token embedded.
A persistent supervisor for coding agents: every project gets a durable agent that remembers its work.
Models, harnesses and hosts plug in and ORT holds the state. You steer a tree of chats instead of a grid of terminals.
bun run src/main.ts serve 7777
ORT is one tree of chats. The ORT chat at its root delegates to each project's main chat, and the project's saved sessions sit beneath it as child chats.
An agent is bound to one project folder (agent:<project_id>), and a session's question climbs the tree as a thread card until it reaches a human.
“The old fixtures name a field the schema dropped — keep legacy alias or rename?”
awaiting decision · click “answer via owner agent” above to resolve inside autonomy bound
You think in models, ORT thinks in routes. A canonical model gathers every provider's route to the same model into one chain rail in your order: workbuddy/deepseek-v4.1-flash-1m and the gateway's deepseek-v4.1-flash are two routes, one model.
A run's harness, model and host are decided before anything spawns, from one frozen view of the fleet. A rate limit files a provider hold and demotes the pair; the chain walks on to the next route, then to your fallback models.
Where work may run at once is decided by six pool scopes. One admit(run) path is shared by the planner, the dispatch commit, and the session guard.
Occupancy is sessions creating or busy; any pool no row bounds is unlimited. A refusal names the full pool and leaves the task READY.
Every dispatch writes its runs row before the first event, and every event is persisted before it is acted on — the record outlives the process that made it.
Steer a live run, cancel it or close it, and each control call is recorded with its source. A retried run resumes its harness session rather than restarting.
A node is an ssh login and Bun 1.3 or later — nothing of ORT is installed on it. Registering a host starts the idempotent walk: probe, provision, handshake, smoke, halting on the first failure and resuming where it stopped.
A node never holds a provider credential; the walk mints it a revocable gateway key of its own, delivered to a 0600 file on stdin. Then it can drain and retire.
Runs ship per session over a single SSH channel. Zero resident daemon; clean teardown when the run settles.
ort host serveStays resident on the remote agent host — in-flight runs survive a control-plane restart untouched.
The console exists once — nine pages served from one canonical source. No mount keeps a second implementation or a second copy of a fact.
Select any page below to see all three mounts follow the same route in lockstep.
The agent shell served directly by ort serve on loopback with its write token embedded.
A thin Electron shell under a single-instance lock that starts or reuses the local supervisor, tray included.
Electron · Linux AppImage/debThe DeepSeek Harness ui-ort panel mounts a generated mirror pinned by SHA256SUMS; a drift spec fails on any diff.
Built to sit quietly on your workstation or home server — zero container sprawl, zero hidden credential vaults.
Bun ≥ 1.3 and TypeScript, one process. No Node.js or Python needed for the supervisor itself.
Everything lives in data/supervisor.db, moved with ORT_DB. Every write goes through ORT.
HTTP API and console on :7777. serve auto-ticks on its interval; tick runs one cycle manually.
Harnesses plug in behind a frozen contract. pi-durable is the default under the launcher and desktop app, strictly opt-in — ORT core imports no substrate module.
Owner memory is its own canonical store serving every agent and chat. Credentials are references only (an env var, file, or login) — never stored, never shown. ORT is its own dogfood project, working this repository's TODO.md.
Clone, install, point it at a folder and serve — the console comes up on loopback with its own 0600 bearer token.
serve binds 127.0.0.1. A non-loopback ORT_BIND without an auth secret refuses to start.
Every call except GET /status requires a bearer token generated at 0600 beside the database.
State lives in data/supervisor.db. Never point two supervisors at the same file — use ORT_DB for isolation.
Planned surfaces and pool scopes currently tracked in the repository's own roadmap.
A published client library for driving projects, tasks, Board moves, runs and events instead of raw HTTP.
Newline-delimited requests and event streams for headless scripting and live pipelines against ORT.
Exposing ORT's supervisor operations as typed RPC methods for editor and tool integrations.
canonical pool scopeOne capacity cap across every provider route of a canonical model, enforced in admission and on the lanes.