Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.321 ·

Auto-mode rules get their own cloud-session notice, and stalled TLS handshakes time out

Cloud sessions report auto-mode rules as their own reason, and a stalled secure connection now stops with ERR_TLS_HANDSHAKE_STALLED

Group of 3 You'll notice Improvements
JSON All of v2.1.321
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Auto ModeArea: what it touches
ImprovementsKind: in v2.1.321,
ImprovementsSection of the release

What

  • Auto-mode rules: when a setting that restricts a cloud session is only auto-mode rules, the compatibility message gives a separate auto_mode_rules reason with its own text. Before, every restricting setting was reported as a tool restriction.
  • Stalled connections: a TLS handshake is the first exchange that sets up a secure connection to a server. If it does not finish in time, HTTPS requests now stop with ERR_TLS_HANDSHAKE_STALLED and the message "The TLS handshake with the server did not finish in the time allowed, normally 120 seconds. Check the network or proxy." This error is treated as its own kind of network failure.

Why

Cloud sessions with auto-mode rules get a more accurate explanation, and a stuck connection gives a clear error pointing to the network or proxy instead of hanging.

See this entry in the whole of v2.1.321 →

Feedback