<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>developer-tools - Tag - Miłosz Kukuła dev blog</title><link>https://kukulam.dev/tags/developer-tools/</link><description>developer-tools - Tag - Miłosz Kukuła dev blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>contact@kukulam.dev (kukulam)</managingEditor><webMaster>contact@kukulam.dev (kukulam)</webMaster><lastBuildDate>Wed, 11 Nov 2026 11:00:00 +0100</lastBuildDate><atom:link href="https://kukulam.dev/tags/developer-tools/" rel="self" type="application/rss+xml"/><item><title>Claude Code configuration hierarchy</title><link>https://kukulam.dev/posts/claude-code-configuration-hierarchy/</link><pubDate>Wed, 11 Nov 2026 11:00:00 +0100</pubDate><author>kukulam</author><guid>https://kukulam.dev/posts/claude-code-configuration-hierarchy/</guid><description><![CDATA[<div class="featured-image">
                <img src="/logo" referrerpolicy="no-referrer">
            </div>Introduction In this post, we&rsquo;ll explore where Claude Code keeps its configuration and which file wins when the same thing is defined in more than one place. By the end of this post, you&rsquo;ll know where to put a setting so that it applies only to you, to your team, or to the whole organization.
Configuration hierarchy Claude Code reads its configuration from four scopes. The table below is based on a slide from Boris Cherny&rsquo;s talk Practical Tips on How to use Claude Code, updated to the current file names.]]></description></item></channel></rss>