Repository navigation
Release 0.2.18: explicit continuation consent and retained Bridge outcomes - #29
Merged
Merged
Conversation
added 30 commits
October 15, 2026 19:38
added 8 commits
October 15, 2026 21:54
ancongui
marked this pull request as ready for review
October 16, 2026 06:58
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.
Changes
Signed source-control continuation requires separate administrator consent bound to the original execution identity, current repository mapping, component scope, plan and WAL. Studio guides that review in three steps and retrieves the original receipt after a lost response. The SDK, CLI and MCP expose the same operations.
Ambiguous Bridge responses and cancellations retain the original intent and block generic resume, handoff and replacement retries. Invocation-local tracking survives native agent graph cancellation. Bridge requests also disable HTTP redirect following independently of SDK retries: a 307/308 response causes one inference request and an unknown-outcome hold instead of forwarding a second POST.
The factory opens in overview mode, stage focus is explicit, and compact consent reviews remain readable in short or zoomed viewports. Updated walkthroughs include the consent and recovery layouts.
Validation
Exact-head CI passed: 2,423 Python cases passed with 51 explicit skips and four warnings; 263 Studio unit cases and 551 browser cases passed. Documentation, container and installed-wheel verification gates also passed. No cloud runtime deployment or live provider inference is part of this change. Existing unknown outcomes remain held; recovering a remote completion into a running agent is outside this release.