-
Notifications
You must be signed in to change notification settings - Fork 623
AgentKit Option C: AG-UI wire format with a typed extension profile #4612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| --- | ||
| "@agent-native/core": patch | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 Release the Core wire change with an appropriate versionThe changeset still classifies
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixed in 614404f. The changeset now marks both @agent-native/core and @agent-native/agentkit as pre-1.0 minor releases, matching the explicitly documented protocol-v2 wire break and coordinated migration requirement. The no-major-changeset guard and all 72 repository guards pass. |
||
| "@agent-native/agentkit": minor | ||
| --- | ||
|
|
||
| **Breaking (pre-1.0):** AgentKit protocol v2 intentionally rejects v1-only | ||
| peers because the AG-UI envelope is not wire-compatible with the original | ||
| Builder envelope. Upgrade the AgentKit client and server together, then rerun | ||
| transport conformance before deploying a custom adapter. The deprecated | ||
| `resolveApproval` API remains only as a source-compatibility bridge after both | ||
| peers are on v2. | ||
|
|
||
| Carry AgentKit runs over the AG-UI wire format instead of a Builder-only | ||
| envelope. Overlapping events map onto native AG-UI event types, and the | ||
| Builder-specific events travel as a versioned typed extension profile over | ||
| `CUSTOM`, so a stock AG-UI client can read the stream while AgentKit consumers | ||
| still receive fully typed domain events. Sequencing, replay cursors, and profile | ||
| version negotiation are defined as explicit extensions because AG-UI specifies | ||
| none of them. Approvals now use AG-UI's interrupt model: the Core transport | ||
| exposes `resumeRun` with `resume` entries in place of `resolveApproval`. An | ||
| approval interrupt terminally closes its protocol run, and `resumeRun` returns | ||
| the distinct replacement run that carries the resolution and continued work. | ||
Uh oh!
There was an error while loading. Please reload this page.