Skip to main content

QuickRun

Run detected scripts and ad-hoc commands in a managed QuickRun panel, with history, pinning, and auto-restart.

Updated
Reviewed

QuickRun

QuickRun lives in the footer of the project sidebar. It's the fast way to fire off a command or start a long-running process without setting up a full Recipe. The footer is one row: the activity readout on the left, and a Run command button on the right (it shortens to Run when the sidebar is narrow). Click it and the QuickRun panel opens above the row with the cursor already in the input; click it again to fold the panel away. Whether the panel is open is remembered per project.

Note
Three surfaces run things for you and they divide cleanly. QuickRun is for a single command against the selected worktree, typed or picked from a list. Recipes are for a saved multi-panel setup you want back. The empty-grid launcher is where recipes and closed sessions surface when a worktree has no panels open. See The Empty Grid.

Running a Command

The top line of the panel names where the command will run: the selected worktree's branch, beside a branch icon. Below it, the input shows a $ prompt and the placeholder Run a command. Type a command and press Enter, or click the Run arrow at the end of the field. The input clears, a terminal panel starts in the worktree, and the command is saved to your history. If the panel can't start, the command goes back into the field with a Couldn't start line under it.

Note
QuickRun needs a worktree selected. With none active, the input is replaced by the line "Select a worktree above to run a command".

Output Location

Two toggle buttons sit between the input and Run. The second one controls where the terminal panel appears:

  • Grid (default): opens in the main panel grid as an interactive terminal. Tooltip: Output: grid (interactive terminal).
  • Dock: runs in the dock as a background task. Tooltip: Output: dock (background task).

The output choice applies while the panel is open and starts at Grid each time QuickRun opens. The first toggle is Auto-restart, which is remembered per project. In a narrow sidebar both toggles drop to their own line inside the field's border, so the command keeps its width.

Command Suggestions

Focusing or clicking the input, typing into it, or pressing ArrowDown opens the suggestion list. QuickRun sits at the bottom of the sidebar, so the list unfolds upward from the input. It is grouped into three bands:

  • Pinned: commands you saved. Pinned detected scripts keep the order their source file declares, followed by pinned commands you typed yourself.
  • Scripts: the project's detected runners that aren't pinned, in the order the source file declares them.
  • Recent: your last 10 commands, most recent first. Commands already listed as pinned or as a script are left out, and repeats are collapsed. History is stored per project, so switching projects gives you that project's commands rather than a shared list.

Each row is one line: the command's name, then what it runs. Filtering is a case-insensitive substring match on both, and the matching text is highlighted. When what you've typed isn't already a row, a Run row for your exact text leads the list, so whatever Enter runs is always a visible row.

A strip under the list says what will happen before it does: the full command of the highlighted row (or Choose a command, or type one), the branch it runs on, and how it runs, such as Grid or Dock · Restarts.

Choose a script or run the command you typed

Keyboard

KeyWhat it does
EnterRuns the highlighted row, or the text in the field when the list is closed.
ArrowDown / ArrowUpOpens the list, then moves the highlight. Hovering a row moves the highlight too.
TabCopies the highlighted command into the field to read or edit it, without running it.
Option-P Alt-P Alt-P Pins or unpins the highlighted row.
EscapeCloses the list and keeps focus in the field.

Detected Runners

Runner detection reads more than package.json. Daintree scans a worktree for package.json scripts, Makefile targets, justfile recipes, Taskfile tasks, Procfile processes, mise tasks, Django's manage.py, composer.json scripts, and dev container commands. On a JavaScript project it also works out which script is the canonical dev command from the framework in your dependencies, so a Next.js or SvelteKit repo surfaces the right one first instead of whichever script sorts earliest.

The same detected runners back project.runCheck, an MCP tool in the Full tool set, used to run a project's own check. It names a runner rather than a command (an agent can only run something the project already declares) and it reports the process's real exit code rather than guessing from scrollback text. It runs in the main process specifically so a long test suite isn't cut off by the renderer's dispatch timeout and can still be cancelled.

A QuickRun task's icon follows whatever ends up running inside it, so npm run dev on a Vite project shows a Vite icon rather than an npm one. See Process Icons for how that resolves and how plugins add their own detections.

Pinning Commands

Highlight a row and click the pin that appears at its right edge, or press Option-P Alt-P Alt-P . The row moves into the Pinned band and is saved with the project's settings. At pin time, the current auto-restart and output location toggles are captured as the command's own settings. Unpin the same way.

While a pinned command is highlighted, both toggles show its saved settings, and running it uses them. Pressing a toggle while it is highlighted overrides that setting for this one launch and leaves the saved command unchanged.

Note
Highlighting a pinned command can change what the toggles show. That's intentional: each pinned command carries its own auto-restart and output location, and the toggles always show what the next run will do.

Auto-Restart

The auto-restart toggle is the circular arrow button beside the input. Its tooltip reads "Auto-restart: on" or "Auto-restart: off". The setting persists per project, so you can leave it on for projects where you always want dev servers to come back after a crash.

If auto-restart is in effect when you launch a command, the spawned terminal restarts whenever its process exits. Here's the sequence:

  1. The process exits, and Daintree checks the exit code and panel state.
  2. An exponential backoff delay kicks in: 250ms to start, doubling each attempt (500ms, 1s, 2s, 4s), capped at 5 seconds.
  3. During the delay, a banner reading "Auto-restarting…" appears inside the terminal.
  4. Once the delay passes, the command restarts. The usual exit banner is suppressed.

If the process ran for more than 10 seconds before exiting, the backoff resets to zero. A stable run followed by a crash counts as a fresh event, not the continuation of a crash loop.

Tip
Auto-restart is built for dev servers and file watchers like npm run dev or npm run test:watch. A process that exits with code 130 (the usual Ctrl+C result) does not auto-restart. A command that handles interrupts and exits with another code may restart; close or trash its panel to stop the cycle.
Note
If a process keeps crashing quickly, the backoff compounds up to the 5-second cap. Close or trash the terminal panel to stop the restart cycle for good.

Active Tasks

Above the input, a task list shows the QuickRun-spawned panels for the selected worktree, oldest at the top and the newest nearest the input. The five newest are shown; older ones collapse into an N earlier button whose popover lists them with the same controls. Each row shows a status dot and the command; click the command to focus its terminal panel. Beside it, a running task shows its elapsed time and any other task says its state in words.

  • Running: pulsing dot and elapsed time.
  • Restarting: pulsing amber dot, shown during the auto-restart backoff delay.
  • Finished: the process exited with code 0. The row stays until you dismiss it or newer launches push it into earlier.
  • Failed: the process exited with a non-zero code.

Hovering or focusing a row swaps the time or status word for its actions: Stop task while it runs or restarts, Restart task on a failed task without auto-restart, Dismiss task once it has finished or failed, and Focus terminal on every row. A dismissed task comes back if it starts running again.