CodeLoom

One engine. One protocol. As many clients as you want.

A coding-agent stack split at its natural seam: a server that owns the workspace, a control plane for running it unattended, and thin clients that just render what the server says. Three parts, one protocol between all of them.

shipping

CodeLoom Engine

A JSON-IPC Unix server. The TUI is just a client.

·NDJSON over one Unix socket — every client reads the same stream.
·A write funnel with a syntax gate, full undo, and a TypeSafe judge layer.
·Orchestrator spawns 6 subagent personas into isolated git worktrees.

unix socket

$ python app.py .
listening on .engine/engine.sock

6 subagents · 32 tools · TypeSafe judge

Open engine

concept

CodeLoom Cloud Controller

Fleet control for engines running in the cloud.

·Provisions a sandbox per run, clones the target repo, hands it a session.
·Schedules and staggers runs across a fleet under a budget ceiling.
·Settle is still routed back to you — merge, PR, keep, or discard.

fleet status

3 sandboxes running · 1 queued
budget: $12.40 / $50.00

provision → schedule → supervise → settle

Open cloud controller

in development

CodeLoom Clients

Every surface that talks to the engine over one socket.

·A web client: sign in with GitHub, start a sandboxed session, watch a live transcript with inline diffs.
·A multi-agent graph, git changes and per-agent tokens, cost and duration as it works.
·Also: a terminal TUI. No client talks to a model directly.

web first, same events

web   session · live ▍
      diff · agents · changes
tui   :CodeLoom ask
JSON events, nothing else

Open clients

an open-source resume project byIresh Sharma journal