1 min readfrom InfoQ

Presentation: From Copy-Paste to Composition: Building Agents Like Real Software

Our take

Jake Mannix’s presentation, "From Copy-Paste to Composition," addresses a critical evolution in AI agent design. Moving beyond rudimentary architectures, Mannix outlines a framework for building agents akin to robust software – versioned, encapsulated "virtual tools." This approach leverages an intermediate protocol layer to enable key capabilities like interface mapping and dynamic schema projection. Crucially, it incorporates runtime taint tracking to proactively mitigate data exfiltration risks, all while maintaining development velocity.
Presentation: From Copy-Paste to Composition: Building Agents Like Real Software

The conversation around AI agents has rapidly moved beyond initial excitement into a space demanding serious engineering rigor. Jake Mannix’s recent presentation, "Presentation: From Copy-Paste to Composition: Building Agents Like Real Software," highlights a crucial shift – moving away from ad-hoc, easily-broken architectures towards more structured, maintainable systems. The current landscape, as Mannix describes it, resembles a chaotic “1970s BASIC” environment, which is a stark contrast to the sophisticated applications we expect from modern software. This resonates with observations from other corners of the AI safety and security space; for example, Anthropic’s detail on containing Claude across various environments [Anthropic Details How It Contains Claude Across Web, Code, and Cowork] demonstrates the growing awareness of the need for robust containment strategies. The fundamental challenge is moving beyond simply *building* agents to building *reliable* and *secure* agents, and Mannix’s proposed protocol layer offers a compelling route toward that goal.

Mannix's core concept – the intermediate protocol layer – is particularly interesting because it addresses several critical concerns simultaneously. Versioning and encapsulation, achieving what he terms "virtual tools," mirror established software engineering practices, bringing much-needed stability. The inclusion of interface mapping, dynamic schema projection, and runtime taint tracking is a significant advancement. Taint tracking, in particular, proactively addresses the very real risk of data exfiltration, a concern increasingly highlighted in articles like "Detecting Vulnerabilities in Agent Skills with SkillSpector" [Detecting Vulnerabilities in Agent Skills with SkillSpector: From Green Checkmark to Real Security Judgment], which underscores the challenges even static analysis tools face in accurately identifying vulnerabilities. The fact that this design aims to achieve these benefits *without* sacrificing velocity is a key differentiator—it’s not about slowing down innovation, but about ensuring it’s done responsibly. It’s a recognition that security and agility are not mutually exclusive, but rather interdependent goals. As Google Cloud’s GKE Security Blueprint [GKE Security Blueprint Joins Growing List of Cloud AI Frameworks] illustrates, the broader industry is actively developing frameworks to secure AI workloads, and Mannix's approach aligns with this trend.

The implications of this shift are profound. Currently, many AI agent implementations feel fragile and difficult to debug, let alone scale or secure. A move towards composable, versioned agents built on a standardized protocol would dramatically improve their reliability and predictability. This not only benefits developers building agents but also empowers users who rely on them. Imagine a world where AI agents are as dependable and trustworthy as the applications we use every day – that’s the potential Mannix’s approach unlocks. It promises a shift from treating agents as experimental projects to viewing them as first-class software components, integrated seamlessly into existing workflows. A well-defined protocol layer creates a foundation for specialized tooling, improved testing, and ultimately, a more mature AI agent ecosystem. This should reduce the risk of unexpected behavior and allow for more sophisticated integration with other systems.

Ultimately, Mannix’s vision represents a move away from the "move fast and break things" mentality that has characterized early AI development and towards a more sustainable and responsible approach. The challenges of building truly reliable and secure AI agents are significant, but the rewards – increased productivity, reduced risk, and greater trust – are well worth the effort. One key question to watch is how readily developers will adopt this architectural pattern. The complexity of implementing a protocol layer could be a barrier to entry, but the long-term benefits, particularly in enterprise environments, are likely to outweigh the initial investment. Will the industry embrace this move towards composable AI agents, or will we continue to see a proliferation of brittle, ad-hoc solutions?

Jake Mannix discusses moving AI agents past chaotic "1970s BASIC" architectures. He shares how implementing an intermediate protocol layer allows engineering leaders to build versioned, encapsulated "virtual tools." This design enables interface mapping, dynamic schema projection, and runtime taint tracking to proactively eliminate data exfiltration risks without slowing velocity.

By Jake Mannix

Read on the original site

Open the publisher's page for the full experience

View original article