ag_ui_strands 0.1.0__tar.gz

ag_ui_strands-0.1.0/.gitignore

@@ -0,0 +1,134 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Ruff
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db

ag_ui_strands-0.1.0/PKG-INFO

@@ -0,0 +1,8 @@
+Metadata-Version: 2.4
+Name: ag_ui_strands
+Version: 0.1.0
+Author: AG-UI Contributors
+Requires-Python: <3.14,>=3.12
+Requires-Dist: ag-ui-protocol>=0.1.10
+Requires-Dist: fastapi>=0.115.12
+Requires-Dist: strands-agents>=1.15.0

ag_ui_strands-0.1.0/README.md

@@ -0,0 +1,58 @@
+# AWS Strands Integration for AG-UI
+
+This package exposes a lightweight wrapper that lets any `strands.Agent` speak the AG-UI protocol. It mirrors the developer experience of the other integrations: give us a Strands agent instance, plug it into `StrandsAgent`, and wire it to FastAPI via `create_strands_app` (or `add_strands_fastapi_endpoint`).
+
+## Prerequisites
+
+- Python 3.10+
+- `poetry` (recommended) or `pip`
+- A Strands-compatible model key (e.g., `GOOGLE_API_KEY` for Gemini)
+
+## Quick Start
+
+
+The `examples/server/__main__.py` module mounts all demo routes behind a single FastAPI app. Run:
+
+```bash
+cd integrations/aws-strands/python/examples
+poetry install
+poetry run python -m server
+```
+
+It exposes:
+
+| Route | Description |
+| --- | --- |
+| `/agentic-chat` | Frontend tool demo |
+| `/backend-tool-rendering` | Backend tool rendering demo |
+| `/shared-state` | Shared recipe state |
+| `/agentic-generative-ui` | Agentic UI with PredictState |
+
+This is the easiest way to test multiple flows locally. Each route still follows the pattern described below (Strands agent → wrapper → FastAPI).
+
+## Architecture Overview
+
+The integration has three main layers:
+
+- **StrandsAgent** – wraps `strands.Agent.stream_async`. It translates Strands events into AG-UI events (text chunks, tool calls, PredictState, snapshots, etc.).
+- **Configuration** – `StrandsAgentConfig` + `ToolBehavior` + `PredictStateMapping` let you describe tool-specific quirks declaratively (skip message snapshots, emit state, stream args, send confirm actions, etc.).
+- **Transport helpers** – `create_strands_app` and `add_strands_fastapi_endpoint` expose the agent via SSE. They are thin shells over the shared `ag_ui.encoder.EventEncoder`.
+
+See [ARCHITECTURE.md](ARCHITECTURE.md) for diagrams and a deeper dive.
+
+
+## Key Files
+
+| File | Description |
+| --- | --- |
+| `src/ag_ui_strands/agent.py` | Core wrapper translating Strands streams into AG-UI events |
+| `src/ag_ui_strands/config.py` | Config primitives (`StrandsAgentConfig`, `ToolBehavior`, `PredictStateMapping`) |
+| `src/ag_ui_strands/endpoint.py` | FastAPI endpoint helper |
+| `examples/server/api/*.py` | Ready-to-run demo apps |
+
+## Next Steps
+
+- Wire Strands’ callback handler into the wrapper to expose multi-agent metadata.
+- Add an event queue layer (like the ADK middleware) for resumable streams and non-HTTP transports.
+- Expand the test suite as new behaviors land.
+

ag_ui_strands-0.1.0/examples/.gitignore

@@ -0,0 +1,98 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Ruff
+.ruff_cache/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db

ag_ui_strands-0.1.0/examples/README.md

@@ -0,0 +1,82 @@
+# AWS Strands Example Server
+
+Demo FastAPI server that wires the Strands Agents SDK (Gemini models) into the
+AG-UI protocol. Each route mounts a ready-made agent that showcases different UI
+patterns (vanilla chat, backend tool rendering, shared state, and generative UI).
+
+## Requirements
+
+- Python 3.12 or 3.13 (the project is pinned to `<3.14`)
+- Poetry 1.8+ (ships with the repo via `curl -sSL https://install.python-poetry.org | python3 -`)
+- Google API key with access to Gemini 2.5 Flash (set as `GOOGLE_API_KEY`)
+- (Optional) AG-UI repo running locally so you can point the Dojo at these routes
+
+## Quick start
+
+```bash
+cd integrations/aws-strands/python/examples
+
+# pick a supported interpreter if your global default is 3.14
+poetry env use python3.13
+
+poetry install
+```
+
+Create a `.env` file in this folder (same dir as `pyproject.toml`) so every
+example can load credentials automatically:
+
+```bash
+GOOGLE_API_KEY=your-gemini-key
+# Optional overrides
+PORT=8000                 # FastAPI listen port
+```
+
+> The sample agents default to `gemini-2.5-flash` and already set sensible
+> temperature/token parameters; override only if you need a different tier.
+
+## Running the demo server
+
+Either command exposes all mounted apps on `http://localhost:${PORT:-8000}`:
+
+```bash
+poetry run dev          # uses the Poetry script entry point (server:main)
+# or
+poetry run python -m server
+```
+
+The root route lists the available demos:
+
+| Route | Description |
+| --- | --- |
+| `/agentic-chat` | Simple chat agent with a frontend-only `change_background` tool |
+| `/backend-tool-rendering` | Backend-executed tools (charts, faux weather) rendered in AG-UI |
+| `/agentic-generative-ui` | Demonstrates `PredictState` + delta streaming for plan tracking |
+| `/shared-state` | Recipe builder showing shared JSON state + tool arguments |
+
+Point the AG-UI Dojo (or any AG-UI client) at these SSE endpoints to see the
+Strands wrapper translate Gemini events into protocol-native messages.
+
+## Environment reference
+
+| Variable | Required | Purpose |
+| --- | --- | --- |
+| `GOOGLE_API_KEY` | Yes | Auth for the Gemini SDK (`strands.models.gemini.GeminiModel`) |
+| `PORT` | No | Overrides the default `8000` uvicorn port |
+
+All OpenTelemetry exporters are disabled by default in code (`OTEL_SDK_DISABLED`
+and `OTEL_PYTHON_DISABLED_INSTRUMENTATIONS`), so you do not need to set those
+manually.
+
+## How it works
+
+- Each `server/api/*.py` file constructs a Strands `Agent`, registers any tools,
+  and wraps it with `ag_ui_strands.StrandsAgent`.
+- `server/__init__.py` mounts the four FastAPI apps under a single router and
+  exposes the `main()` entrypoint that `poetry run dev` calls.
+- The project depends on `ag_ui_strands` via a path dependency (`..`) so you can
+  develop the integration and server side-by-side without publishing a wheel.
+- Want a different Gemini tier? Update the `model_id` argument in the agent
+  definitions inside `server/api/*.py`.
+
+
+