Tasks runner

Running project tasks has moved out of the editor and into the run dock — the panel at the bottom of the workspace side panel. That’s where task discovery, one-shot runs, long-running services, readiness detection, live output, and failure hand-off all live now, on desktop and in the portal.

Start here:

• The run dock — what it is and where tasks come from
• Configuring tasks — .glueprint/tasks.json, services, readiness, and overriding discovered scripts
• Runs, services, and output — statuses, stopping and restarting, the output view, and offline behavior

What changed from the old editor runner

• Discovery now includes configured commands, package scripts, Cargo manifests, and .NET manifests (.sln, .slnx, .csproj, and .fsproj). See The run dock for the full source list.
• The old editor-scoped shortcuts (Cmd/Ctrl+Shift+B, Cmd/Ctrl+Alt+B) are retired, and there is no re-run-last-task shortcut. On desktop, use Cmd/Ctrl+K, then Cmd/Ctrl+R; the portal uses Cmd+Alt+R (Ctrl+Alt+R). Both open the Run menu without starting a task.
• Output no longer docks inside the editor — runs get tabs in the dock, and their diagnostics still feed the editor’s Problems panel exactly as before.

preLaunchTask

The debugger can still chain a task before launching. If a debug configuration declares preLaunchTask, that task runs first and the debugger only starts if it exits cleanly. See Debugger.

Related topics

• Debugger
• The run dock