Andy Triedman of Theory Ventures, a venture firm that invests in AI startups, said agents are “really hamstrung if they cannot take actions in these systems” (episode 79, 35:54), and called that ability an absolutely necessary prerequisite for building a software factory effectively (36:30). How much simulation that takes depends on the domain. For his personal app, he gives agents read-only access to the database and runs an iOS simulator (35:03). A cybersecurity company he discussed has to simulate ten or fifteen closed-source enterprise production systems, along with large amounts of simulated behavior and logs (35:54).
The tradeoff is engineering effort. Triedman said the most sophisticated companies he works with dedicate whole teams to building these environments and to configuring them to resemble different customers, so agents can work in a close facsimile of production and then transfer to the real world (36:30). He also said agents should never have write access to any data you have (40:39), and that where data is sensitive, simulated copies or an internal mock of customer data are “basically as effective” (41:09). Least privilege is the general rule behind that advice. This is his view from the companies he works with, not an industry standard. Episode 79’s show notes credit Svix, Walrus Memory and Inngest as season-four presenting sponsors, and G2i, which reviews RL environments and evals, as the episode’s sponsor.
Research benchmarks use the same idea to score agents. AppWorld builds nine everyday apps behind 457 APIs, fills them with simulated activity for about 100 fictitious users, and checks the final state of the apps, including for unexpected changes the authors call collateral damage. τ-bench simulates the customer with a language model and compares the database at the end of a conversation with the expected state.
Worked example: a team wants an agent to triage error alerts and propose fixes for a billing service. Instead of pointing it at production, the team builds a simulated environment: a seeded copy of the database with mock customer records, a stub of the payments API that logs each call instead of executing it, and 50 replayed incidents with known root causes. The agent finds the right root cause in 41 of 50 runs, or 82%. In 3 runs it tried to update mock billing records it was only meant to read. The 82% holds only as far as the replayed incidents resemble real ones. The three write attempts are a permissions finding, caught before any real customer record was at risk: make the agent’s access read-only before it reaches production, and refresh the incidents from real traffic so the success rate keeps meaning something.
A simulation environment is about fidelity: how closely the systems an agent acts on resemble production. Sandboxing is about the execution boundary that limits what the agent can reach. An agent can run in a sandbox with no simulated systems at all, and a simulation is only as safe as the permissions around it.
Hear it from the guest
“They have entire teams that are spending basically all of their time just building these simulation environments.”
Quotes lightly edited to remove filler words.
Sources
- Trivedi et al.: AppWorld, a controllable world of apps and people for benchmarking interactive coding agents (ACL 2024) — Describes an execution environment of nine day-to-day apps operable through 457 APIs, populated with simulated activity for about 100 fictitious users, with state-based tests that also check for unexpected changes; abstract checked November 7, 2026.
- Yao et al.: τ-bench, a benchmark for tool-agent-user interaction in real-world domains — Simulates the user with a language model, gives the agent domain API tools and policies, and compares the database state at the end of a conversation with the annotated goal state; abstract checked November 7, 2026.