Stop prompting your AI agents. Start managing them.
The speaker discusses the shift from traditional agent prompting to agent management, highlighting the limitations of local Kanban board approaches and advocating for cloud-based VPS solutions with multiple communication channels to effectively manage autonomous AI agents across projects.
Summary
The transcript opens with an observation that while many people discuss orchestrating multiple agents autonomously, few actually implement it successfully. Most implementations still rely heavily on human-in-the-loop prompting, even when agents are organized in loops or hierarchies with sub-agents.
The speaker then transitions to their personal insight: moving from the role of 'agent prompter' to 'agent manager' represents a fundamental shift in approach. They describe initial attempts using Kanban boards as a management tool, which seemed promising for task initiation but proved problematic in practice. The speaker identifies two specific challenges: difficulty maintaining multi-turn interactions (beyond 2-3 turns) and the limitations of running agents on local infrastructure.
The solution the speaker implemented involved two key changes: migrating from local runtime to cloud-based VPS hosting and establishing multiple communication channels to interact with agents. This infrastructure change enables flexibility in how agents are prompted and managed—through text messages, integration with Linear (a project management tool), or direct shell prompts. This multi-channel approach represents a more sophisticated agent management paradigm compared to single-interface solutions.
Key Insights
- Despite widespread discussion of autonomous multi-agent orchestration, most implementations still rely heavily on human-in-the-loop prompting rather than true autonomy
- Kanban boards are insufficient for managing agent workflows because they struggle to maintain interactions beyond 2-3 turns and lack proper intervention capabilities
- Local runtime environments do not work effectively for agent management, requiring migration to cloud-based infrastructure
- Multi-channel communication interfaces (text, Linear integration, shell prompts) enable more flexible and effective agent management than single-interface approaches
- The conceptual shift from 'agent prompter' to 'agent manager' represents a fundamental change in how practitioners approach autonomous agent systems
Topics
Transcript
[0:00] We have heard a lot of people talk about orchestrating many agents autonomously across a project. We actually haven't seen many people do it. I still see a lot of prompting even if you're prompting into a loop [music] or a goal as far as sub-agents. People are really still human in the loop. >> What really clicked for me was starting to move away from being agent prompter to agent manager. The first thing that everybody tried was a Kanban board. You would put all these things in there and move them back and forth. What I found is that it was hard to get two, three, four turns. Through that, it was easy to [0:31] get to…
Full transcript available for MurmurCast members
Sign Up to AccessMore from How I AI
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.
Intent engineering beats prompt engineering every time
The speaker emphasizes the importance of integrating AI, specifically Claude, into daily workflows by creating reminders to seek its assistance. This approach allows for collaborative problem-solving, transforming static prompts into dynamic conversations.