<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Tooling on AIBussin — AI applications, systems and books</title>
		<link>https://aibussin.com/categories/tooling/</link>
		<description>Recent content in Tooling 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/tooling/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Built-In Tools</title>
				<link>https://aibussin.com/books/pi/06-chapter/</link>
				<pubDate>Fri, 02 Oct 2026 09:00:00 +0100</pubDate>
				<guid>https://aibussin.com/books/pi/06-chapter/</guid>
				<description>&lt;p&gt;In an interactive session, Pi displays tool activity as it works. Visibility is not restriction: Pi does not require approval before every tool call, and built-in tools ordinarily run with the operating-system permissions of the Pi process. Headless modes expose activity differently, and showing a call does not prevent its effects.&lt;/p&gt;&#xA;&lt;p&gt;One control is the &lt;em&gt;set&lt;/em&gt; of tools made available to the model. &lt;code&gt;settings.md&lt;/code&gt; gives &lt;code&gt;defaultTools&lt;/code&gt; a default of &lt;code&gt;read&lt;/code&gt;, &lt;code&gt;bash&lt;/code&gt;, &lt;code&gt;edit&lt;/code&gt;, and &lt;code&gt;write&lt;/code&gt;. Settings, command-line options and loaded integrations can change the effective set; none of these settings is an operating-system sandbox.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
