[FEATURE] Async Support in ConversationManager

[chase-prescient]

Problem Statement

I love everything about Strands! except I think it would be very beneficial to add async support to ConversationManager. I currently have several use cases that prevent me from fully adopting strands because I need to call an asynchronous coroutine within the apply_management method. Is this on the roadmap at all?

Proposed Solution

maybe like an aapply_management method the event loop calls?

Use Case

1. Injecting External State from Async Sources
2. Tooling and Middleware That Depends on Async I/O

Alternatives Solutions

No response

Additional Context

No response

[zastrowm]

Side note: After #1374 is merged, ConversationManagers can be HookProviders which can be asynchronous. It wouldn't be clean, but it would allow you to do asynchronous things.

That said, I also don't see a problem with allowing conversation managers in general to be asynchronous - I think everywhere we call apply_management or reduce_context would support reduce_context

[Unshure]

Hi, we are inclined to this feature, but we would like to review and refine a proposal before we are ready to review a pull request.