The execution plane for coding agents

Give agents a fleet of real machines.

PRTL runs durable agent sessions wherever the work belongs—macOS, Windows, or Linux—from the same commands your agent already knows.

Install PRTL See the boundary

prtl status 4 nodes reachable

studiomacOS · arm64running
forge-winWindows · x64ready
spark-01Linux · arm64running
builderLinux · x64ready

›prtl status --repo forge --task-ref forge-arm64 --json

One binary. Three operating systems. Four native targets.

Apple Silicon
Windows x64
Linux x64
Linux ARM64

01 / Install

One command on every machine.

The installer selects the native target, verifies its SHA-256 digest, and installs an immutable revision. No repository access or cloud credential is required.

macOS + Linux

curl -fsSL https://prtl.space/install.sh | sh

Windows PowerShell

irm https://prtl.space/install.ps1 | iex

Development snapshots are public and revision-pinned, but currently unsigned. Signed release channels come next.

02 / The boundary

Plans stay plans.
Runs stay observable.

WHAT

Beads holds intent.

Goals, issues, dependencies, acceptance criteria, and the ready frontier remain in the work graph agents already use.

bd ready --json

WHERE + HOW

PRTL holds execution truth.

Attempts, sessions, nodes, worktrees, runtime policy, and exact evidence stay with the execution plane.

prtl status --json

03 / Agent first

No planner hiding inside the scheduler.

PRTL is model-free. Your agent keeps the judgment; PRTL supplies the deterministic surface for dispatch, admission, recovery, policy, and evidence. The CLI is the API.

$ bd ready --json
$ prtl node ls --json
$ prtl run --repo forge --task-ref forge-linux-arm64 \
    --node spark-01 --agent codex --task "Implement this bead"
$ prtl status --repo forge \
    --task-ref forge-linux-arm64 --json

Four targets are already waiting.

Put the right agent
on the right machine.

Install the development snapshot