[BUG] after close vs-code during sub agent task, the task ending don't report his state to the parent agent

[bozoweed]

Problem (one or two sentences)

if you use orchestrator and close you vs-code during sub task, then restart vs-code and resume the task , when task is over it's not notifie the orchestrator

Context (who is affected and when)

every people that use subtask system, when need to close vs-code during hugh task or when need to reload view to fix some issue

Reproduction steps

1. run orchestrator
2. wait for subtask begin and close vs-code
3. restart vs-code and the sub task
4. at end of the sub task not report done to orchestrator

Expected result

should report his final state to orchestrator

Actual result

sub task is endend like if not runed from parent agent

Variations tried (optional)

No response

App Version

latest

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[bozoweed]

@roomote can you investigate on that issue and provide PR. something simple not complex should just keep refer to his parent agent and if have one should report to that agent his final state , all ready working if not closing vs-code so juste turn that on persistente system

[roomote]

I'm exploring a potential fix for this issue where subtasks don't report back to the parent orchestrator after VS Code is restarted. I'll investigate the state management and persistence mechanisms to ensure proper communication is restored.

[roomote]

@bozoweed I've created PR #9039 to address this issue: #9039

The fix restores parent task references when resuming subtasks from history after VS Code restarts. This ensures that subtasks can properly report their final state back to their parent tasks.

The implementation:

• Persists parent-child relationships through the existing task metadata
• Restores parent task references when resuming from history
• Recursively restores parent tasks if they're not already in the task stack
• Maintains the parent-child relationship across VS Code sessions

All CI checks have passed. The solution is simple as requested - it leverages the existing persistence system to maintain the parent reference and ensures completion reporting works after restart.

[hannesrudolph]

Duplicate of #8081