Orkestrate

Get started

Workbench (TUI)

What you get when you run orkestrate with no subcommand — and what it is not.

v0 scope: The workbench is a pack launcher and catalog UI. Agent chat runs in OpenCode, in a separate terminal window.

What it is

Running orkestrate with no arguments starts an OpenTUI fullscreen terminal UI. It lists installed packs, lets you browse the bundled + registry catalog, install packs, see launch status, and spawn OpenCode — it does not host an embedded agent conversation inside Orkestrate.

Runtime

The CLI runs on Bun (#!/usr/bin/env bun). The site installer adds Bun if needed: curl -fsSL https://orkestrate.space/cli/install.sh | bash (or the PowerShell equivalent).

First run (welcome)

If no packs are installed in the workspace, a welcome screen appears before the main list:

  • Explains that no packs are installed yet.
  • Enter installs the bundled coding pack (global install path).
  • Ctrl+C exits without installing.

After that, the main workbench opens with coding in the installed list.

Two screens

Installed packs (default)

Title: Packs. Each row shows pack id, truncated description, and status:

  • idle — no active launch for this pack in this repo.
  • ● running — one or more launches still tracked (footer shows run id or count).

The list refreshes about every 1.5s so status stays current while you keep the workbench open.

Browse packs

Press b. Title: Browse packs. Shows bundled catalog entries plus registry results merged into one list. Tags on rows:

  • [registry] — from orkestrate.space API (when reachable).
  • [installed] — already in .orkestrate/packs/.

Enter on an uninstalled row runs registry install / bundled install for that slug, then switches back to installed view.

What launch does from the workbench

On an installed pack, Enter or l calls the same path as orkestrate run launch <id>:

  1. Syncs the pack harness slice into the pack home (see launch docs).
  2. Opens a new terminal window running OpenCode with that home.
  3. Your repo remains the working directory; your personal OpenCode config is untouched.

Footer message briefly confirms success or shows the error string. The workbench stays open; OpenCode runs in the other window.

Key reference

Installed view

↑ / ↓ / k / j     Move selection
Enter / l         Launch selected pack
s                 Stop active session(s) for selected pack
b                 Browse catalog
q / Ctrl+C        Quit workbench

Browse view

↑ / ↓             Move selection
Enter             Install selected catalog entry
i                 Back to installed packs
Esc               Back to installed packs
q / Ctrl+C        Quit

Not in the workbench (v0)

  • Chatting with the agent inside Orkestrate.
  • Editing harness files (use your editor + pack validate).
  • Registry publish / submit (use the website).
  • Multi-pack orchestration or handoff between agents.

CLI without the workbench

Every workbench action has a subcommand if you prefer scripts or CI:

orkestrate registry install coding
orkestrate run launch coding
orkestrate run list
orkestrate run stop <run-id>
orkestrate doctor