<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browser-Tools on Viswa Balaji</title><link>https://viswabalaji.github.io/tags/browser-tools/</link><description>Recent content in Browser-Tools on Viswa Balaji</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 12 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://viswabalaji.github.io/tags/browser-tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Daytona Compute + PyAI Conference</title><link>https://viswabalaji.github.io/technical/daytona-pyai-conference/</link><pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate><guid>https://viswabalaji.github.io/technical/daytona-pyai-conference/</guid><description>&lt;p&gt;Last week at Daytona Compute and PyAI conferences, the same architectural pattern dominated: agent-in-sandbox. These agents run in full OS environments with forking, checkpointing, and multi-day execution. &lt;a href="https://www.daytona.io/"&gt;Daytona&lt;/a&gt; demonstrated 50,000 concurrent sandboxes in 2 minutes 13 seconds. Multiple companies showed agents running for days.&lt;/p&gt;
&lt;p&gt;Five patterns from the floor:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Sandbox architecture choices&lt;/strong&gt;: agent-in-sandbox versus sandbox-as-tool patterns&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Progressive tool disclosure&lt;/strong&gt;: using knowledge graphs to manage complexity, not just for skills but for code understanding&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Browser vs computer use&lt;/strong&gt;: when each approach makes sense&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CPU bottleneck&lt;/strong&gt;: why there&amp;rsquo;s a high spike in CPU demand again&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Parallel execution&lt;/strong&gt;: multiple long-running agents per user&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="sandbox-patterns-agent-in-vs-tool"&gt;Sandbox Patterns: Agent-In vs Tool&lt;/h2&gt;
&lt;p&gt;Two distinct patterns emerged. In &lt;a href="https://blog.langchain.com/the-two-patterns-by-which-agents-connect-sandboxes/"&gt;agent-in-sandbox&lt;/a&gt;, the agent runs inside a full OS environment with persistent state, installing packages and maintaining processes. The sandbox becomes the workspace. In sandbox-as-tool, the agent operates outside and calls the sandbox for specific stateless execution via APIs from providers like E2B, Modal, Daytona, or Runloop.&lt;/p&gt;</description></item></channel></rss>