workflows

Use configureWorkflow with a name, the shell command, and a waitForPort matching your server's port. Set outputType to "webview" for web applications, and the workflow auto-starts after configuration by default.

Call restartWorkflow with the workflow name, such as "Start application". You can pass a custom timeout in seconds for applications with slow startup, and the result includes restart status and an optional screenshot URL.

Supported ports are 3000, 3001, 3002, 3003, 4200, 5000, 5173, 6000, 6800, 8000, 8008, 8080, 8099, and 9000. The waitForPort parameter must match the port your application actually listens on.

Common causes include the application not listening on the expected port, the endpoint not returning HTTP 200, or startup errors in your code. Check the workflow logs via getWorkflowStatus and verify your port configuration.

Use bash for one-off commands like build scripts, tests, or package installs that do not need to keep running. Workflows are only for persistent processes such as servers, TUIs, and background services.

Yes, the maximum is 10 workflows. Keep workflows minimal by using one primary workflow per project and removing unused ones with removeWorkflow, which also stops them if running.