Background job session auto-marked 'completed' without user request, 3x same day
Description
A background Claude Code job session (in the "claude agents" / FleetView-style job list UI) repeatedly gets auto-marked as completed without the user ever asking for that, making the session hard to find/resume afterward.
Environment
- Claude Code v2.1.215
- Model: Sonnet 5
- Platform: macOS (Darwin 25.5.0)
Steps to reproduce / observed pattern
- Start a background job session and have a multi-turn conversation.
- Send a reply that is short and reads as fully resolved (even without a literal completion marker like "result:").
- The session's status in the job list flips from "Working" to "Completed" on its own.
This happened 3 times in one session on 2026-07-22:
- 1st: after a short closing-shaped reply ("Rule saved...").
- 2nd: after another short wrap-style reply, with no literal "result:" line present.
- 3rd: after a reply that explicitly stated "session still open, not closing anything" — screenshotted directly from the job list by the user, showing the session moved to Completed seconds after that reply.
Expected behavior
A session should only move to "completed" status when the user explicitly asks to close it out (or an equivalent explicit signal), never inferred purely from the shape/tone of an assistant reply — especially not when the reply explicitly says the session is still open.
Actual behavior
Some classifier/mechanism appears to infer session completion from the general "resolved-sounding" shape of a reply, independent of the literal presence of a documented completion signal (e.g. a result: line), and can override explicit statements to the contrary in the same message.
Impact
Once a session is marked completed, it becomes difficult to relocate/resume it in the job list, effectively losing access to an otherwise still-active working session.