chore(deps): add ssh2 as a regular dependency#23
Merged
khaliqgant merged 1 commit intomainfrom Apr 29, 2026
Merged
Conversation
Required for the upcoming `ricky connect <provider>` flow that imports `connectProvider()` from `@agent-relay/cloud`. The cloud package declares `ssh2` as an `optionalDependency`, which means a globally- installed `ricky` could silently fall back to spawning system `ssh` when a user installs with `--omit=optional`, in restricted CI environments, or on Windows without OpenSSH. Pinning `ssh2` here guarantees the native SSH path on every install. Mirrors the pattern in the relay CLI repo, where `ssh2` is a regular dep at the package root for the same reason. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
Adds
ssh2(^1.17.0) as a regular dependency of@agentworkforce/rickyso that globally-installed users get the native SSH path for the upcomingricky connect <provider>flow.Why
Once we wire up
ricky connecttoconnectProvider()from@agent-relay/cloud(relay PR #798), ricky will depend onssh2transitively through@agent-relay/cloud. But the cloud package declaresssh2as anoptionalDependency— and "optional" means failure-is-non-fatal, not skipped. The realistic failure modes for globally-installed ricky users:npm install -g ricky --omit=optional(ornpm config set omit optional) → ssh2 silently skippedsshfallback in the cloud SDK uses anSSH_ASKPASSscript, which is a Linux/macOS pattern)When
ssh2is missing the cloud SDK'sloadSSH2()returnsnulland the code falls back to spawning systemssh, which fails silently in the environments above.Pinning
ssh2as a regular dep at the ricky package root guarantees the native SSH path on every install. This mirrors the pattern in the relay CLI repo, wheressh2is a regular dep at the package root for the same reason — even though@agent-relay/cloud(its bundled dep) declares ssh2 as optional.Test plan
npm installresolvesssh2@^1.17.0cleanlypackage-lock.jsonupdatedconnectProvider()integration lands, smoke testricky connect claudeend-to-endCompatibility
Additive — no removed deps, no API surface change. Bundle size grows by
ssh2(~150KB gzipped, plus its nativecpu-featureshelper).