Descriptions:
🔥 Hot take: An agent you can’t SEE is an agent you can’t improve.
Spinning up 20 agents in a loop and looking the other way isn’t agentic engineering, it’s gambling with tokens, its vibe coding…
🎥 VIDEO REFERENCES
– Learn Cmux Codebase: https://github.com/disler/learning-cmux-with-agents
– Cmux: https://cmux.com/
– Five Pillars of Agentic Engineering: https://youtu.be/2KcITKKJikA
– Pi Agent Teams Video: https://youtu.be/M30gp1315Y4
🚀 BECOME AN AGENTIC ENGINEER
https://agenticengineer.com/tactical-agentic-coding?y=WAFUMBLOjHo
The AI labs WANT you token-maxing. I’d rather give every one of my agents agentic access and watch Cmux solve the three multi-agent orchestration problems that are quietly killing your agentic speed.
🚀 In this video, I (IndyDevDan) learns Cmux live: the way I learn every new tool, with AI coding agents driving the whole session. Problems first, tools second. We line up three multi-agent orchestration problems every engineer building agent teams runs into: no programmatic access, no way to monitor and improve, and the slow grind of booting an agent team by hand: and we test whether Cmux (and the tried-and-true tmux) can actually solve them. The answer comes down to one word: agentic access.
🔥 Watch as we scale from a single throwaway workspace up to an 8-agent hot fix team racing toward a solution. Claude Code, codex, and Pi agent running GLM-5.2 and minimax-m3 all attack the same problem in parallel: first agent to the goal post wins, then notifies the orchestrator. This is scaling your compute to scale your impact, fully visible, no black boxes. We boot 8 agents across 4 teams with 4 in-app browsers, and any agent can prompt any agent: a flat communication channel that still keeps an orchestrator, leads, and workers in their lanes.
🛠️ The pattern I keep coming back to is three-tier agent orchestration: orchestrators prompt the leads, leads prompt the specialized agent experts. Cmux controls panes, windows, and surfaces with four simple moves: send, read, open, close. So your agents can drive terminals at the speed of agents, not the speed of humans. I show the exact just-file one-tap command I use to instant-launch a fresh agent team for the thousandth time, because booting agents by hand kills the agentic speed.
💡 The core lesson: if a tool doesn’t have agentic access, I don’t give it another second of my time. Agentic access is one of the five pillars of agentic engineering — and it’s why I reach for Cmux over a single terminal or even sub-agents prompting in a box. Monitoring isn’t optional. An agent you can’t see is an agent you can’t improve. That’s the line between vibe coding and agentic engineering, and it’s the whole reason we rise with the ceiling instead of sinking to the floor.
🌟 Whether you’re orchestrating Claude Code fleets, customizing your Pi agent harness, or designing your own multi-agent orchestration patterns with agent teams of AI coding agents, this video hands you the mental model, the control loop, and the workflow to learn with AI agents and command your fleet. Stop token-maxing. Start orchestrating.
Stay focused and keep building.
Dan
📖 CHAPTERS
00:00 Multi-Agent Orchestration Patterns
02:02 Agent Orchestration Problems
05:40 Cmux in 3 Minutes
07:14 How Your Agents Control Cmux
10:17 Cmux Grids, Terminals, and Agent Fleets
18:53 8 Agent Hot Fix Team: Race and Notify
23:01 8 Agents, 4 Teams, 4 Browsers
26:04 How I’m Using Cmux for Instant Sessions
#agenticengineering #aicoding #terminal
