<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Configuration on AIBussin — AI applications, systems and books</title>
		<link>https://aibussin.com/categories/configuration/</link>
		<description>Recent content in Configuration 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/configuration/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Settings and Where Configuration Comes From</title>
				<link>https://aibussin.com/books/pi/07-chapter/</link>
				<pubDate>Fri, 02 Oct 2026 09:00:00 +0100</pubDate>
				<guid>https://aibussin.com/books/pi/07-chapter/</guid>
				<description>&lt;p&gt;You edit &lt;code&gt;settings.json&lt;/code&gt;, run &lt;code&gt;/reload&lt;/code&gt;, and the setting does not take effect. Or it takes effect in a way you did not predict. Both come from the same cause: you were reasoning about one file when Pi merges several.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;configuration.md&lt;/code&gt; gives the shape in one sentence. Pi supports user-level and project configuration. User-level lives in the agent directory, defaulting to &lt;code&gt;~/.pi/agent&lt;/code&gt;. Project configuration lives in &lt;code&gt;.pi&lt;/code&gt; under the working directory and loads after project trust is granted — with one exception, &lt;code&gt;sessionDir&lt;/code&gt;, which Pi reads before resolving trust so it can locate sessions.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
