Background session commands wait for a sign-in refresh before…

Background session commands wait for a sign-in refresh before exiting

The logs, attach, respawn, rm and stop commands, and --bg, now wait for any sign-in refresh to finish before exiting

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

SessionsArea: what it touches

Bug FixesKind: in v2.1.312, 27 Oct 26

Bug FixesSection of the release

What

The commands that manage background sessions (logs, attach, respawn, rm and stop) and starting a session with --bg now wait for any sign-in token refresh in progress to finish before they exit. Before, they exited as soon as Claude Code had finished sending its usage data.

Why

A freshly refreshed sign-in is less likely to be lost when one of these commands exits.

See this entry in the whole of v2.1.312 →

The build it came inv2.1.312

27 Oct 2026 · 265 entries, this one is #138.

Use it now10
You'll notice136
Nothing to try yet9
Under the hood110

Either side of it

v2.1.311Older

Open the release →

Names in this entry

cli--bg
Start the session as a background agent and return immediately. Prints the session ID and management commands. Combine with --exec to run a shell command as a background job instead of a Claude session, or with --agent to run a specific subagent. Checks workspace trust for the directory before it starts. Can't be combined with -p/--print; see the error reference

Is this right?