Project scripts

Project scripts are commands the project itself declares, checked into .pragma/scripts.json at the project root:

{
  "setup": ["bun install", "cargo fetch"],
  "teardown": ["docker compose down"],
  "runScripts": {
    "run": [{ "command": "bun run dev" }],
    "build": [{ "command": "bun run build" }],
    "test:watch": [{ "command": "bun run test --watch" }]
  }
}

Setup and teardown

• setup runs headlessly after a worktree is created — it is the "Running scripts" step of the creation screen. New worktrees arrive with dependencies installed and caches warm.
• teardown runs headlessly before a worktree is deleted. A failure blocks the deletion — use it to stop containers, release ports, or clean caches that must not leak.

Commands run concurrently, capped at four at a time.

Run scripts

Every key under runScripts becomes a toolbar button on the tab strip:

• run and build are reserved defaults — Play for run, Hammer for build.
• Any other key is a custom button ("Run test:watch"), with an optional Iconify icon.
• While active, the button turns into a stop control; stopping restores the worktree's previous split layout (a run script temporarily replaces it).
• Config changes hot-reload — edit .pragma/scripts.json and the buttons update within a moment. Parse errors surface in the button tooltip.

Running scripts also appear in the command palette: Enter opens the script tab, Shift+Enter closes it.

A typical split: run on the left, the agent terminal in the middle, browser pointed at the dev server on the right.