Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

The "job" versus "task" wording test for MCP background work is gone

You'll notice
Useful1 Signal1
MCP

The status line always calls MCP background work a "task" instead of sometimes saying "job".

Feature flag
tengu_copper_thistle Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.247: on

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

What

The status line no longer chooses between calling MCP background work a job or a task. It always says 1 MCP task or N MCP tasks.

Details
  • The flag that drove the choice, tengu_copper_thistle, still exists and still gates footer layout elsewhere; it just no longer decides this label. Its in-build fallback is false.
Evidence

return e === 1 ? "1 MCP task" : ${e} MCP tasks;

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

See this entry in the whole of v2.1.247 →