I'm a developer and AI enthusiast. I share my journey and thoughts about AI and technology here.
I prefer agent memory on demand, not by default. The real difficulty is deciding what to keep, when to keep it, and how to stop memory from turning into noise.
Claude Code is great for interactive exploration. Once you need long-running, recoverable, auditable agent execution, code-level control becomes much harder to avoid.
Yes. It is git worktree used as isolation for agent workflows: one repository, multiple directories, and far fewer workspace collisions.
Prompt caching is driven by prefix matching, not by session identity. If the same prefix shows up again, reuse can happen across conversations and sometimes across users.
TTL is the lifetime of a prompt cache entry. Each hit refreshes it. Leave it unused for long enough, and it expires.
Prompt caching cuts the price of repeated prefixes. Tool-result replacement shrinks the prompt itself. Both can save money, but they push on different parts of the bill.
Usually yes. A worktree works best as a disposable task folder: create it for the job, merge the branch, then remove the directory and keep the commits.
Deep dive into Cursor Rules classification and prompt structure to make AI your top developer assistant
