Capability overview
What does daily workflow do in DevDock?
Pin the commands and environments you use most and run them from the project overview or Today.
Saved workflows keep servers, workers, watchers, Docker services, and loopback readiness checks in an intentional order.
Today brings pinned workflows and recently opened projects together so returning to work does not depend on shell history.
In the workflow
Return from Today
Open recent work or a pinned daily workflow without hunting for the project again.
DevDock keeps the project, registered folder, working directory, execution target, and retained output connected so the same task remains understandable later.
Useful in practice
Where this capability earns its place.
Related manual
Commands, workflows, and run history
Create dependable project commands, choose safe execution targets, manage long-running work, and use history to diagnose failed runs.
The guide covers generated and custom commands, review before the first run, run and stop processes, build reusable workflows, read run history, protect environment values. It is the best next step when you want to move from the product overview into a repeatable setup.
Read the guideDirect answers
Questions about daily workflow.
What does daily workflow do in DevDock?
Pin the commands and environments you use most and run them from the project overview or Today. Saved workflows keep servers, workers, watchers, Docker services, and loopback readiness checks in an intentional order. Today brings pinned workflows and recently opened projects together so returning to work does not depend on shell history.
Does DevDock replace the terminal?
No. It provides a repeatable control surface for common project workflows and can still open a registered folder in a terminal, Visual Studio Code, or File Explorer.
Does project detection run repository code?
No. Detection reads a bounded set of manifests and marker files. It does not execute package managers, build tools, project scripts, or network requests.