[FEATURE]: Allow "aborted" agents to be continued

[skerit]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Sometimes a sub-agent has to be paused or some unforeseen circumstance causes it to abort automatically. In these cases the subagent is lost. There is no session-id to re-use, and the only thing the main agent can do is start the same task over.

This is quite annoying and wasteful of tokens. Why not simply always return the session id and let any subagent be resumed, no matter if it's "aborted" or "finished".

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]: Agent-level resume for subagents (resumeSessionId parameter) #6584: [FEATURE]: Agent-level resume for subagents (resumeSessionId parameter) - directly addresses resuming aborted subagents
• [FEATURE]:Add retry / re-run capability when operation is aborted #8197: [FEATURE]:Add retry / re-run capability when operation is aborted - similar motivation for avoiding token waste on failures
• [FEATURE]: /continue command #5150: [FEATURE]: /continue command - session continuation feature
• [FEATURE]: implement a /resume and /pause command #7226: [FEATURE]: implement a /resume and /pause command - pause/resume capabilities
• [FEATURE]: Better session resume ergonomics #8336: [FEATURE]: Better session resume ergonomics - improving resumption UX

Feel free to ignore if none of these address your specific case.

[skerit]

Issue #6584 seems to be about an internal API, not about the main agent being able to resume an aborted session.
Issue #8197 seems to be about retries for any failed input, not just subagents.

So I don't think these apply.

[github-actions]

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.