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 ·

Owner messages from MCP results can count as you speaking, currently dark

Project owner messages fetched by a tool could be replayed as if you said them, currently dark.

Nothing to try yet Notable In Development
JSON All of v2.1.242
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
ProjectsArea: what it touches
In DevelopmentKind: in v2.1.242,
What probably matters to youSection of the release

Verified owner rows replay as user turns only when tengu_hearth_resolved_rows is exactly "full"; it defaults to "off".

What

In Claude Code Projects, a tool result from the project fetch tools can now carry verified rows of messages from the project owner, and those get replayed into the conversation as turns that count as the user speaking. The remote setting tengu_hearth_resolved_rows defaults to "off" and this path requires the value to be exactly "full", so absent server config nothing here runs.

Details
  • Rows arrive under a new result metadata key, anthropic/hearth.rows, alongside the existing attachment-based path. The key does not appear in v2.1.241.
  • Replayed turns are flagged as harness-generated.
  • New telemetry event auto_mode_projects_owner_rows reports one of ok, invalid_rows, truncated or no_owner_rows; skipping the feature reports flag_not_full, deduplicated once per session.
  • The scan loop is wrapped so it iterates nothing unless the caller passes an enable flag, which the caller computes as a thread check plus the setting above. The setting also accepts "model_only", but only "full" turns this on.
Evidence

anthropic/hearth.rows

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

Read from
Feature flag
tengu_hearth_resolved_rows 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.242: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.242. 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 "full" for tengu_hearth_resolved_rows, 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_hearth_resolved_rows, 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