<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coding-Agent on Bil Arikan</title><link>https://bil.arikan.ca/tags/coding-agent/</link><description>Recent content in Coding-Agent on Bil Arikan</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 29 May 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://bil.arikan.ca/tags/coding-agent/index.xml" rel="self" type="application/rss+xml"/><item><title>Local AI Lab --- Bridging OpenClaw and Pi Across Containers</title><link>https://bil.arikan.ca/posts/local-ai-lab-bridging-openclaw-and-pi/</link><pubDate>Fri, 29 May 2026 00:00:00 -0500</pubDate><guid>https://bil.arikan.ca/posts/local-ai-lab-bridging-openclaw-and-pi/</guid><description>&lt;p&gt;Container 110 (Pi Coding Agent) and container 111 (OpenClaw) are both running. The question now is how OpenClaw routes a coding task to Pi and gets the result back.&lt;/p&gt;
&lt;p&gt;Pi&amp;rsquo;s integration interface is RPC over &lt;a href="https://en.wikipedia.org/wiki/Standard_streams" target="_blank" rel="noreferrer"&gt;stdin/stdout&lt;/a&gt; &amp;mdash; it&amp;rsquo;s designed to be driven as a subprocess, not called over a network. OpenClaw lives in a separate container. Separate containers don&amp;rsquo;t share a process space, so &amp;ldquo;spawn Pi as a subprocess&amp;rdquo; doesn&amp;rsquo;t work out of the box.&lt;/p&gt;</description></item><item><title>Local AI Lab --- Setting Up Pi as a Local Coding Agent</title><link>https://bil.arikan.ca/posts/local-ai-lab-setting-up-pi-coding-agent/</link><pubDate>Thu, 28 May 2026 00:00:00 -0500</pubDate><guid>https://bil.arikan.ca/posts/local-ai-lab-setting-up-pi-coding-agent/</guid><description>&lt;p&gt;The last two posts got the inference layer and the gateway running. CT 100 is serving Qwopus at 44 T/s with MTP speculative decoding active. CT 101 is serving Gemma 4 E4B at 51 T/s. CT 111 (OpenClaw) is routing Telegram messages to the AMD container and responding.&lt;/p&gt;</description></item></channel></rss>