3 people reported
All time, since Sep 23, including 1 thumbs-up on GitHub.
Unprompted session backgrounding
“It should not be backgrounded with no input, and the dispatch should not be labelled as a slash command the user never typed.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/3036/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Idle interactive session moves to background with no user input. Transcript shows "Backgrounding after the current tool finishes…" and a daemon "bg spawned" entry with source "slash" though history.jsonl has no input; /exit then detaches.
Is this your bug?
File my report- Where
- Interactive sessions
- Error text
Backgrounding after the current tool finishes…- Versions
- 2.1.280 to 2.1.296
- Platforms
- Linux, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Background respawn exits before init2 people
- Background /loop crons stop firing2 people
- Finished Bash stuck as Running3 people