Managing Agent Workflows with Cmd+Ctrl
AI Engineergo watch the original →
the gist
Cmd+Ctrl is a cross-platform control plane that aggregates coding agent sessions, providing mobile notifications, remote interaction, and a unified dashboard to eliminate agent idle time.
Solving Agent Idleness
Michael Richman introduces Cmd+Ctrl to address "Fear of Missing Agent Time" (FOMAT), a workflow bottleneck where developers lose productivity because agents sit idle in terminal sessions waiting for human input. The system functions as a centralized control plane that bridges the gap between local terminal-based agents and mobile or web interfaces, allowing developers to monitor, unblock, or initiate tasks from anywhere.
System Architecture and Functionality
Cmd+Ctrl operates via a daemon layer that runs alongside various agent platforms, including Claude Code, Cursor, Codex, and Gemini CLI. This daemon monitors the agent's lifecycle and communicates state changes to a shared control plane. Key features include:
- Unified Dashboard: A single interface aggregates sessions across multiple machines, such as local Macs or cloud-based VMs, providing a "standup" summary of recent activity.
- Push Notifications: The system triggers alerts when an agent completes a task or requires user intervention, allowing developers to respond via mobile device or watch.
- Remote Interaction: Users can resume sessions, issue new prompts, or start entirely new agent tasks from the mobile app, which then syncs back to the terminal environment.
- Open-Source Daemon: The underlying daemon layer is open-source, enabling integration with custom agent frameworks or additional CLI tools.
The Shift in Developer Flow
Richman argues that agentic coding has shifted the definition of developer "flow" from hyper-focused individual task execution to the orchestration of multiple parallel agents. By providing a single pane of glass for these sessions, Cmd+Ctrl aims to reduce the cognitive load of managing multiple concurrent threads and allows developers to step away from their machines without losing visibility into their agentic workflows.