Feature guide Windows

Keep command output attached to the project that produced it

Return to previous runs with their task, target, timing, exit state, and retained output still connected.

Capability overview

What does command history do in DevDock?

Return to previous runs with their task, target, timing, exit state, and retained output still connected.

Standard output and error output remain distinguishable, and long-running managed process trees can be stopped from the same workspace.

History makes it possible to compare a failure with the last healthy run instead of reconstructing the command from memory.

DevDock command workspace showing a detected development command and its output area
Commands stay attached to the project, working directory, and execution target they belong to.

In the workflow

Run a command

Start a saved workflow and follow its output from the project view.

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 guide

Direct answers

Questions about command history.

What does command history do in DevDock?

Return to previous runs with their task, target, timing, exit state, and retained output still connected. Standard output and error output remain distinguishable, and long-running managed process trees can be stopped from the same workspace. History makes it possible to compare a failure with the last healthy run instead of reconstructing the command from memory.

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.

Next

See all DevDock capabilities.

Back to capabilities