Clear message when a background session lacks the credentials to…

Clear message when a background session lacks the credentials to send

A background session missing its API key, token or workload identity now says nothing was sent and how to fix it

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

1Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

SessionsArea: what it touches

ImprovementsKind: in v2.1.323, 12 Nov 26

ImprovementsSection of the release

What

A background session is a Claude Code session that keeps running without a terminal open. If the background service does not have the session's API key, token or workload identity, Claude Code now says "Nothing was sent: the background service lacks this session's API key, token or workload identity." It offers two fixes:

Add the credential to your settings.
Run claude stop <id>, then claude --resume in a shell that has the credential.

Why

Instead of a vague failure, you get a clear path to getting the session working again.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeChanged claude rm and the agents view to say a session is removed from the list, not deleted; claude rm help says the conversation is kept…

See this entry in the whole of v2.1.323 →

The build it came inv2.1.323

12 Nov 2026 · 888 entries, this one is #534.

Use it now77
You'll notice533
Nothing to try yet64
Under the hood214

Either side of it

v2.1.322Older

Open the release →

Names in this entry

cli--resume
Resume a specific session by ID or name, or show an interactive picker to choose a session. In place of an ID, you can pass the absolute path to a session's .jsonl transcript file. The picker and name search include sessions that added this directory with /add-dir. When you pass a session ID, Claude Code searches the current project directory and its git worktrees, then every other project on this machine. Before v2.1.223, the ID search covered only the current project directory and its git worktrees. Background sessions appear in the picker marked with bg. Resuming one that is still running opens that session in this terminal through claude attach, and a prompt you pass on the command line goes to it as its next turn. Before v2.1.285, Claude Code refused and printed the claude attach command to run instead

Anthropic's note

Upstream's own release notes for v2.1.323 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Changed claude rm and the agents view to say a session is removed from the list, not deleted; claude rm help says the conversation is kept and claude --resume lists it

Is this right?