Let's Talk About FOMAT: Fear of Missing Agent Time — Michael Richman, Cmd+Ctrl

Key Concepts

• FOMAT (Fear of Missing Agent Time): The anxiety or inefficiency caused by being away from a development machine while an AI agent is either blocked, waiting for input, or has completed a task.
• Agentic Choreography: The emerging software development paradigm where developers manage multiple parallel AI agent sessions, acting as orchestrators rather than just solo coders.
• Command and Control: A tool developed by Michael Richmond to provide a unified, cross-platform interface for monitoring and interacting with various coding agents.
• Single Pane of Glass: A centralized dashboard architecture that aggregates agent sessions from different environments (local machines, cloud VMs, various IDEs/CLIs).
• Agent Idleness: The wasted time when an agent is paused, waiting for human intervention, which scales negatively as task duration increases.

---

1. The Problem: FOMAT and Agent Idleness

Michael Richmond identifies a critical friction point in modern AI-assisted development: FOMAT. As coding tasks evolve from 5-minute snippets to 5-day autonomous processes, the "babysitting" requirement becomes a bottleneck. Developers currently suffer from:

• Context Fragmentation: Managing multiple sessions across different tools (Claude Code, Cursor, Gemini, Codex) leads to cognitive overload.
• Physical Tethering: The inability to monitor or unblock agents while away from the primary development machine.
• Visibility Gaps: Not knowing when an agent has stalled or requires a decision, leading to significant downtime.

2. Solution: The "Command and Control" Framework

Richmond introduced "Command and Control," a system designed to decouple agent interaction from the terminal/IDE.

Core Features:

• Unified Interface: A mobile/web application that aggregates sessions from any coding agent.
• Push Notifications: Real-time alerts when an agent requires input or completes a task.
• Session Management: Categorization of sessions into "Notifications," "On My Radar," "Recent," and "Archive."
• Overview Dashboard: A summary feature that uses recent message history to provide a "stand-up" style status report for all active agents.
• Remote Interaction: The ability to issue commands, resume sessions, or start new tasks from a mobile device or watch.

3. Technical Architecture

The system is designed to be coding-tool agnostic and modular:

• Daemon Layer: A lightweight process runs alongside each agent platform (e.g., Claude Code, Cursor). This layer is open-source and monitors the agent's lifecycle.
• Control Plane: An aggregation layer that collects data from various environments (local Mac, cloud VMs, etc.).
• API/UI Layer: The mobile/web interface that communicates with the control plane to provide the "single pane of glass" experience.

4. Key Arguments and Perspectives

• The New "Flow": Richmond argues that the traditional definition of "flow" (hyper-focus on one task) is being replaced by Agent Choreography. Success now depends on the developer's ability to move between agents, unblock them, and redirect their efforts efficiently.
• Cognitive Load Management: He emphasizes that managing multiple agents is mentally exhausting. By offloading the monitoring to a notification-based system, developers can reclaim time away from the screen, which is essential for creative problem-solving.
• The Reality of Autonomy: Despite the industry hype, agents are not yet fully autonomous. Richmond asserts that we must build tools that acknowledge this "high-touch" reality rather than pretending agents can operate indefinitely without human oversight.

5. Notable Quotes

• "We all want to believe that our agents are low touch and high autonomy. But we all know the truth, right? It's back and forth, it's babysitting."
• "The new flow comes from the elegance of that choreography and the results on the other side."
• "We need systems that make it possible to reach our agents during those breaks, wherever we might be and whenever that happens. And that is how we truly alleviate the fear of missing agent time."

6. Synthesis and Conclusion

The transition to agentic coding requires a shift in tooling. As tasks become longer and more complex, the developer's role is shifting from "writer of code" to "orchestrator of agents." The Command and Control system addresses the inherent limitations of current agent frameworks by providing visibility and remote access. By centralizing session management and implementing intelligent notification systems, developers can mitigate the anxiety of FOMAT, reduce agent idleness, and maintain a more sustainable, productive workflow that allows for necessary time away from the keyboard.