{
  "format": "agent-article-v0",
  "article_id": "EA-159",
  "canonical_url": "/tools/ea-159-ag-ui",
  "page_type": "reference",
  "claim_ids": [],
  "evidence_ids": [
    "EVD-EA-159-URL-D203E8FD41A4",
    "EVD-EA-159-URL-7E888B93B8A0",
    "EVD-EA-159-URL-6591BA851A2D",
    "EVD-EA-159-URL-10A12ACB9645",
    "EA-159-R11-RESEARCH",
    "EA-159-R11-WEB-READBACK"
  ],
  "unknown_ids": [
    "EA-159-UNKNOWN-01",
    "EA-159-UNKNOWN-CURRENTNESS"
  ],
  "operational_object_ids": [],
  "provider": [],
  "models": [],
  "plans": [],
  "surfaces": [],
  "regions": [],
  "current_status": "UNKNOWN",
  "observation_status": "SPEC_ONLY",
  "freshness": "UNKNOWN",
  "last_verified": null,
  "supersedes": [],
  "superseded_by": [],
  "provenance": [
    "COMM-047-EA0159",
    "SRC-EA-159-URL-D203E8FD41A4",
    "SRC-EA-159-URL-7E888B93B8A0",
    "SRC-EA-159-URL-6591BA851A2D",
    "SRC-EA-159-URL-10A12ACB9645",
    "WEBBODY-EA0159-R8-5379E071"
  ],
  "article_sources": [
    {
      "id": "EVD-EA-159-URL-D203E8FD41A4",
      "evidence_class": "RESEARCH",
      "title": "Agent User Interaction Protocol | AUTHOR_ORG: AG-UI project | CANONICAL_URL:",
      "href": "https://docs.ag-ui.com/introduction",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-159-URL-D203E8FD41A4"
      ],
      "supporting_locators": [
        "EVIDENCE_TABLE",
        "- Agent User Interaction Protocol | AUTHOR_ORG: AG-UI project | CANONICAL_URL: https://docs.ag-ui.com/introduction"
      ],
      "scope": "EVIDENCE_TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-159-URL-7E888B93B8A0",
      "evidence_class": "RESEARCH",
      "title": "AG-UI | AUTHOR_ORG: AG-UI project | CANONICAL_URL:",
      "href": "https://docs.ag-ui.com/concepts/architecture",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-159-URL-7E888B93B8A0"
      ],
      "supporting_locators": [
        "EVIDENCE_TABLE",
        "- AG-UI | AUTHOR_ORG: AG-UI project | CANONICAL_URL: https://docs.ag-ui.com/concepts/architecture"
      ],
      "scope": "EVIDENCE_TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-159-URL-6591BA851A2D",
      "evidence_class": "RESEARCH",
      "title": "AG-UI | AUTHOR_ORG: AG-UI project | CANONICAL_URL:",
      "href": "https://docs.ag-ui.com/concepts/events",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-159-URL-6591BA851A2D"
      ],
      "supporting_locators": [
        "EVIDENCE_TABLE",
        "- AG-UI | AUTHOR_ORG: AG-UI project | CANONICAL_URL: https://docs.ag-ui.com/concepts/events"
      ],
      "scope": "EVIDENCE_TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-159-URL-10A12ACB9645",
      "evidence_class": "RESEARCH",
      "title": "Agent User Interaction Protocol | AUTHOR_ORG: ag-ui-protocol | CANONICAL_URL:",
      "href": "https://github.com/ag-ui-protocol/ag-ui",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-159-URL-10A12ACB9645"
      ],
      "supporting_locators": [
        "EVIDENCE_TABLE",
        "- Agent User Interaction Protocol | AUTHOR_ORG: ag-ui-protocol | CANONICAL_URL: https://github.com/ag-ui-protocol/ag-ui"
      ],
      "scope": "EVIDENCE_TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EA-159-R11-RESEARCH",
      "evidence_class": "RESEARCH",
      "title": "EA-159 監査済みresearch / canonical revision binding",
      "supports": [
        "1. ESTABLISHED [S1 support]: AG-UI describes itself as an open, lightweight, event-based protocol for connecting AI agents to user-facing applications, designed as a general-purpose bi-directional connection between frontend and agentic backend.\n2. ESTABLISHED [S1+S2 support]: The documentation places AG-UI at the agent↔user interaction layer and distinguishes it from MCP (agent↔tools/data) and A2A (agent↔agent). The architecture is described as building on web foundations such as HTTP and WebSockets.\n3. ESTABLISHED [S1 support]: The documentation says the protocol carries agent state, UI intents, and user interactions; it also describes streaming tool results/logs and custom events as part of the interaction surface.\n4. ESTABLISHED [S3 limit]: The event documentation labels the 1.0 specification as Draft and documents event changes/deprecations. Therefore the stable interoperability claim must be version-qualified.\n5. INFERENCE [S1-S4]: AG-UI can reduce ad-hoc frontend/backend wiring for long-running, stateful agent interactions, but the protocol description does not establish that a UI is safe, that an event is authorized, or that a streamed tool result is correct."
      ],
      "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。",
      "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET",
      "source_or_experiment_ids": [
        "COMM-047-EA0159"
      ],
      "supporting_locators": [
        "COMM-047-EA0159",
        "EA-159-R5-LEGACY-MIGRATION-20261008-R1",
        "content/staging/EA-159.md"
      ],
      "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。",
      "provenance_status": "AUDIT_PASS_CANONICAL_BINDING"
    },
    {
      "id": "EA-159-R11-WEB-READBACK",
      "evidence_class": "IMPL",
      "title": "EA-159 Web body identity / canonical readback",
      "supports": [
        "canonical staging bodyのSHA-256一致とR9 canonical ledger readbackをProduction projectionの入力として検証する。"
      ],
      "limit": "body identity/readbackは本文claim自体の真偽や外部ソースの最新性を追加保証しない。",
      "checked_at": null,
      "origin_class": "IMPLEMENTATION_READBACK",
      "source_or_experiment_ids": [
        "WEBBODY-EA0159-R8-5379E071"
      ],
      "supporting_locators": [
        "WEBBODY-EA0159-R8-5379E071",
        "content/staging/EA-159.md",
        "EA-159-R5-LEGACY-MIGRATION-20261008-R1"
      ],
      "scope": "R9/R10 canonical readback後のProduction生成時body identity。",
      "provenance_status": "CANONICAL_READBACK_BODY_HASH_MATCH"
    }
  ],
  "research_sections": [
    {
      "heading": "WHY_THIS_MATTERS_TO_UPDATE",
      "text": "AG-UI addresses the user-facing boundary that is often incorrectly merged with agent-to-tool or agent-to-agent protocols. It is relevant to future updates on streaming, interactive approval, state visibility, and frontend auditability."
    },
    {
      "heading": "SCOPE_ROUTING",
      "text": "interoperability / implementation / Enterprise AI Core / UI boundary / governance / security"
    },
    {
      "heading": "CLAIM_OR_RESEARCH_QUESTION",
      "text": "What does AG-UI claim to standardize between an agentic frontend and backend, what is its maturity boundary, and what remains application-specific?"
    },
    {
      "heading": "EVIDENCE_TABLE",
      "text": "[S1] SOURCE_CLASS: official_project_docs | EXACT_TITLE: AG-UI Overview - Agent User Interaction Protocol | AUTHOR_ORG: AG-UI project | CANONICAL_URL: https://docs.ag-ui.com/introduction | PUBLICATION_UPDATE_ACCESS: current documentation accessed 2026-09-14 00:10 JST | VERSION_RELEASE_TAG: page does not expose a stable release pin | SUPPORTING_LOCATOR: overview lines 20-27 and agentic-protocol distinction lines 35-39 | EVIDENCE_LABEL: VERIFIED_SPEC + PRODUCT_VOLATILE | RELATION: support for protocol scope; limit for release pin and security guarantees.\n[S2] SOURCE_CLASS: official_project_docs | EXACT_TITLE: Architecture - AG-UI | AUTHOR_ORG: AG-UI project | CANONICAL_URL: https://docs.ag-ui.com/concepts/architecture | PUBLICATION_UPDATE_ACCESS: current documentation accessed 2026-09-14 00:10 JST | VERSION_RELEASE_TAG: unpinned current docs | SUPPORTING_LOCATOR: architecture page describing event-driven connection between frontend and agents; current page boundary recorded | EVIDENCE_LABEL: VERIFIED_SPEC + PRODUCT_VOLATILE | RELATION: support/context; limit for maturity.\n[S3] SOURCE_CLASS: official_project_docs | EXACT_TITLE: Events - AG-UI | AUTHOR_ORG: AG-UI project | CANONICAL_URL: https://docs.ag-ui.com/concepts/events | PUBLICATION_UPDATE_ACCESS: current documentation accessed 2026-09-14 00:10 JST | VERSION_RELEASE_TAG: 1.0 Specification (Draft); TypeScript/Python/.NET SDK references; deprecated events removed in 1.0 per page | SUPPORTING_LOCATOR: events page maturity/version note and event catalog | EVIDENCE_LABEL: VERIFIED_SPEC + PRODUCT_VOLATILE | RELATION: support for event surface; limit because 1.0 is explicitly draft.\n[S4] SOURCE_CLASS: author_maintained_repo | EXACT_TITLE: ag-ui - Agent User Interaction Protocol | AUTHOR_ORG: ag-ui-protocol | CANONICAL_URL: https://github.com/ag-ui-protocol/ag-ui | PUBLICATION_UPDATE_ACCESS: repository accessed 2026-09-14 00:10 JST | VERSION_RELEASE_TAG: default branch not pinned | SUPPORTING_LOCATOR: repository description identifying AG-UI as open, lightweight, event-based protocol | EVIDENCE_LABEL: OSS_PRACTICE + PRODUCT_VOLATILE | RELATION: implementation context; limit because default branch is mutable."
    },
    {
      "heading": "FINDINGS",
      "text": "1. ESTABLISHED [S1 support]: AG-UI describes itself as an open, lightweight, event-based protocol for connecting AI agents to user-facing applications, designed as a general-purpose bi-directional connection between frontend and agentic backend.\n2. ESTABLISHED [S1+S2 support]: The documentation places AG-UI at the agent↔user interaction layer and distinguishes it from MCP (agent↔tools/data) and A2A (agent↔agent). The architecture is described as building on web foundations such as HTTP and WebSockets.\n3. ESTABLISHED [S1 support]: The documentation says the protocol carries agent state, UI intents, and user interactions; it also describes streaming tool results/logs and custom events as part of the interaction surface.\n4. ESTABLISHED [S3 limit]: The event documentation labels the 1.0 specification as Draft and documents event changes/deprecations. Therefore the stable interoperability claim must be version-qualified.\n5. INFERENCE [S1-S4]: AG-UI can reduce ad-hoc frontend/backend wiring for long-running, stateful agent interactions, but the protocol description does not establish that a UI is safe, that an event is authorized, or that a streamed tool result is correct."
    },
    {
      "heading": "LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE",
      "text": "Documentation is not proof of adoption or cross-implementation compatibility. Draft event semantics may change; frontend and backend may disagree on event ordering, replay, reconnect, cancellation, or schema. HTTP/WebSockets transport does not provide agent authorization or user-consent semantics by itself. No independent UI reliability, accessibility, security, latency, or event-conformance benchmark was adopted."
    },
    {
      "heading": "AVAILABILITY_GATES",
      "text": "AG-UI event/spec version; frontend/backend SDK release; transport choice; auth/session/tenant binding; event schema and custom-event policy; reconnect/replay behavior; browser/CSP/origin policy; tool-result redaction; user approval mechanism; state persistence; region/data handling; observability and retention."
    },
    {
      "heading": "IMPLEMENTATION_STATE",
      "text": "Evidence-only desk research. No AG-UI SDK, browser session, WebSocket, event stream, or user-facing application was run."
    },
    {
      "heading": "BENCHMARK_OR_EVAL",
      "text": "No event-conformance, reconnect, ordering, latency, accessibility, UI safety, or cross-framework benchmark was run."
    },
    {
      "heading": "SECURITY / PRIVACY / AUDIT / COST / OPERABILITY",
      "text": "UI events may contain prompts, tool arguments/results, identity, and business data; classify/redact before client delivery. Audit should link user/session, agent run, event sequence, approval, tool call, and rendered action. Reconnect and duplicate events require sequence/idempotency policy. Cost/operability must count long-lived connections, streamed tokens/events, retries, and frontend failure; not measured."
    },
    {
      "heading": "SAFE_WORDING_FOR_FUTURE_BOOK",
      "text": "「AG-UIは、agentic backendとユーザー向けfrontendの間を、HTTP／WebSocket等の上にイベント駆動・双方向で接続するプロトコルである。イベント仕様1.0は当該資料でDraftと表示されているため、採用時は版・SDK・再接続・認可・表示安全性を個別に確認する。」"
    },
    {
      "heading": "UPDATE_WORK_HANDOFF",
      "text": "Future update Work should pin the event specification and SDK commits, then test text/state/tool-result/custom events under reconnect, duplicate, out-of-order, cancellation, partial failure, approval, redaction, and browser-origin controls. Preserve the layer distinction from MCP and A2A."
    },
    {
      "heading": "OPEN_UNKNOWN",
      "text": "stable release and governance; SDK parity; event ordering/replay/idempotency; auth and user-consent profile; browser security guidance; accessibility; cross-framework compatibility; production incident history; cost/SLO."
    },
    {
      "heading": "STOP_CONDITION",
      "text": "Do not present AG-UI Draft events as a finalized universal standard. Do not claim that an event stream authorizes a tool action, proves backend correctness, or safely exposes all agent state.\nUNIT_CLOSE_STATUS: INDIVIDUAL_BOUNDED_CLOSE / EVIDENCE_RECORDED / UNKNOWN_PRESERVED"
    },
    {
      "heading": "EVIDENCE PACKET",
      "text": "---"
    }
  ],
  "human_url": "/tools/ea-159-ag-ui",
  "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-159-ag-ui",
  "json_url": "/agent/article.json?path=%2Ftools%2Fea-159-ag-ui"
}