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.187 ·

Entry
JSON All of v2.1.187
EntryKind: in v2.1.187,
Bug FixesSection of the release
  • UTF-8 multi-byte characters in keyboard input: The key parser now correctly reassembles multi-byte UTF-8 sequences delivered as individual escape sequences. Previously, non-ASCII characters entered via the terminal (particularly on some Linux/remote terminals) could be dropped or misinterpreted. A pendingByteEvents buffer accumulates bytes and flushes the complete character once all bytes have arrived. (search for "pendingByteEvents")
  • AbortSignal memory leak in event listeners: Abort-signal subscriptions created during agent turns now use a FinalizationRegistry to automatically remove the listener when the child object is garbage-collected. Previously, long-running sessions with many tool calls could accumulate a growing number of stale abort listeners. (search for "FinalizationRegistry")
  • FileIndex: skip path normalization when unchanged: Path normalization is now skipped when the raw git paths have not changed, avoiding unnecessary work and a potential re-index cycle. (search for "[FileIndex] skipped path normalization")
  • FileIndex: discard mid-refresh results when cache was reset: If the file index cache is reset while a refresh is in progress, the results of that refresh are now discarded rather than written over the fresh cache. (search for "[FileIndex] discarding refresh results")
  • Windows: UNC watch paths dropped gracefully: When the file watcher encounters remote UNC paths on Windows, they are now silently dropped with a debug log rather than crashing the watcher. (search for "FileChanged: dropped remote UNC watch path(s)")
  • MCP schema validation error surfaced as named error: MCP tool results that fail schema validation now throw a McpResponseSchemaError with the validation message attached, rather than an untyped error. (search for "McpResponseSchemaError" or "MCP server returned a malformed result")

See this entry in the whole of v2.1.187 →

Feedback