<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Automation on AIBussin — AI applications, systems and books</title>
		<link>https://aibussin.com/categories/automation/</link>
		<description>Recent content in Automation on AIBussin — AI applications, systems and books</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Fri, 02 Oct 2026 09:00:00 +0100</lastBuildDate>
		
			<atom:link href="https://aibussin.com/categories/automation/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Headless Pi</title>
				<link>https://aibussin.com/books/pi/32-chapter/</link>
				<pubDate>Fri, 02 Oct 2026 09:00:00 +0100</pubDate>
				<guid>https://aibussin.com/books/pi/32-chapter/</guid>
				<description>&lt;p&gt;A CI job needs to run a review over a diff. A pre-commit hook needs to summarise what just changed. Neither has a person, and neither wants a terminal.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;pi&lt;/code&gt; already handles this, and the handling is almost entirely documented in one place: &lt;code&gt;cli-integration.md&lt;/code&gt;. But the interesting question is not &amp;ldquo;how do I print the answer&amp;rdquo; — it is &lt;strong&gt;what is different when the agent has no person attached&lt;/strong&gt;, because most of what you built in the previous twenty-nine chapters assumed one.&lt;/p&gt;</description>
			</item>
			<item>
				<title>RPC</title>
				<link>https://aibussin.com/books/pi/35-chapter/</link>
				<pubDate>Fri, 02 Oct 2026 09:00:00 +0100</pubDate>
				<guid>https://aibussin.com/books/pi/35-chapter/</guid>
				<description>&lt;p&gt;You want to drive Pi from an editor plugin, from a Python service, or from an IDE — without reimplementing the TypeScript SDK in another language or running Pi inside your host process. A subprocess gives the host a separate failure and lifecycle boundary. It does not sandbox the agent: Pi and its tools can still reach whatever files, credentials, and services the child process is permitted to access.&lt;/p&gt;&#xA;&lt;p&gt;RPC is the fourth interface in this progression and the one that keeps the isolation. This chapter is about the protocol: what flows in each direction, how you correlate, and the subprotocol that almost nobody realises exists.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
