Oct 13, 2026

Summary

Building an AI agent is easy now. Running thousands of them safely in production is a different problem entirely.

AI agents have gone from demos to writing code, handling customer questions, automating workflows, and making real decisions. The hard part is no longer making agents smarter. It's keeping them reliable once they're operating at scale.

As a former VP of Engineering at Meta and now CEO and Co-Founder of Guild.ai, James Everingham has seen exactly where production systems break down. The failures come from everything around the model: context management, permissions, observability, cost controls, versioning, evaluation, and governance.

This session looks at what changes when agents stop being prototypes and start being production systems. Attendees will walk away with practical frameworks for designing agent systems that are observable, secure, reusable, and built to evolve.

Speakers

James Everingham

James Everingham

CEO @ Guild.ai

James is the CEO and co-founder of Guild.ai, the control plane for AI agents where engineers build, reuse, and evolve intelligent software together.

Most recently, James was the Vice President of Engineering at Meta Devinfra, responsible for building and running the core developer tools, services, and platforms that power Meta's products. He and his team built Meta's first internal AI agent, which delivered immediate impact on how Meta engineers use AI tooling. During his time at Meta, James co-created Diem and served as Instagram's Head of Engineering.

With a 40-year career as a manager, entrepreneur, and technology developer, James has led numerous world-class engineering teams. At Yahoo, he served as Vice President of Engineering for Yahoo's media properties after the acquisition of Luminate, an interactive image technology company he founded. His previous roles include co-founder and SVP, Engineering, at Lightspark; CTO and founding team member at LiveOps; Senior Director of Engineering at Tellme (acquired by Microsoft); and Senior Director of Engineering at Netscape Communications, where he was responsible for the flagship Netscape browser. Before joining Netscape, James held engineering and management positions at Oracle and Borland International.

Stay In The Loop