[BUG] Background task result unknown after automatic compacting and 5-hour limit

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The session spawned a background task to run a test. But then the automatic context compacting happened and after the session hooks it ran directly into the 5-hour limit. I wonder what happened to the background task? From that interface, it's not visible to see what happened.

What Should Happen?

Some info about the background task should be there for me to check. Or wait with automatic compacting for user input or until the background task is done and then show results on the new startup text.

Error Messages/Logs

Steps to Reproduce

Close to full context or close to session 5-hour limit: Start a background task. Claude Code started a background task itself for running a longer running script. This was not user requested. I don't know if that can be triggered consistently or perfectly timed to reproduce. But it surely will happen for someone out there. Session limits and automatic compacting happens often.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.0.108 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_