feat: Add support for AG-UI

[adlio]

Adds an AG-UI "bridge" to enable Strands Agents to be the backend for an agentic frontend like Copilot Kit.

Description

Posting this for draft review and considering... continuing to work on docs and examples for using this.

Documentation PR

TBD

Type of Change

• New features

Testing

Used this version of Strands to build an interactive web-based Tic Tac Toe against Claude via Bedrock.

Checklist

• I have read the CONTRIBUTING document
• I have added 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
• 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.

[ryanycoleman]

Addresses #140

[zastrowm]

Based on the current implementation, this looks like several related features are part of this. Specifically, I think we need we're seeing gaps in:

• Session/agent-state ([FEATURE] Add Database Session Management #33, [FEATURE] Community-driven session management #57) (CC @Unshure)
• Multi-agent integration (can't find any direct issues related, but I know @awsarron will be looking at)
• Built-in tools ([FEATURE] Develop strategy for vending tools tools#31)

[adlio]

Based on the current implementation, this looks like several related features are part of this. Specifically, I think we need we're seeing gaps in:

* Session/agent-state ([[FEATURE] Add Database Session Management #33](https://github.com/strands-agents/sdk-python/issues/33), [[FEATURE] Community-driven session management #57](https://github.com/strands-agents/sdk-python/issues/57)) (CC @Unshure)

* Multi-agent integration (can't find any direct issues related, but I know @awsarron will be looking at)

* Built-in tools ([[FEATURE] Develop strategy for vending tools tools#31](https://github.com/strands-agents/tools/issues/31))

Thanks for the review @zastrowm. Yes! This PR as-is would be valuable but not sufficient. I'm continuing to work on a sample/docs updates, etc. I'll review those other bits to see if the agent state and built-in tools work could align as well.

[clareliguori]

It looks like these are already defined in the AG-UI Python SDK - should we use that Enum instead: https://github.com/ag-ui-protocol/ag-ui/blob/d53b012ff8051420905d85bb1a443c2729616d88/python-sdk/ag_ui/core/events.py#L29

[adlio]

I agree, but I'd assumed the team would want to avoid having all strands agents depend on ag_ui (it's barely older than strands itself, and not all agents will have a web-based UI). Would you prefer: 1) Taking a hard-dependency on ag_ui and adding a bridge directly in the core package, or 2) Having an ag_ui example that could potentially turn into a strands-ui package if it succeeds?

[zastrowm]

I agree on avoiding a direct dependency - at this point we'd be looking towards an example/sample.

There's still a lot of open questions around the other features (#33, #31, multi-agent) which the team is starting work towards and knowing the gaps we have is really useful - but it's still too early for a direct integration.

[NathanTarbert]

Hey @adlio this is awesome, I'm with the org behind AG-UI and I'd love to chat more about this integration to make sure it's easy for our users to build with it.