DEV Community

Martin Grüner
Martin Grüner

Posted on Originally published at martingruner.com

Making active local development work visible in DevDock 1.4

A project dashboard can list repositories, commands, and containers, yet still miss the state that matters most: what is changing right now.

For DevDock 1.4, I focused on three pieces of active state.

See when an agent is working in a project

DevDock now shows when Claude Code or Codex is working in a registered project. For Claude Code, it reads the recent local transcripts already stored under ~/.claude/projects, including sessions started from a terminal or the desktop app. The project list can show the session title or latest prompt without an account connection.

That visible state helps prevent accidental overlap: switching branches, starting a build, or editing the same files while an agent is active.

Keep long Git operations within reach

Long Git operations no longer need to hold the workspace open. A new Activity center lists running operations and recent results.

Hiding a progress window leaves the operation running. Selecting it in the Activity center reopens the current step and live output. Pull-before-push still continues into the original push after a successful pull.

Stop the whole command process tree

Stopping a saved command now stops its complete process tree. Scripts such as npm run dev often start a child dev server or watcher. Ending only the parent can leave a port occupied, so DevDock now tracks and stops every process the command starts, including when the app closes.

Smaller improvements that remove friction

The release also improves toolchain detection, event-stream reconnection, action-specific status, Git authentication feedback, command controls, and Microsoft Store purchase restoration.

The complete release article includes screenshots, user-facing details, and update instructions:

Read the DevDock 1.4 release notes

Top comments (0)