<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Condukt blog</title>
    <link>https://condukt.tuist.dev/blog/</link>
    <description>An Elixir framework for defining and running AI agents.</description>
    <language>en-US</language>
    <atom:link href="https://condukt.tuist.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
    
    <lastBuildDate>Tue, 19 May 2026 00:00:00 GMT</lastBuildDate>
    
    <item>
      <title>Microsandbox support in Condukt</title>
      <link>https://condukt.tuist.dev/blog/microsandbox/</link>
      <guid isPermaLink="true">https://condukt.tuist.dev/blog/microsandbox/</guid>
      <pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate>
      <author>The Tuist team</author>
      <description>Condukt can now run agent tool calls inside a local microVM through Microsandbox, with the same tools and the same agent definition.</description>
    </item>
    
    <item>
      <title>The network is the open side of the sandbox</title>
      <link>https://condukt.tuist.dev/blog/the-network-is-the-open-side-of-the-sandbox/</link>
      <guid isPermaLink="true">https://condukt.tuist.dev/blog/the-network-is-the-open-side-of-the-sandbox/</guid>
      <pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
      <author>The Tuist team</author>
      <description>Sandboxing the filesystem and processes is the easy part. The network is the surface most stacks leave open, and the one that matters most as agents start touching real systems. Here is how we are closing it in Condukt, and the missing piece we are watching for.</description>
    </item>
    
    <item>
      <title>Coding agents as runtimes</title>
      <link>https://condukt.tuist.dev/blog/coding-agents-as-runtimes/</link>
      <guid isPermaLink="true">https://condukt.tuist.dev/blog/coding-agents-as-runtimes/</guid>
      <pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
      <author>The Tuist team</author>
      <description>Codex and Claude are already tuned coding harnesses. Condukt should meet them where they are and orchestrate them as runtimes.</description>
    </item>
    
    <item>
      <title>Tool calls in a pod you already run</title>
      <link>https://condukt.tuist.dev/blog/kubernetes-sandbox/</link>
      <guid isPermaLink="true">https://condukt.tuist.dev/blog/kubernetes-sandbox/</guid>
      <pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
      <author>The Tuist team</author>
      <description>We just shipped a Kubernetes sandbox for Condukt. One pod per session, the same agent definition, the same tools.</description>
    </item>
    
    <item>
      <title>Where an agent&#39;s tools should run</title>
      <link>https://condukt.tuist.dev/blog/sandboxes-for-tool-calls/</link>
      <guid isPermaLink="true">https://condukt.tuist.dev/blog/sandboxes-for-tool-calls/</guid>
      <pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate>
      <author>The Tuist team</author>
      <description>We just landed sandboxes in Condukt. Same agent, swap where the tool calls actually execute. Here is the thinking behind it.</description>
    </item>
    
    <item>
      <title>Secrets belong in the session</title>
      <link>https://condukt.tuist.dev/blog/agent-session-secrets/</link>
      <guid isPermaLink="true">https://condukt.tuist.dev/blog/agent-session-secrets/</guid>
      <pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate>
      <author>The Tuist team</author>
      <description>Agents need to act against real systems. We added session secrets to Condukt so credentials become part of the execution boundary, not part of the conversation.</description>
    </item>
    
  </channel>
</rss>
