cli_bg_dispatch telemetry gains cwd

cli_bg_dispatch telemetry gains cwd_gone reason

Background dispatch telemetry records a missing working directory as its own reason.

Under the hood No documentation found Internal Changes

JSON All of v2.1.257

Under the hoodTier: how much it should matter to you

1Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

SessionsArea: what it touches

Internal ChangesKind: in v2.1.257, 01 Sep 26

Internal ChangesSection of the release

The claude --bg dispatch failure telemetry (cli_bg_dispatch) now records a distinct cwd_gone reason, tracked through the same success/failure counter as gate_blocked, instead of grouping it with generic spawn failures.

Read from

Names in the bundlecwd_gone

How sure we are

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

Anthropic's release notes agreeFixed claude --bg from a directory that was just deleted reporting "backgrounded" and leaving a crashed session row; it now prints the…

See this entry in the whole of v2.1.257 →

The build it came inv2.1.257

1 Sep 2026 · 505 entries, this one is #390.

Use it now45
You'll notice231
Nothing to try yet71
Under the hood158

Either side of it

v2.1.252Older
v2.1.258Newer

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

Anthropic's note

Upstream's own release notes for v2.1.257 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.

Fixed claude --bg from a directory that was just deleted reporting "backgrounded" and leaving a crashed session row; it now prints the reason and exits 1

Is this right?