Context
The stack is deliberately API-only — no bundled UI, and that stays. But AG-UI is emerging as a standard protocol for connecting agent backends to third-party frontends (streaming, state sync, tool-call rendering). Supporting it would let any AG-UI-compatible frontend plug into pack routes without this repo shipping or maintaining a UI.
Scope
- An opt-in AG-UI endpoint (e.g.
AGUI_ENABLED=false by default, consistent with the project's feature-flag conventions) that adapts pack runs/streams to AG-UI events.
- Mapping decisions: pack phases and typed outputs → AG-UI message/state events; budget errors (
402) and compliance gating (403) → protocol-level errors.
- Works against the mock provider so it's testable in CI without an API key.
Dependencies
Depends on token-level streaming (#86) — AG-UI's value is largely incremental output; doing it phase-level only would underdeliver.
Open questions
- Protocol maturity: AG-UI is young; pin a spec version and treat the adapter as experimental at first.
Context
The stack is deliberately API-only — no bundled UI, and that stays. But AG-UI is emerging as a standard protocol for connecting agent backends to third-party frontends (streaming, state sync, tool-call rendering). Supporting it would let any AG-UI-compatible frontend plug into pack routes without this repo shipping or maintaining a UI.
Scope
AGUI_ENABLED=falseby default, consistent with the project's feature-flag conventions) that adapts pack runs/streams to AG-UI events.402) and compliance gating (403) → protocol-level errors.Dependencies
Depends on token-level streaming (#86) — AG-UI's value is largely incremental output; doing it phase-level only would underdeliver.
Open questions