Unlock Agent Autonomy: The Runtime for AI-Native Systems
Tushar Jain
- When
- Tuesday, June 303:45 PM – 4:05 PM · 20 min
- Where
- Leadership 2San Francisco, CA · imported from ai.engineer's public schedule feed
About this session
The way software gets built in 2026 doesn't look like it did in 2024. The actors changed. Agents read and write entire codebases. Subagents spawn to chase down a flaky test, refactor a module, or triage an incident. But this shift doesn't stop at the SDLC. Agents increasingly invoke tools, interact with enterprise systems, install dependencies, call APIs, and orchestrate workflows across local machines, CI systems, cloud infrastructure, and organizational boundaries. The teams leaning into this shift are moving faster, and the gap is widening by the quarter.
But few have the confidence to let agents operate autonomously across those environments. Not because the model capability isn't there. Trust isn't. Agents can pull a poisoned dependency, invoke an untrusted tool, wipe a database, leak sensitive data, or access systems they shouldn’t. Prompt-level instructions won't close that gap, the unlock has to happen one layer down, at the runtime layer itself.
Docker spent the last decade making it safe to ship software by getting the runtime right: isolation, network policy, trusted base images, and credentials. Agents are the next workload, and the same principles apply. Tushar Jain, EVP of Engineering at Docker, walks through what the runtime layer for AI-native systems looks like in practice: hardened runtime foundations, sandboxes that constrain what agents can touch, and governance controls that limit what agents can introduce, access, and execute across local, CI, cloud, and enterprise environments. The pattern is the same on every vector: reduce the surface area of what the agent gets to decide, so the parts that matter aren't left to a prompt.
Attendees leave with a clearer framework for giving agents more autonomy safely. Engineers see how agentic applications can operate across tools and infrastructure. Security leaders get a runtime model that maps to controls they already understand. Platform teams get a way to scale agent execution without standing up a new runtime for every team.
Speaker
EVP of Engineering, Docker
Tushar Jain is Executive Vice President of Engineering at Docker.
More in AI Architects: Show my Workflow
- Your Agent Evolved. Your Evals Didn't.Tuesday, June 30 · 11:10 AM – 11:30 AM · Leadership 2
- The Last Human Code Review: Building Trust in AI-Generated CodeTuesday, June 30 · 11:40 AM – 12:00 PM · Leadership 2
- Prototyping as Leadership: How a CTO Ships with AI AgentsTuesday, June 30 · 12:05 PM – 12:25 PM · Leadership 2
- Serving 2 Million Models Without Melting: Scaling the Hugging Face HubTuesday, June 30 · 1:30 PM – 1:50 PM · Leadership 2
- IT Admin for the AI Workforce: Why Your AI Agents Will Need Their Own IT DepartmentTuesday, June 30 · 1:55 PM – 2:15 PM · Leadership 2
For developers: this programme is open data — JSON, iCal, schedule XML and an MCP endpoint.Show endpointsHide
- JSONEvery published session and speaker, in one request./aie-worldsfair-2026-import/feed.json
- iCalSubscribe in Google, Apple or Outlook Calendar./aie-worldsfair-2026-import/feed.ics
- Schedule XMLfrab / pentabarf — the format conference apps import./aie-worldsfair-2026-import/feed.xml
- MCP + RESTPoint Claude at the programme. OpenAPI 3.1 included./agents
No key, no signup, CORS open. Everything here is generated from the same data the organisers edit.