ORT

One Radiant
Thing.

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.

Presence is computed on every read, never stored — idle · queued · working · waiting · needs_input · blocked · failed · offline.

One drop, one light — the glow rolls to the bead that serves. (Illustrative fleet.)

One agent per project

§1

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.

An optional owner agent answers each chat inside an autonomy bound, while an autonomous loop works every onboarded project's goal tree until it is exhausted.

ORT chat invoices · main chat scrapingcow · main chat session · working session · saved session · saved session · clouded a question escalates as a thread card →
figure: the chat tree — directives flow down, escalations flow up (illustrative)

Models, not endpoints

§3.0

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. A switched-off model admits nothing.

~1,600 routes discovered live 1 chain per model, walked in order route before spawn — the chain is picked before the session starts
gpt-5.2-codexvia orca-router · serving
claude-sonnetvia llm-gateway · ready
deepseek-chatskipped · rate-limited
local-7bprovider off
handoffowner's per-model fallbacks
figure: one model's route chain — the serving bead, ready, skipped, off, then the fallback interchange (illustrative)

Capacity as pools

§3.17

Where work may run at once is decided by pools: global, harness, provider, model, host and project. One admission decision is shared by the planner, the dispatch commit and the session guard; occupancy is the sessions creating or busy, and a pool no row bounds is unlimited.

A refusal names the full pool (capacity: provider workbuddy 1/1), and the task stays READY for the next cycle.

globalharnessprovidermodelhostproject
figure: a pool's cap as sockets — five of eight running; the six scopes ORT admits against

Remote nodes, one walk

§3.19

A node is an ssh login and Bun 1.3 or later, and nothing of ORT is installed on it. Registering a host starts the walk (probe, provision, handshake, smoke), each step idempotent and recorded, halting on the first failure and resuming where it stopped. Runs ship per session over one ssh channel, or stays resident on an agent host (ort host serve), whose runs survive a control-plane restart.

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.

registereddisabled
probedmachine-id, bun, node
provisionedworker shipped
handshakentunnel up
smoke-passed16-token run
enabledtakes work
figure: the walk — a node onboards itself stage by stage; a halted step is recorded, a re-point restarts it

Sessions that survive

§3.9

Sessions are durable and resumable. Every dispatch writes its runs row before the first event; every event is persisted before it is acted on, so 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. One run, one row, settled once.

you · directive — port the invoice parser to the new schema, keep the tests green
session s-41 · working — 3 files touched, suite running… steer · cancel
thread · needs you — the old fixtures name a field the schema dropped: keep or rename?
figure: a session chat — durable, resumable, every run event persisted; a question escalates as a thread (illustrative)

One source, three mounts

§3.16 · §1.1

The console exists once — Chats, Board, Agents, Hosts, Models, Projects, Settings, Memory, Gateway. The web shell serves it on ORT's own origin; the desktop app, a thin Electron shell under a single-instance lock, loads the same page and starts or reuses the supervisor.

The Harness ui-ort panel mounts a generated mirror pinned by a SHA256SUMS manifest; a drift spec fails when any file differs. No mount keeps a second implementation or a second copy of a fact.

localhost:7777/app/chats

Web console

the agent shell — every page ORT serves
ORT.app · Electron

Desktop app

a thin shell over the supervisor, tray included
dsh · ui-ort panel

Harness panel

the same console inside the DeepSeek Harness

How it runs

one process, one file of truth
runtimeBun and TypeScript, one process. and no Node or Python needed for the supervisor itself.
truthOne SQLite database: data/supervisor.db, moved by ORT_DB. Every write goes through ORT.
apiHTTP API and the console on :7777. serve ticks on its own interval; tick runs one cycle by hand.
boundaryHarnesses plug in behind AgentAdapter/1, a frozen nine-method contract. Credentials are references only, never stored, never shown.
memoryOwner memory is its own canonical store; one shared memory serves every agent and every chat.
itselfORT is its own dogfood project: the autonomous loop works this repository's TODO.md.

Still on the bench

from TODO.md, marked coming

Put a drop on your desk

The supervisor is one Bun process over one SQLite file. Clone, install, point it at a folder and serve — the console is up on loopback with its own token.

# needs Bun ≥ 1.3 and nothing else
git clone git@github.com:KinoThe-Kafkaesque/ORT.git
cd ORT && bun install
# onboard a folder, queue a task, put up the console
bun run src/main.ts add-project .
bun run src/main.ts task ORT "My first task"
bun run src/main.ts serve 7777
# console → http://localhost:7777
# the Electron shell: bun install in apps/desktop, then bun run app
# serve this machine to another ORT: bun run src/main.ts host serve

Loopback only by default, and a non-loopback bind without a secret refuses to start. State lives in data/supervisor.db — never point two supervisors at the same file. Every call but GET /status is bearer-authenticated.