[BUG] /compact command ignores stop requests, forces session termination and loss of history

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 /compact feature does not respond to stop requests from users. When a user attempts to stop the compacting operation, it continues running, forcing the user to terminate the entire session - resulting in complete loss of conversation history and context.

Critical UX Failure:

• Violates fundamental principle of user agency/control
• Results in permanent loss of user trust in the feature
• Creates fear of using the feature due to potential history loss
• No recovery path - entire session context is destroyed

As a UI/UX professional, this is a textbook example of how a single control failure permanently damages feature adoption. Users won't return to a feature that has cost them work and ignored their explicit commands.

What Should Happen?

• /compact should immediately stop when user requests it to stop
• User should maintain control over long-running operations
• Session history should not be at risk when stopping a feature

Error Messages/Logs

Steps to Reproduce

1. Run /compact command
2. Attempt to stop the operation (user request to stop)
3. Observe that the command ignores the stop request and continues
4. Only option is to terminate the entire session

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

latest

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_