Repository navigation
docs: connect an AG-UI client to an Everruns endpoint - #113
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/ag-ui.md: how to point an AG-UI 1.0 client (@ag-ui/clientHttpAgent, CopilotKit) at an Everruns AG-UI endpoint, with auth, thread ids, interrupt reasons and resume payloads, frontend tools, and token usage.Test Plan
Docs only, no code or generated models change.
just pre-pushpasses. Payload shapes checked against the server's resume parsing (ag_ui_interrupts.rs) and frontend tool handling (ag_ui_frontend_tools.rs).Checklist