Repository navigation
feat(ag-ui): answer interrupts through the core resume command - #1677
Merged
Merged
Conversation
AgentSession and AgentSnapshot take a second type parameter for application
state. The snapshot gains an optional, deeply readonly `state`, and `submit`
accepts `{ message, state }` with a partial state as well as plain text.
A session is told its state type by one declaration: `type<T>()` for the type
alone, or any Standard Schema value to also check each state as it arrives.
`readState` runs that check for session implementations. The fake session
holds, sets and validates state the same way.
No backend session supplies `state` yet; LangGraph and AG-UI follow.
createSession takes a stateType, either type<T>() or a Standard Schema. createAgentSession publishes the state document as the typed state of the core snapshot, checks it once per document when a schema is declared, and reports a rejected document in stateIssues without failing the run. A session created without a state reports none until one is supplied.
The session createSession returns now publishes the core snapshot itself: messages, tool calls, error, usage and typed state beside the protocol evidence. createAgentSession is removed. retry rejects when the failure leaves the backend outcome open, as the core contract requires, and the literal state document a request sends is no longer published.
…ntract The snapshot gains optional interrupts and subagents, and the session an optional resume(responses) that answers pending interrupts by id. The fake session publishes both fields and records resume calls.
Every published interrupt has an id, and resume takes the core contract's responses in place of a bare value. One pending interrupt receives its response's value; several are answered as one map keyed by backend id. Callers in the cockpit examples, the native conversation example and the parity fixtures move to the new command.
…he client only The raw session has loaded nothing at that point, so its resume rejects for a missing pause, not for the unmatched id. The session's own specs cover the rejection; the diagnostic keeps the provider routing evidence.
…already merged by its final head)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…blish core child agents
…d by its final head)
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
The AG-UI session's
resumeis now the core contract's command, and its snapshot publishes the coreinterruptsandsubagents. With this, an AG-UI session is a coreAgentSessionincluding pause and resume.Includes #1675. #1659 has merged, and with it on
main#1675 can no longer pass on its own: the AG-UI session is now typed as a core session, so the coreresumeandsubagentsthat #1675 adds need the AG-UI changes in this PR to compile. This PR carries both. The commit specific to this PR isfeat(ag-ui): answer interrupts through the core resume command and publish core child agents; the rest of the diff is #1675 (core contract, LangGraph session and its callers).Breaking changes
resume(pause, responses)is nowresume(responses). There is no pause token to pass: the session answers the pause that is pending.decision.idis still published.value, notpayload. The request anddecision.attempt.responsesstill carry the protocol'spayload. A response may still carry the protocol's optionalmetadata.resumerejects instead of resolving'error'when it cannot send what was asked: nothing is waiting, the pausing run has not settled, an answer was already sent, a run is active, an interrupt has expired, a response names an interrupt that is not pending or names one twice, or an interrupt is left unanswered. It still resolves'aborted'after disposal or with an aborted signal, and with the run's outcome once the answer is sent.snapshot.subagentsentries are core child agents. Each hasid,status, its ownmessagesandtoolCalls, andname,description,toolCallId,parentId,errorwhen known. The protocol evidence stays on each entry asstartedandterminal, so code that reads those keeps working.earlierSubagentsis unchanged.Added
snapshot.interrupts: the pending interrupts, from the pause until an answer is sent. Absent when nothing is waiting and for a pause the session cannot answer.Why the child agents are in this PR
The core contract added
subagentsin #1675, and the AG-UI snapshot already had a field of that name holding protocol evidence. The session could not satisfy the core type until that field held core children, so this PR does it rather than renaming the field.Things to know
completeeven when its outcome issuspended; this matches what ReactChatalready shows.Chatattributes messages the same way today.Verification
nx run-many -t runtime-quality,runtime-type-tests,test,type-tests,lint -p core,ag-ui,langgraph,react,angularpasses.nx run-many -t test,lintfor the 10 AG-UI and runtime cockpit React apps passes.node --test scripts/react-parity/ag-ui-candidate-package.spec.mjs: 28 pass.inventory.mjs --check --drift warnpasses.verify-ag-ui-candidate.mjs,verify-ag-ui-client-tools.mjs, the native browser fixtures, the Mastra runner itself, and Playwright e2e. The machine was too loaded for the package verifiers to finish.🤖 Generated with Claude Code