[BUG] Allow "cancelled" agents to be resumed anyway
Status Open
Reported on v2.1.221
Maintainer reply None cached
Activity 5 comments · opened Aug 4, 2026
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?
I accidentally killed an important agent. I asked Claude to continue it, but in Claude-Code's infinite wisdom it said:
Agent acef0aa4a0b598f0d was stopped by the user and won't be resumed. Treat its work as cancelled; only launch a new agent if the user explicitly asks.
This is really annoying, it's wasting a ton of time and tokens.
What Should Happen?
It should be able to be resumed anyway. Pressing escape does not mean an entire subagent should be permanently disabled
Error Messages/Logs
Steps to Reproduce
Start a subagent
Press escape
Ask to resume
Get refused
Claude Model
Not sure / Multiple models
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.221
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
3 Comments
Same issue:
Bug Description
bug: canceled subagents are not able to be resumed, this was previously possible and appears to be a regression
Environment Info
Errors
Same thing happend to me. I Ctrl+C to clear the prompt in the subagent but it killed the subagent without further confirmation and the work was lost.
+1, this is very frustrating. I accidentally cancelled several running subagents while trying to clear the prompt and now I can't get claude to resume even though I have
--dangerously-skip-permissionson.