Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.247 ·

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

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

You'll notice Removed
JSON All of v2.1.247
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
RemovedKind: in v2.1.247,
RemovedSection of the release
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.

Read from
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: off

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 has happened since
Flag reading moved The flag server now returns off for tengu_copper_thistle, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_copper_thistle, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.247 →

Feedback