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
1 participant
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.
I'd like apps that QM builds and deploys to use QM as their agent backend through AG-UI. The use case is internal apps for signed-in users, with shared state, browser-side tools, and human-in-the-loop interactions inside the app's own UI.
The proposal is an optional plugin, Pi first, targeting the full published spec. Calls would run as the viewing user through QM's authenticated gateway. It also asks whether generic core support for state and frontend-tool continuation is the right boundary.
This PR adds only
adrs/ag-ui.mdto get alignment before implementation.