Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

A bad server value can no longer break the ultraplan time limit

If the ultraplan time limit sent from the server is not a valid positive number, Claude Code now uses 5400 seconds instead

You'll notice Bug Fixes
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Bug FixesKind: in v2.1.323,
Bug FixesSection of the release
What

Claude Code waits a set time for an ultraplan result before giving up, and that time can be set remotely. It now checks the value it receives. If the value is not a valid positive number, Claude Code uses 5400 seconds (90 minutes) instead. Before, a bad value could produce a zero or broken time limit.

Why

An invalid remote value no longer stops ultraplan from waiting the expected time.

Read from
Feature flag
tengu_ultraplan_timeout_seconds Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.323: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.323. It isn't a statement about your account. What a flag value here can and cannot tell you

See this entry in the whole of v2.1.323 →

Feedback