martingruner.com
Menu

developer command runner Windows

Run development commands with the project context attached

Save, run, stop, and revisit development commands with their working directory, target, output, timing, and project context intact.

Get it fromMicrosoft Store

Direct answer

How is a developer command runner different from a terminal?

DevDock turns recurring development commands into visible, reviewable tasks. Every run keeps its project, folder, working directory, execution target, exit state, timing, and retained output together, so a useful command does not disappear into shell history.

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.

Best for

Where this workflow fits.

  • Starting servers, workers, watchers, and supporting services
  • Reusing commands that need specific folders or environment inputs
  • Comparing a failed command with the last healthy run

Local project data, operating-system secret storage, read-only local audits, and no source upload.

Relevant capabilities

What DevDock brings to the job.

Daily workflow

Pin the commands and environments you use most and run them from the project overview or Today.

Read feature guide →

Command history

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

Read feature guide →

Project shortcuts

Open a registered folder in a terminal, Visual Studio Code, or File Explorer from the same workspace.

Read feature guide →

Practical workflow

From setup to a reviewed result.

  1. Add a project

    Register a local project folder and give it a clear place in the sidebar.

  2. Review the workspace

    See its folders, health, saved commands, and recent activity from one overview.

  3. Run a command

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

  4. Return from Today

    Open recent work or a pinned daily workflow without hunting for the project again.

Useful in practice

Context switching

Pin the daily workflow for each project and reopen the same environment, inputs, and recent output after a restart.

Read use case →

Safer onboarding

Give a new contributor a reviewed set of local tasks and health checks without asking them to assemble a private command notebook.

Read use case →

Docker-heavy development

See service health, published ports, resource snapshots, and host-versus-container commands without memorizing Compose syntax.

Read use case →

Related searches

One workflow, several common names.

This page focuses on developer command runner. People also describe the same or closely related job as script runner for developers, saved terminal commands, development workflow runner, task runner GUI.

script runner for developerssaved terminal commandsdevelopment workflow runnertask runner GUI

Direct answers

Questions about developer command runner.

How is a developer command runner different from a terminal?

DevDock turns recurring development commands into visible, reviewable tasks. Every run keeps its project, folder, working directory, execution target, exit state, timing, and retained output together, so a useful command does not disappear into 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.

Go deeper

Create dependable project commands, choose safe execution targets, manage long-running work, and use history to diagnose failed runs.

Read Commands, workflows, and run history
More DevDock

Browse every focused tool and workflow.

See all DevDock tools