Capability overview
What does project health do in DevDock?
See whether configuration, dependencies, Git, Docker, toolchains, or recent command results need attention.
Health remains descriptive: a warning identifies the affected folder, tool, configuration, or recent run without blocking unrelated work.
Detection and runtime health stay separate, so a recognized project can explain that an SDK, executable, engine, or service is unavailable.
In the workflow
Review the workspace
See its folders, health, saved commands, and recent activity from one overview.
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
Project health and troubleshooting
Interpret health warnings, separate setup problems from command failures, and recover a workspace without resorting to broad destructive cleanup.
The guide covers what project health means, start with scope and evidence, resolve missing tools, investigate failed commands, handle git warnings, recover workflows, when to rescan or rebuild the workspace. 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 project health.
What does project health do in DevDock?
See whether configuration, dependencies, Git, Docker, toolchains, or recent command results need attention. Health remains descriptive: a warning identifies the affected folder, tool, configuration, or recent run without blocking unrelated work. Detection and runtime health stay separate, so a recognized project can explain that an SDK, executable, engine, or service is unavailable.
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.