Commands, processes, and workspaces

Play and Start Workspace are different

Play starts or stops the project's configured execution commands. Start Workspace performs the complete opening workflow.

1. Open the configured editor.
2. Start execution commands from top to bottom.
3. Wait for the configured local URL to respond.
4. Open the local URL and links selected for Workspace.

Configure execution commands

Create one command for every process Localdeck should manage. Each command can have a name and readiness URL.

Name: Web
Command: pnpm dev
URL: http://localhost:3000

Projects with multiple processes

Name: API
Command: pnpm dev:api
URL: http://localhost:4000

Name: Web
Command: pnpm dev:web
URL: http://localhost:3000

Logs and status remain separated by command. Stopping the project stops every process Localdeck started for it.

Static websites without a development command

A static project can be opened directly in the browser when it contains an HTML entry point and does not need a development server. Relative asset paths work more reliably than root-relative paths when opening files directly.

Port conflicts

When a configured port is occupied, Localdeck identifies the process and lets you cancel, continue, or close the conflicting process when macOS permissions allow it.

Logs and failed processes

Open Logs from the project menu or click its Running or Error badge. Each execution command has its own tab.

• Running means the managed process remains active.
• Initializing means Localdeck started the command but its URL is not ready yet.
• Error means a command terminated unexpectedly. Open Logs to inspect the reason.