Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Remote session time limits can now come from a per-tenant value

A remote session's time limit can now come from a value set for its tenant, not only from the CLAUDE_CODE_REMOTE flag setting

Under the hood Internal Changes
JSON All of v2.1.288
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.288,
Internal ChangesSection of the release
What

Remote sessions run Claude Code on a machine other than yours and have a maximum lifetime. Claude Code now first checks where that limit comes from:

  • If it comes from somewhere other than the flag, Claude Code uses a value set for the tenant, meaning the account or workspace the session runs under.
  • Otherwise it falls back to the earlier flag-based value, which applies when CLAUDE_CODE_REMOTE is set.

Previously the limit came only from the flag. When the tenant value is in use and the last full check happened very close to the limit, Claude Code now treats the remaining time as zero instead of leaving it unset.

Why

Remote session time limits can now differ per tenant instead of being fixed by one flag.

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 doubtIt is not clear what decides whether the limit comes from the tenant or the flag.

See this entry in the whole of v2.1.288 →

Feedback