Subagent steering can be resolved per model / Claude Code v2.1.219

Not switched on

Useful2 Signal3

Subagents Notable not in their notes

Subagent nudging behaviour can be picked per model, but the whole feature stays behind a gate.

A model-keyed steer lookup is wired in behind tengu_thistle_grebe, with CLAUDE_CODE_THISTLE_GREBE overriding everything.

Feature flag

tengu_thistle_grebe Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.219: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.219. It isn't a statement about your account. What a flag value here can and cannot tell you

CLAUDE_CODE_THISTLE_GREBE

What

Steer mode can now be chosen based on the model in use rather than only env, client data and growthbook.

Details

Resolver values are default, no_nudges and counter_steer
A fourth source runs after env, client data and growthbook: if a model was registered for this resolution it consults a model-keyed lookup and reports source: "model" in tengu_subagent_steer_applied
Env var CLAUDE_CODE_THISTLE_GREBE still wins over everything
Gated on tengu_thistle_grebe / CLAUDE_CODE_THISTLE_GREBE

Evidence

counter_steer

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

v2.1.227 Prompt section discouraging over-delegation to subagents
Both mention thistle grebe subagent

Subagent steering can be resolved per model

Related