---
title: "How E2B Uses Its Own Sandboxes to Develop E2B with AI"
description: "Claude agents work E2B's backlog inside E2B sandboxes: an architect writes the work package, an engineer builds it, AI reviews it and a person signs off before production."
date: "2026-11-01T21:00:22-08:00"
author: tomas-srnka
categories:
  - talks
thumbnail: "./thumbnail.png"
thumbnailAlt: "Tomas Srnka on stage at #nobullshit.camp 2026 in Bratislava, next to the words Agents build E2B"
talk:
  youtube: psZC8H1DUGw
  length: "28:06"
  format: talk
  event: "#nobullshit.camp 2026"
  city: Bratislava
  recordedBy: Labyrinth Labs
  poster: "./poster.jpg"
  speakers:
    - tomas-srnka
  chapters:
    - { at: "0:00", title: Introduction and what E2B builds }
    - { at: "2:24", title: E2B in numbers }
    - { at: "3:40", title: "Open-source runtime, cloud and BYOC" }
    - { at: "4:30", title: "MicroVMs, templates and the 100 ms target" }
    - { at: "6:46", title: Defining a template and running a task }
    - { at: "8:11", title: Why agents work the backlog }
    - { at: "11:00", title: The architect harness and the work package }
    - { at: "12:53", title: Agentic review before a human sees the PR }
    - { at: "13:42", title: "One task, one sandbox, one branch" }
    - { at: "15:20", title: From Linear ticket to pull request }
    - { at: "16:23", title: "Live demo: fixing a production bug in a sandbox" }
    - { at: "20:48", title: Two and a half minutes to a pushed PR }
    - { at: "22:13", title: "Q&A: the 100 ms target, Firecracker and verification" }
    - { at: "24:03", title: "Q&A: tickets, models and metrics" }
    - { at: "26:17", title: "Q&A: Docker, skills and correcting agents" }
  takeaways:
    - at: "5:25"
      text: A template is built once and paused. Every sandbox resumes a fork of it, so a Chrome or app started at build time is already running.
    - at: "9:15"
      text: Tickets reach agents as Markdown, not links. The architect turns each one into a work package before an engineer agent touches code.
    - at: "11:47"
      text: A work package carries more than the outcome. It says where to look in the codebase, how to start the dev environment and how to test.
    - at: "12:53"
      text: AI reviewers check quality and bugs on every PR. A person still checks the fundamentals before merge, especially on critical paths.
    - at: "13:42"
      text: One task, one sandbox, one branch. Nothing runs on a laptop, a shared box or production.
    - at: "20:48"
      text: The demo ticket went from work package to pushed PR in about two and a half minutes, with a screenshot as proof of the fix.
    - at: "27:19"
      text: Bugs that reviewers catch are fed back into the harness, so the agents stop repeating them.
  links:
    - { label: Sandbox forking docs, href: "https://docs.e2b.dev/sandbox/fork" }
    - { label: Template quickstart, href: "https://docs.e2b.dev/template/quickstart" }
    - { label: E2B runtime on GitHub, href: "https://github.com/e2b-dev/runtime" }
    - { label: E2B is hiring, href: "https://e2b.dev/careers" }
---

Tomas walks through how E2B's engineering team hands its backlog to agents. An architect harness that knows the codebase turns a Linear ticket into a work package. An engineer agent builds it inside an E2B sandbox on its own worktree and branch, AI reviewers check the pull request, and a person signs off before anything reaches production.

The live demo takes a real bug from the team's backlog to a pushed PR in about two and a half minutes, screenshot included. The Q&A covers the 100 ms startup target, Firecracker versus containers, how verification criteria are written, which models the team runs, what it measures, and how corrections flow back into the harness.