<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Settings on Tokenise</title><link>https://tokenise.rosvetic.com/tags/settings/</link><description>Recent content in Settings on Tokenise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sun, 18 Oct 2026 16:03:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/tags/settings/index.xml" rel="self" type="application/rss+xml"/><item><title>Teach Claude Code's auto mode about your infrastructure, and don't drop the $defaults</title><link>https://tokenise.rosvetic.com/posts/claude-code-auto-mode-environment-defaults-trap/</link><pubDate>Sun, 18 Oct 2026 16:03:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/claude-code-auto-mode-environment-defaults-trap/</guid><description>&lt;p&gt;Since v2.1.283 auto mode is the built-in starting permission mode for interactive terminal and VS Code sessions, and by default it trusts exactly two things: the directory you launched in and that repo&amp;rsquo;s configured remotes. Everything else counts as external. So the first time Claude pushes a fix to a sibling repo in your company&amp;rsquo;s GitHub org, or writes a build artefact to your team&amp;rsquo;s bucket, the classifier blocks it, and it&amp;rsquo;s right to by its own lights. It has no idea those destinations are yours.&lt;/p&gt;</description></item></channel></rss>