Capability overview
What does project workspace do in DevDock?
Keep each project's overview, commands, run history, databases, security checks, settings, and tools together.
A DevDock project can represent one repository, a monorepo, or a product assembled from several separately located folders.
Each registered folder retains its own detection results, task working directories, and shortcuts while contributing to one coherent project overview.
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
Getting started with DevDock
Build a dependable DevDock workspace: register a project, verify detection, run commands safely, and create a daily workflow you can return to.
The guide covers decide what the project represents, register the first folder, review detection before relying on it, read the project overview, run the first generated command, create a daily workflow, return to the project with context intact. 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 workspace.
What does project workspace do in DevDock?
Keep each project's overview, commands, run history, databases, security checks, settings, and tools together. A DevDock project can represent one repository, a monorepo, or a product assembled from several separately located folders. Each registered folder retains its own detection results, task working directories, and shortcuts while contributing to one coherent project overview.
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.