revert(remote): remove SSH remote feature from develop#690
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
1 participant
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
Why
The current SSH Remote feature is not mature enough to stay on
developfor release. The exposed user experience is also not ready: the run-location controls, host selection, remote directory, run mode, and protected path settings need a more intentional product/design pass before shipping.This PR removes the feature from the release train while keeping unrelated MCP Remote OAuth work intact.
Tests
npm run typechecknpm --prefix kun run typechecknpm run lint(passes with the existing 14 hook dependency warnings)npm testnpm --prefix kun testnpm run buildgit diff --check develop..HEAD