{"version":"2.1.323","anchor":"ultraplan-timeout-now-read-through-a-validating-helper","canonical_anchor":"ultraplan-timeout-now-read-through-a-validating-helper","heading":"A bad server value can no longer break the ultraplan time limit","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/ultraplan-timeout-now-read-through-a-validating-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A bad server value can no longer break the ultraplan time limit\n\nIf the ultraplan time limit sent from the server is not a valid positive number, Claude Code now uses 5400 seconds instead\n\n**What**\n\nClaude 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.\n\n**Why**\n\nAn invalid remote value no longer stops ultraplan from waiting the expected time.\n\n- Flag `tengu_ultraplan_timeout_seconds`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}