We scan new podcasts and send you the top 5 insights daily.
Rather than a single omnipotent agent handling all workflows, software will sustain a blend of horizontal agents, specialized vertical agents, and domain-rich user interfaces. Context switching and focused craft make dedicated interfaces necessary alongside agent-to-agent interactions.
As companies deploy numerous task-specific AI agents (e.g., payroll, payments), the user experience risks fragmentation. Xero's solution is a 'super agent' that manages all sub-agents, orchestrating actions, transferring information, and applying user preferences globally to create a cohesive system.
True Agentic AI isn't a single, all-powerful bot. It's an orchestrated system of multiple, specialized agents, each performing a single task (e.g., qualifying, booking, analyzing). This 'division of labor,' mirroring software engineering principles, creates a more robust, scalable, and manageable automation pipeline.
Comparing chat interfaces to the MS-DOS command line, Atlassian's Sharif Mansour argues that while chat is a universal entry point for AI, it's the worst interface for specialized tasks. The future lies in verticalized applications with dedicated UIs built on top of conversational AI, just as apps were built on DOS.
To enable a 'bring your own agent' model, applications must offer dual interfaces. A traditional UI for the human user, and a machine-controllable programming interface (MCP or API) for the AI agent. The key is that both interfaces must modify the same underlying state in real-time for seamless collaboration.
The 'agents vs. applications' debate is a false dichotomy. Future applications will be sophisticated, orchestrated systems that embed agentic capabilities. They will feature multiple LLMs, deterministic logic, and robust permission models, representing an evolution of software, not a replacement of it.
Contrary to the trend toward multi-agent systems, Tasklet finds that one powerful agent with access to all context and tools is superior for a single user's goals. Splitting tasks among specialized agents is less effective than giving one generalist agent all information, as foundation models are already experts at everything.
Legacy systems like CRMs will lose their central role. A new, dynamic 'agent layer' will sit above them, interpreting user intent and executing tasks across multiple tools. This layer, which collapses the distance between intent and action, will become the primary place where work gets done.
Traditional software required deep vertical focus because building unique UIs for each use case was complex. AI agents solve this. Since the interface is primarily a prompt box, a company can serve a broad horizontal market from the beginning without the massive overhead of building distinct, vertical-specific product experiences.
Instead of relying on a single, all-purpose coding agent, the most effective workflow involves using different agents for their specific strengths. For example, using the 'Friday' agent for UI tasks, 'Charlie' for code reviews, and 'Claude Code' for research and backend logic.
The belief that users want a single, all-in-one AI agent is flawed. A 'polyagentamorous' future is more likely, where users fluidly switch between multiple agents (like Grok, Claude, Muse) for different tasks based on their specific strengths and alignments, much like they use different apps today.