feat(runtime): compose steerable provider sessions - #662
Draft
drewstone wants to merge 2 commits into
Draft
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
createSteerableSandboxSession; the low-level one-shot provider executor is unchanged.AgentSession.cancel(), and provider-specific stream/cancel failures become the existing interrupt signal so a forced steer can re-plan.AgentProfileidentity, provider-owned backend defaults, provider options, normalized events, usage fields, live progress, and trace data survive the adapter boundary.No new agent loop or provider-specific coordinator is introduced.
Proof
Retained risk
The package has no configured third-party environment provider, so the live network-provider check remains an integration responsibility; the PR proves the public Interface 0.39 contract with exact provider events and session controls.
@tangle-network/agent-provider-cli-bridge@0.2.33advertises continuation but does not exposeenvironment.session(), so this mode rejects it before creation.@tangle-network/agent-provider-tangle@0.4.5exposes the required session controls; adding them to the CLI-bridge provider is a separate upstream change.