Return to a project with its daily workflow intact

The job to be done

Pick up a project without rebuilding where you left it

Moving between a client project, your own product and a quick fix somewhere else costs more than the switch itself. You have to find the right folder, remember which servers it needs, check whether the branch is current and recall the last command that worked.

DevDock keeps that per project. Today lists recent projects, your pinned commands from all of them and the warnings that need attention. Opening a project shows what is running, its health and its daily commands on one Overview, and a command that takes input starts with the values you used last time.

Agent presence adds one more check. If Claude Code or Codex is still working in a project you are about to change, its sidebar row says so.

Recommended path

Switch projects in five short steps

Use Today as the starting point, and check the project before changing anything in it.

1. Start on Today

   Recent projects lists what you had open most recently. Quick actions holds pinned commands from every project, and Needs attention collects health warnings from all of them.

2. Check for a running agent

   Look at the project's sidebar row before switching branches or pulling. Hover the agent status to read the session title or the latest prompt.

3. Read the Overview

   Running now lists commands still active in the project. Project health shows uncommitted changes, commits waiting to push, upstream changes and missing dependencies.

4. Start the day's commands

   Run pinned commands from the Daily workflow panel. With Pro, one saved environment starts the whole local setup and shows Ready once its Readiness URL responds.

5. Move by keyboard

   Ctrl+K opens the command palette by default for any project, section or folder. Ctrl+Shift+K opens the command launcher from any Windows app, with Today's pinned commands listed first.

Capabilities involved

What tells you where a project stands

Limits to know

Limits that affect switching

DevDock Free holds three projects. If you move between more than three, DevDock Pro removes the limit.

Quitting DevDock stops the commands it started, including the processes they launched. After a restart, you start the day's commands again from the Overview, Today or a Pro environment.

Agent presence recognizes Claude Code and Codex without setup. Other tools appear only when an integration writes DevDock's heartbeat file, and an idle agent session is not shown.

Run History in Free lists the 20 newest matching runs per project. Pro lists every run kept under the retention settings, which default to 30 days and 200 runs per project.

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.

Its sections cover generated and custom commands, review before the first run, run and stop processes, build reusable workflows, read run history, protect environment values. Use it when you are ready to reproduce this workflow with your own project data.

Direct answers

Questions about this use case.