Two Claude Code sessions in the same folder will sooner or later edit the same file and undo each other's work. A worktree fixes that by giving each session its own copy of the files on its own branch. Here is where Claude Code stores worktrees, how they work, what they share with your main folder, and the small routine that makes them worth using.
Claude Code gives every session a scratch folder under /private/tmp, and it is easy to think that this folder is where all of its leftovers live. It is the smallest part: more temporary files sit next to it, and the long-term record of every session stays in ~/.claude for a month by default.
When many Claude agents work together, a single agent that is tricked by hidden instructions can pass those instructions on to all the others. This post explains what a sandbox protects in a group of agents, which kinds of isolation exist from a simple command filter to a separate virtual machine, how to configure them in Claude Code, and which setups work well in practice.
I opened Claude Code on a side project after a day away, and it greeted me with a careful reconstruction of what we had been doing, pieced together from the notes file and the working tree. It was right, but it was a guess. The whole conversation that produced that work was sitting on disk, one command away. Here is how sessions actually persist, what a resumed one gives you back, and what it never will.
When a coding agent writes most of the code, reading every diff stops being realistic, and "reading diagonally" — skimming — becomes the default. It is a real bet, not a safe one: architecture doesn't break in any single diff, it erodes across all of them, and skimming checks exactly the part that was never the problem.
Claude Code writes two records to your disk: an append-only ledger of every exchange with the model, and a small cached snapshot of how full your rate limits are. Almost every tool and blog post about local usage tracking knows about the first one and misses the second — including, until I actually looked, me.
Every "always allow" click quietly trades a little control for a little convenience — and after a few months of daily agent use, those clicks add up to a security posture nobody designed. Here's how to audit what your coding agent can already do without asking, which grants deserve scrutiny, and how to put deliberate guardrails back.
Claude Code skills have no requires: field, no imports, no dependency resolver — and yet you can build a real graph of skills that depend on each other. This post lays out the mental model, the three composition mechanisms that fall out of it, and a refactor of this blog's own skill folder as a case study in what happens when you skip them.
Your ~/.claude folder quietly accumulates two very different things: configuration you'd hate to lose, and private data you must never publish. Here's how to put the first under git without ever committing the second.
Every post on this blog needs two images that do completely different jobs: a social card that has to earn a click in a feed, and an inline hero that opens the article. This post is about how the blog makes both — a typographic default that costs nothing, an opt-in artificial-intelligence (AI) cover that costs about four cents, and the little Model Context Protocol (MCP) server that wires an image model straight into Claude Code. The cover above was made by that exact pipeline.