feat(runtime): retain CLI Bridge runs across restart - #15
Merged
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.
Outcome
Braid now keeps CLI Bridge provider jobs and sessions alive across detach, process restart, reconnect, reconcile, cancellation, and follow-up turns.
The TUI and JSONL interface show the exact AgentProfile, runner, model route, connection, environment, provider session, token usage, model calls, and measurement completeness.
Direct product proof
A clean install of the exact packed
@tangle-network/braid@0.1.0candidate drove Pi 0.83.0 withtangle-router/glm-5.2through CLI Bridge.3f0343a6337feb7da794e9195706f8aefc119068e2c35113d9df8b3293fa84c9./tmp/braid-live-core-final.jsonfromnode scripts/live-core/run.mjs.Checks
pnpm check: 633 tests; 631 passed; 2 intentional skips; 0 failed.Product recording