https://docs.ag-ui.com/introduction

この標準文書は未翻訳です。以下に英語の原文を表示します。

この情報源から得られる知見

  • Define ordered event semantics, reconnect/idempotency, and partial-failure handling for every AG-UI integration — the protocol governs transport reliability, not UI composition.
  • Cancellation and resume must be first-class in every streaming UI surface backed by AG-UI: cancel must be keyboard-reachable and immediately effective.
  • Shared-state conflict resolution and accessible streaming-announcement behavior (live regions, partial-output labelling) must be explicitly designed, not assumed from the transport.
  • Distinguish AG-UI transport from A2UI UI description: AG-UI carries events and state, A2UI describes component schemas — they are complementary layers, not alternatives.

AwesomeDSへの反映先

実装・成果物

直接リンクされた成果物はありません。

注意事項と模倣防止

Transfer ordered event semantics, cancel/resume, and shared-state conflict patterns; do not conflate AG-UI transport with the UI schema or product policy layers.

証拠レベル: first-party-guidance · 最終確認 2026-07-16 · 確認周期 30d