Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.259 ·

Cloud/bughunter poll timeout driven by remote config client_wait_minutes

The remote wait-minutes value is now clamped between 30 and 55, defaulting to 45 when unset or invalid.

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaCode Reviewwhat it touches
KindInternal Changesin v2.1.259,
Group of 3 Under the hood No documentation found

The remote wait-minutes value is now clamped between 30 and 55, defaulting to 45 when unset or invalid.

The remote-config value client_wait_minutes is now read and clamped to a finite number between 30 and 55, falling back to 45 if it is unset, non-numeric, or out of range. This replaces the previously hardcoded 30-minute (1800000ms) timeout used by the remote/cloud-review task poller before it declares poll_timeout; the value is computed once (memoized) and reused everywhere the timeout is checked or reported, including the timeout error message. The same value is used to compute BUGHUNTER_RESULT_RELAY_MAX_SEC for the bughunter feature's result-relay wait time.

Read from
Names in the bundleclient_wait_minutes

See this entry in the whole of v2.1.259 →

Feedback