AI can write code. What does it take to ship?Join AI DevCon, Nov 2-4
Book a Demo
CareersPricingDocs
Log inBook a Demo
Cornelia Davis

SPEAKER

Cornelia Davis

Builder, Teacher, Change Junky

Cornelia's career has spanned several major shifts in software, from image processing algorithm development to web-centric computing, and then cloud-native software, infrastructure and platforms (Cloud Foundry, Kubernetes and more). At Temporal she is helping to bring a new programming paradigm to an industry increasingly in need of one - a need that has accelerated dramatically with the advent of modern AI systems. She is the author of Cloud Native Patterns: Designing change tolerant software.

LinkedInWebsite

Upcoming sessions

See complete program

3 November

3:15 PM · 30 min

52AConference Session

Your Agent Just Wrote a Tool—and Ran It. You Need More than a Sandbox.

AI agents are already well entrenched in the traditional software delivery lifecycle: they build, review, test, and deploy code, yet even as we automate more and more, we are still talking about a controlled build-test-deploy cycle.

But what happens when an agent writes and executes new code not as a deliverable, but as a tool for accomplishing its current goal? There is no pull request, deployment pipeline, or human checkpoint. This is testing in production in its most literal form.

The DevOps movement made testing in production viable by creating safety nets: containers, progressive delivery, observability, and rapid rollback. Runtime code generation by autonomous agents needs its own safety net, and a sandbox is only the beginning. A sandbox controls where code runs; it does not fully control what that code can do.

In this demo-heavy session, we’ll examine the execution model required for agents to safely create and run code without human intervention. Generated code must remain inside the host agent’s governed context: inheriting its tool permissions, policy constraints, and relevant event history, without acquiring capabilities the agent itself does not possess.

We’ll introduce an execution environment built around these principles, explore its architecture, and share practical patterns for making runtime code generation observable, auditable, and bounded.