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.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Screen reader announcements are queued and held back at startup

Use it now
Useful2 Signal2
Elsewhere

Screen reader announcements are queued and held quiet during startup, under the axScreenReader setting.

axScreenReader
What

Spoken announcements now go through a queue with a bounded buffer instead of firing immediately, and a quiet window suppresses them during startup until an explicit end point. This runs under the existing axScreenReader setting.

Details
  • The controller records when the first announcement was written and when the startup quiet window opened, and clears both on reset.
  • Whether accessibility output is enabled is now passed in as a function rather than read from a module-level global.
Evidence

startupQuietOpenedAtMs

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

Related

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

See this entry in the whole of v2.1.238 →