DEV Community

Honey Kiran
Honey Kiran

Posted on Originally published at honeykiran.substack.com on

Your Subagents Have Three Silent Defaults. One of Them Isn't Read-Only.

When an agent spawns a subagent, three things happen by default — and a thread on r/ClaudeCode this week laid them out like a charge sheet:

1. The full reload. Every spawn re-reads the entire CLAUDE.md from the top. Spawn twenty subagents, pay for the same instructions twenty times — in tokens, in latency, in context crowded with rules most of them will never use.

2. Inherited effort. The subagent runs at the parent's effort setting whether the job needs it or not. A two-line lookup burns the same depth as the architecture review. Nobody set that. It's just the default, silently spending.

3. The "read-only" that isn't. A subagent configured as read-only can still have its Bash tool open. Read-only in the description; a shell in the hand. Anything the shell can do, the "read-only" agent can do.

Defaults are decisions you didn't make

None of these is a bug in the dramatic sense. Each is a default that made sense to somebody, once, applied to your work without asking. That's what makes them dangerous: they don't appear in your config review, your cost report shows them as weather, and the read-only one wears a name tag that says it's safe.

The audit takes an afternoon:

  • Print what a spawn actually inherits — instructions, effort, tools — for every agent type you run.

  • Scope the tools to the label. If it says read-only, the tool list should be embarrassed to include a shell.

  • Pay for instructions once. Shared context goes in a place spawns reference, not a document each one re-reads in full.

  • Set effort per job class, not per parent mood.

My agents work the 3AM shift so no human has to. Their subagents clock in with exactly the tools on their badge — nothing inherited, nothing silent.

What did your last subagent inherit that you never chose?


Disclaimer

  • This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.

  • I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.

  • Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.

  • Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.

  • Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.


© 2026 Honey Kiran. All rights reserved.

Honey Kiran · DevOps & Platform Engineering

AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.

Examples are illustrative — validate in your own environment before running in production.

Top comments (0)