Stop Chatting With AI. Start Orchestrating It
The speaker demonstrates AI orchestration tools that allow users to manage multiple AI agents simultaneously through a dashboard interface. The system shows when agents need permissions and allows users to grant or deny access to various operations.
Summary
The speaker presents a new paradigm where users become AI orchestrators rather than individual chatbot users, managing multiple AI agents through a centralized interface. The demonstration shows a dashboard that provides real-time visibility into agent activities and alerts users when agents require permission to perform certain actions. Users can grant permissions directly from the top-level view without diving into individual agent interfaces, and can also modify agent privileges to allow automatic execution of certain commands. However, the speaker acknowledges a user experience challenge where non-technical users are confronted with technical elements like bash commands when reviewing permission requests. To address this, they suggest that users can copy these technical prompts and ask another AI instance to explain what the commands mean, making the system more accessible to non-technical users.
About this episode
JJ recommends thinking about the repetitive tasks that drain your energy—first-drafting emails, preparing for meetings, writing social posts, organizing files. Each of those becomes a skill. Over time, you build a library of skills that handle the mundane work, freeing you to focus on creative and strategic decisions. The goal isn't to eliminate your job; it's to eliminate the parts of your job you hate.
Key Insights
- The speaker argues that users are transitioning from being developers to AI orchestrators who can manage multiple agents simultaneously
- The speaker demonstrates that the orchestration system provides a top-level dashboard view that shows which agents need attention and allows quick permission granting
- The speaker acknowledges that the system creates a user experience contradiction by presenting bash commands to non-technical users, but suggests using another Claude instance to explain technical commands
Topics
Transcript
[0:00] You might not be a developer, you're now an AI orchestrator. You can run many agents at once and have this top-level view to be able to just quickly see which agent needs your attention and just give them those permissions or to pop back in. So, right now we do see that, "Hey, this agent needs our attention." We can go in and review that, and it's actually just asking us if we want to allow this. So, without even having to go in there, I can just allow that. I could go into that connector and change his privileges just to say always allow, so I don't have to do that. But, in this case, that was…
Full transcript available for MurmurCast members
Sign Up to AccessMore from How I AI
Onboard your employees to Cowork in 15 minutes with this system
The transcript describes a workstation operating system that streamlines employee onboarding through an intuitive chat-based interface. The system automates tool connections, role confirmation, colleague mapping, calendar integration, and personalization to get new employees productive from day one.
Your prompt is a spec, and a good spec is the whole game
A prompt acts as a specification that defines quality criteria for AI outputs. By clearly articulating 5-10 defining characteristics of what makes something good (whether a garment, photo, or illustration), you provide the AI with the same level of detail a human creator would need to produce excellent results.
How I use ChatGPT to run my fashion business
Yana Welander demonstrates how she built an AI-native fashion brand using ChatGPT and Codex as her technical co-founder, automating design, production, and business operations from sketches to manufacturing and e-commerce. She shares how AI unlocks previously impossible garments while highlighting remaining challenges in pattern generation and realistic image rendering.
The biggest barrier to AI adoption is not fear of technology. It's the absence of muscle memory.
The speaker argues that the primary barrier to AI adoption is not fear but lack of muscle memory—the habitual use of AI tools. Success requires building collaborative practices through empathy, accessible training, and establishing regular workflows rather than overcoming technological anxiety.
Staying in Gmail means none of your AI work compounds
The speaker discusses how staying within Gmail limits the compounding value of AI-assisted work and writing, and demonstrates a workflow using Claude to enhance Gmail's functionality by adding formatting, links, and draft management capabilities.