Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Freshness check tolerates a clock that jumps backwards

A recency check no longer fails outright when the system clock jumps backwards

Under the hood Bug Fixes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
SessionsArea: what it touches
Bug FixesKind: in v2.1.281,
Bug FixesSection of the release
What

Claude Code has an internal check that decides whether something happened recently. If the computer's clock jumps backwards, the time elapsed can come out negative. Before, the check then answered "not recent." Now it only checks that the recorded time is not later than the current time. The check can also be given a different clock to use, which makes it easier to test.

Why

A clock correction, such as a time sync or a change of time zone setting, should no longer make something that just happened count as stale.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say which feature relies on this recency check.

See this entry in the whole of v2.1.281 →

Feedback