Under the hood
Useful2 Signal2
Background dispatch failures now distinguish a daemon that started but couldn't launch Claude Code.
What's wrong with this entry?
Anonymous. No account, no email.
What
The tengu_bg_dispatch_fallback telemetry now classifies failures where the daemon started but Claude Code did not under a daemon-stderr reason, with a parsed exit code or signal appended when one is present, before falling back to the previous path-bearing and truncated-message forms.
Evidence
tengu_bg_dispatch_fallback
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task