Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Cloud background sessions can hold a lease on the local daemon

Claude Code can now hold a lease connection to its background daemon, reconnect it, and start the daemon a limited number of times

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

Unclear It is not clear what in Claude Code starts this lease routine, so when it actually runs is unknown.

What

Claude Code has a new routine that keeps a "lease" open with its daemon. A daemon is a helper program that runs in the background, separate from the window you type in. The connection runs over a local socket, which is a private channel between programs on the same machine.

The routine:

  • Reconnects when the connection drops.
  • Starts the daemon itself, but only up to a fixed number of times.
  • Refuses to take a lease from a daemon owned by a different user account on the same machine.
  • Stops when it has used up its starts, when the daemon belongs to someone else, or when the daemon is shutting down.
Why

The lease is for cloud background sessions, which are sessions that keep running while you are not watching them, and it is meant to keep the daemon alive for them. Because it ignores daemons run by other users, a shared machine does not let one person's session lean on another person's background process.

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 in Claude Code starts this lease routine, so when it actually runs is unknown.

See this entry in the whole of v2.1.290 →

Feedback