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

Claude Code v2.1.242 ·

Workflow tasks can relay the triggering request in a labelled frame

Workflow runs now label whether a person or a schedule triggered them, and quote the request.

You'll notice No documentation found In Development
JSON All of v2.1.242
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
WorkflowsArea: what it touches
In DevelopmentKind: in v2.1.242,
In DevelopmentSection of the release
What

A workflow run now classifies what set it off. A scheduled or external trigger gets an "automated trigger" banner telling the model it cannot claim user approval, while a run a person decided relays that person's request verbatim and indented, with optional preceding assistant context, and control characters and backticks stripped.

Details
Evidence

[Workflow harness \u2014 automated trigger]

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

Read from
What has happened since
Flag reading moved The flag server now returns on for tengu_bubbly_harbor, 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 off for tengu_bubbly_harbor, 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.242 →

Feedback