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. Cmd/Ctrl+R on desktop (Alt+R on the portal) starts the selected task or stops it if it is running; Open Run Menu in the command palette (Cmd+Alt+R / Ctrl+Alt+R on the portal) opens the dock without starting anything.
• 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

A debug configuration’s preLaunchTask runs in the run dock like any other task, on the workspace’s host and with its output in its own tab. A one-shot task must exit cleanly and a long-running one (a dev server, a watcher) must report ready; then debugging starts and the dock returns to its Debug tab. If the task fails, the dock stays on the task’s tab and says why. See Debugger.

Related topics

• Debugger
• The run dock