refactor: Remove _remove_dangling_messages from SlidingWindowConversationManager

[Unshure]

Breaking Change!!

Description

Remove _remove_dangling_messages from SlidingWindowConversationManager.

Retain previous behavior

For users who want to keep the behavior that the sdk provided before this change, you can add the following logic after your agent call:

agent.(<Your input here>)
if len(agent.messages) > 0 and agent.messages[-1]["role"] == "assistant":
    if any("toolUse" in content for content in agent.messages[-1]["content"]):
        agent.messages.pop()

We believe this currently only happens if the event-loop is interrupted by client applications and thus believe that clients should handle this case outside of the loop.

In the future, we expect dangling tool_use messages to be a valid use-case where agents can resume from and thus we're removing this logic before we got 1.0

Related Issues

N/A

Documentation PR

N/A

Type of Change

Breaking change

Testing

How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli

• I ran hatch run prepare

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[zastrowm]

Can you add a breaking change notice and how customers can do this themselves?

[Unshure]

Can you add a breaking change notice and how customers can do this themselves?

Added to the description