Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Cloud workers report new process startup and memory diagnostics

Anthropic-hosted cloud workers can report startup timing, process tuning and, by opt-in, garbage-collection counts on session results

Group of 3 Use it now Internal Changes
JSON All of v2.1.311
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.311,
What probably matters to youSection of the release

What

When Claude Code runs on Anthropic's cloud machines, it can now report more about how its process starts and uses memory.

  • Result messages, the summary sent at the end of a run, can carry process_start_tuning, process_start_purge_delay_ms and process_garbage_collections.
  • Garbage-collection counts, how often memory is cleaned up, are reported only when CLAUDE_CODE_COUNT_GARBAGE_COLLECTIONS=1 was set at process start. They come only from Anthropic-hosted cloud workers with telemetry on, and never from a process hosting other sessions.
  • The tuning value records which Bun and mimalloc variables were set, never their values.
  • For CLAUDE_CODE_REMOTE sessions, CPU, elapsed time, page faults and storage reads are sampled between startup milestones (spare loaded, claim, input ready, first message, first turn) and sent as process_stretches. Per-phase startup timings are also reported.

Why

These are diagnostics for Anthropic's cloud workers. They do not change how Claude Code behaves on your own computer, and the garbage-collection count stays off unless that variable is set.

See this entry in the whole of v2.1.311 →

Feedback