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

Usage logging checks DNS for the logs host before sending

Claude Code now looks up its logs host in DNS before sending usage logs, and pauses and warns when the host cannot be found

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

What

Claude Code sends usage logs to a logs server. It now looks up that server's address first, in DNS, the system that turns a host name into an address (logs_host_lookup).

  • If DNS gives no address for the logs host (ENOTFOUND), sending pauses and the logs are dropped.
  • You get a warning, and it says whether the refusal was confirmed or not.
  • Before, there was only one record of a refused send and a fixed pause.

The same finding also notes two small changes. rollback was dropped from a list of token-check reasons, next to stale and future_iat. One call now passes keys: process.stdin.isTTY === !0, which is true when the input is an interactive terminal.

Why

On a machine with no internet or in a locked-down setup, Claude Code makes fewer failed attempts to send logs and tells you plainly that it cannot reach the logs host.

See this entry in the whole of v2.1.312 →

Feedback