Agents went from demo to production faster than the engineering practices around them could mature. The agent loop — plan, call tools, reflect, repeat — is the most visible part of an agent system, but it's a small fraction of what's needed to run one reliably and securely. Underneath the loop sits a stack of concerns that frameworks don't solve for you: portability across rapidly obsoleting models, durable state for long-running runs, deployment pipelines that ship daily, runtime sandboxes for code that agents generate and execute, and the observability you need to debug a system that keeps changing its mind. Each is a discipline in its own right, with conventions still being invented. In this track, we'll work through each layer with practitioners shipping agents in production today, drawing out the lessons that turn a compelling demo into a system you can stake a business on.
From this track
Platform Engineering for Agents
Agentic tools amplify what’s already in the codebase. The agent works through your code, your architecture decisions, and the documentation around them. It follows what it can read and guesses at the rest.
Mark Khuzam
Senior Software Engineer @Netflix, Previously Led the Consumer Web Platform Team @OpenTable
