DEV Community: AIFix

claude subagents: When to Use One Agent vs Many (A Practical Setup Guide)

AIFix — Sat, 24 Oct 2026 19:27:42 +0000

If you build with Claude, you have probably wondered whether to split work across claude subagents or keep everything in one agent. Anthropic recently published guidance on exactly this question, and the short answer is: start with one main agent plus skills, and add subagents only when you have a clear reason. Here is what the sources say and how to apply it.

What Anthropic's guide says

In Building agents: When to fold subagents into your main agent loop, Anthropic's Applied AI team writes that across several enterprise deployments, "a single agent with skills frequently outperformed both the one-prompt-for-everything design and the subagent design on quality, and often at a lower cost and latency per task."

A few points from the same article:

One customer that compared its multi-agent setup against a single agent loop saw roughly 2x faster runtime with the single loop.
Skills and tool search use progressive disclosure: the agent sees short descriptions and loads the full content only when needed, which removes a main reason teams split work into subagents.
Group tools by user intent, because past roughly 30-50 tool definitions, tool choice tends to degrade.
A common mistake is giving every team its own subagent, so the architecture copies the org chart.

The guide is clear that subagents still have a place. Use them when:

A single agent hits measurable performance loss from context bloat.
Several tasks can run in parallel with fresh context windows you can throw away afterwards.
One agent struggles to pick the right tools, or the system prompt has conflicting instructions.

What the Claude Code docs add

The official Claude Code subagents docs say each subagent runs in its own context window with its own system prompt, tool access and permissions, and returns a summary to the main conversation. They also note that subagents send their own requests, which count toward the same usage limits.

The docs recommend staying in the main conversation when the task needs back-and-forth, when phases like planning, building and testing share a lot of context, for quick changes, and when latency matters. Subagents fit when the task produces verbose output you don't need in your main context, when you want to restrict tools, or when the work is self-contained and can return a summary.

A small example setup

Per the docs, subagents are Markdown files with YAML frontmatter. Put project ones in .claude/agents/ (or ~/.claude/agents/ for all your projects). Only name and description are required. Here is a read-only research helper, the kind of self-contained job the guidance supports:

---
name: log-researcher
description: "Reads long log files and test output, then reports only the errors and likely causes. Use when output is large."
tools: Read, Grep, Glob
model: haiku
---

You are a log analyst. Find errors, group them by cause,
and return a short summary with file paths and line numbers.
Do not edit any files.

Everything else, such as your normal coding, writing or customer workflow steps, can stay in the main agent, with repeatable procedures moved into skills.

A simple decision checklist

Steps depend on each other or share context? One main agent.
Lots of noisy output (logs, test runs, document reading)? A subagent that returns a summary.
Independent research paths? Parallel subagents.
Need a strictly read-only helper? A subagent with limited tools.
Same instructions reused everywhere? A skill, not a new subagent.

Anthropic's own advice is to measure: build a small eval (even 10 good examples), fold in one subagent at a time, and keep it as a subagent only if the folded version scores worse.

More research-based AI news and guides at ainews.useaifix.com, and automation help at useaifix.com.

node2shell: How to Check If Your Node.js App Is Exposed and Patch It

AIFix — Sat, 24 Oct 2026 04:27:10 +0000

node2shell is the nickname for CVE-2026-111497, a flaw in the Brotli decoder bundled with Node.js. The Node.js project fixed it on 21 October 2026, and the fix is a runtime upgrade. Here's how to check and patch, based on the advisories listed at the end.

What node2shell is

The Node.js security release describes an out-of-bounds write in the bundled Brotli decoder. If an attacker can supply Brotli data that your app decompresses with node:zlib, they can corrupt process memory. Node.js says this can lead to a crash, memory disclosure or remote code execution. It affects the 22.x, 24.x and 26.x lines, and Node.js credits OpenAI Codex Security with reporting it.

Severity ratings differ by source:

The Node.js advisory rates it high.
The CVE record gives it 9.2 (critical) on CVSS 4.0 and places the root bug in Google's Brotli library, versions 1.0.3 through 1.2.0.
Singapore's Cyber Security Agency calls it critical, citing a CVSS 3.1 score of 9.8.

Imperva's Red Team says it got code execution against the official Node.js 24.22.0 image, through both the built-in fetch() and Express 5 / body-parser 2 request parsers. It says 24.22.1 rejected the same input.

Where http2shell fits in

http2shell is not a second bug. Aikido Security uses the name for the same CVE now that it is known to reach beyond Node.js. It lists fixes for Python's Brotli and brotlicffi packages, libbrotli, curl/libcurl, Bun, Envoy and Istio. On 23 October, Aikido said patches were not yet available for every affected service.

Am I exposed?

Vercel's advisory explains that Node.js doesn't decode Brotli by itself. Your app is exposed when your code or a library decompresses attacker-controlled Brotli data. That data can come in a request body or in a response your app fetches.

1. Check the runtime version.

node -v

The fixed versions are 22.23.4, 24.22.1 and 26.12.1 (or newer in the same line). Anything older in those lines is affected. Node.js 20 is end-of-life and won't get a fix, according to Vercel.

2. Look for paths that decode Brotli. Imperva's tests found Express 5 and body-parser 2 decode Brotli request bodies when their parsers are configured:

npm ls express body-parser

Also look for fetch() calls to servers you don't control and direct zlib Brotli use (brotliDecompress).

3. Check containers and CI, not just your laptop. Imperva warns that a package inventory can miss an older Node binary inside a container image:

docker run --rm your-image:tag node -v

How to patch

With nvm:

nvm install 24
nvm use 24
node -v   # should print v24.22.1 or newer

For Docker, rebuild on a base image with a fixed Node version and redeploy. For distro packages, Aikido notes vendors may backport the fix without changing the version number, so check your distribution's security notice.

On a managed platform, check the provider's notice. Vercel says it manages patch versions for 22.x and 24.x, but projects on 20.x must move to 22.x or 24.x and redeploy.

Python and Bun users get their own fixes, per Aikido:

pip show Brotli brotlicffi
pip install -U "Brotli>=1.2.1"      # or "brotlicffi>=1.2.1.0"
bun --version                        # 1.4.4 or later is fixed

Aikido notes that requests, httpx and aiohttp use these packages automatically when installed, and that pip-audit and Dependabot weren't flagging it as of 23 October, so check by hand.

If you can't upgrade today

Vercel and Imperva both added WAF rules, but both say that doesn't replace patching. A WAF also can't see Brotli responses your app fetches from other servers. As a stopgap, Aikido suggests rejecting requests whose Content-Encoding includes br before any decoder runs. For outbound traffic, it suggests disabling or rejecting Brotli response decoding.

Sources

For more research-based AI and tech news, see AI News by AIFix at ainews.useaifix.com, and useaifix.com for help keeping sites and workflows in shape.