feat: Implement breakpoint resume functionality for failed tasks

[Zephyroam]

Description

Fixes #3739

Checklist

Go over all the following points, and put an x in all the boxes that apply.

• I have read the CONTRIBUTION guide (required)
• I have linked this PR to an issue using the Development section on the right sidebar or by adding Fixes #issue-number in the PR description (required)
• I have checked if any dependencies need to be added or updated in pyproject.toml and uv lock
• I have updated the tests accordingly (required for a bug fix or a new feature)
• I have updated the documentation if needed:
• I have added examples if this is a new feature

If you are unsure about any of these, don't hesitate to ask. We are here to help!

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[nitpicker55555]

You designed an entire serialize → store → deserialize pipeline to maintain the agent’s context, but I think this workflow is overly complex and introduces a number of issues, for example, _save_breakpoint_history is invoked repeatedly, and exceptions can cause agent leakage.

Why don’t we simply avoid releasing the agent when a task fails and reuse the existing instance directly instead?

[Zephyroam]

You designed an entire serialize → store → deserialize pipeline to maintain the agent’s context, but I think this workflow is overly complex and introduces a number of issues, for example, _save_breakpoint_history is invoked repeatedly, and exceptions can cause agent leakage.

Why don’t we simply avoid releasing the agent when a task fails and reuse the existing instance directly instead?

Done. Thanks @nitpicker55555