A consultant runs client work from saved agent workspaces and ticket briefs
At a glance
A consultant keeps a separate desktop and coding-agent session for each client, then cycles through active work without losing context. This workflow is listed under client work, coding agents, timesheets.
- Agents / tools
- Claude Code, Codex, Warp, Windows virtual desktops, Custom dashboard
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Set up one Windows virtual desktop per client, associate each desktop with the client's project folder or repository, and use a dashboard to save and restore its open windows and agent sessions. 2) When a request arrives, switch to that client's desktop, enter /ticket in the client agent, describe the request, and add the relevant context. 3) Rotate between active client desktops as agents work; review each result, give feedback, quality-check it, integrate it, and deliver it. 4) Keep an agent running periodically to infer billable time from the active files, ticket, client, and desktop, then fill the corresponding timesheet.
How it went
The commenter said they routinely rotate across five or six active client workspaces and agents in a day, and described getting work done very quickly.
Worth knowing
The workflow depends on keeping client work separated into desktop and project folders. The author still reviews, quality-checks, integrates, and delivers the agent's output.
