<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agents on Viswa Balaji</title><link>https://viswabalaji.github.io/tags/agents/</link><description>Recent content in Agents on Viswa Balaji</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 28 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://viswabalaji.github.io/tags/agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Copilot Harness in Foundry Agent Service</title><link>https://viswabalaji.github.io/technical/microsoft-copilot-harness-foundry/</link><pubDate>Wed, 28 Oct 2026 00:00:00 +0000</pubDate><guid>https://viswabalaji.github.io/technical/microsoft-copilot-harness-foundry/</guid><description>&lt;p&gt;This week we launched the &lt;strong&gt;Microsoft Copilot harness in public preview in Foundry Agent Service&lt;/strong&gt;. You define the agent declaratively with instructions, tools, skills, and guardrails, and Microsoft manages the execution system that runs it.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://viswabalaji.github.io/images/technical/microsoft-copilot-harness/microsoft-copilot-harness-high-level.png" alt="Governed reasoning and isolated tool execution: prompt and Routine inputs, a Foundry model and Microsoft Copilot harness, a named skill, governed tools, Code Interpreter, and a separate durable conversation store."&gt;&lt;/p&gt;
&lt;p&gt;The harness is the same multi-model execution layer Microsoft has standardized on across its Copilot experiences, and &lt;a href="https://www.linkedin.com/posts/satyanadella_were-redefining-the-sdlc-for-the-agentic-ugcPost-7521256751313375232-ObpB/"&gt;Satya announced it&lt;/a&gt; at GitHub Universe as part of a broader push to redefine the software development lifecycle for the agentic era. &lt;a href="https://blogs.microsoft.com/blog/2026/10/28/introducing-the-microsoft-copilot-harness-unlocking-the-potential-of-truly-multi-model-agentic-work/"&gt;Tina Schuchman and Vladimir Fedorov&amp;rsquo;s post&lt;/a&gt; explains why a shared harness matters: models change quickly, and every improvement to the harness now reaches agents built on Foundry too. Jeff Hollan and I wrote the &lt;a href="https://devblogs.microsoft.com/foundry/microsoft-copilot-harness-in-foundry/"&gt;launch post on the Foundry blog&lt;/a&gt;, which &lt;a href="https://www.linkedin.com/feed/update/urn:li:activity:7521266220462018560/"&gt;Satya also shared&lt;/a&gt;. Here I go deeper with a fuller example.&lt;/p&gt;</description></item><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><item><title>Teaching Agents Intuition: Programmatic Tool Chain Caching</title><link>https://viswabalaji.github.io/technical/programmatic-tool-chain-caching/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://viswabalaji.github.io/technical/programmatic-tool-chain-caching/</guid><description>&lt;h2 id="the-recomputation-problem"&gt;The Recomputation Problem&lt;/h2&gt;
&lt;p&gt;Ask an agent to analyze customer churn. It explores tool compositions, tries different approaches, settles on a working sequence. Thirty seconds later, it succeeds. Ask it again tomorrow. It starts from scratch. Same exploration, same trial and error, same thirty seconds. No memory of what worked. No learning.&lt;/p&gt;
&lt;p&gt;Software engineers learned decades ago to cache expensive computations and reuse proven solutions. AI agents are still figuring out the same problems repeatedly.&lt;/p&gt;</description></item></channel></rss>