GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [REQUEST] AG-UI support · Issue #5969 · simstudioai/sim

[REQUEST] AG-UI support #5969

New issue
Copy link
New issue
Copy link
Open
Open
[REQUEST] AG-UI support#5969
Copy link
Labels
featureNew feature or requestNew feature or request

Description

@ebe-wolf
ebe-wolf
opened on Jul 26, 2026
Issue body actions

Add support for the AG-UI (Agent-User Interaction) Protocol to enable standardized real-time communication between AI agents and frontend clients.

The implementation should expose agent execution events (e.g., messages, tool calls, reasoning/status updates, errors, completion, and streamed responses) using the AG-UI protocol, allowing compatible clients such as CopilotKit and other AG-UI consumers to interact with the backend without custom integrations.

Scope

  • Implement AG-UI protocol support for agent execution.
  • Stream agent events (text, tool calls, status, errors, completion, etc.).
  • Map internal workflow/agent events to AG-UI event types.
  • Support incremental/streaming responses.
  • Ensure protocol compliance with the AG-UI specification.
  • Provide an extensible architecture for future event types and protocol updates.

Acceptance Criteria

  • AG-UI compatible clients can communicate with the backend.
  • Agent responses are streamed using AG-UI events.
  • Tool invocation lifecycle is exposed through the protocol.
  • Errors and cancellation events are properly propagated.
  • Protocol implementation is documented and covered by integration tests.

Benefits

  • Standardized frontend integration.
  • Interoperability with existing AG-UI ecosystem tools.
  • Easier maintenance by decoupling internal agent logic from client-specific protocols.
  • Foundation for future multi-agent and workflow integrations.
Reacted by pyush

Activity

  1. ebe-wolf
    added
    featureNew feature or requestNew feature or request
    on Jul 26, 2026
  2. wav-piyush commented on Sep 18, 2026

    @wav-piyush
    wav-piyush
    on Sep 18, 2026
    More actions

    @ebe-wolf I dug into the cobebase, what i think is we should hold off on this AG-UI implementation for now.

    I have some points

    1. we already have an internal streaming protocol system that covers streaming responses like tool lifecycles, errors, cancellation, checkpoints/resume, sub-agents, etc.
    2. there isn't a clear demand signal, yet i think If we had a concrete consumer like CopilotKit, that would be a strong reason to implement it. Without one, we'd mainly be adding compatibility for a potential future use case.
    3. there is an opportunity cost. Implementing this requires event mapping, streaming/tool handling, protocol compliance, tests, and documentation adding another API contract to maintain.

    I think AG-UI is worth keeping on the roadmap rather than rejecting it outright.

    @waleedlatif1 if you think we should add the AG-UI protocol.

    Please let me know , i'm happy to implement it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or requestNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.