Repository navigation
fix: integrate launch safeguards and optional pairing - #29
Merged
Merged
Conversation
# Conflicts: # docs/setup.md # site/docs/try.mdx # site/src/components/LocalConnection.tsx # site/src/components/Thread.tsx
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Kinfe123
marked this pull request as ready for review
October 17, 2026 05:37
This branch was successfully deployed
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.
Land the launch fixes together so their interaction is verified before main changes. This combines #25 (host opt-in pairing), #26 (special-file connector safeguards), #27 (patched dependencies), and #28 (released CLI/source-preview guidance), preserving their commits.
Resolve overlapping documentation and connection-panel edits: source builds connect directly unless the host requires pairing; released v0.3.0 keeps its separate folder connector and can reveal the pairing form. The agent engine, provider/tool handling, terminal/Harness adapter, WASM engine, workspace package, and access adapter are unchanged.
Validation passed on adcf0b5:
Remaining release constraints are unchanged: this does not publish a CLI or npm package; the installer still serves v0.3.0, and transitive audit findings remain documented in #27. Merging main follows the existing deployment integration.