docs: add SSH access section to sandbox documentation #352
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 a new "SSH Access to Sandboxes" section to the sandbox CLI documentation that explains how to SSH into sandboxes and the prerequisite of setting up SSH keys first.
This addresses user confusion from the #frictionlog Slack thread where a user encountered "Permission denied (publickey)" errors when trying to SSH into a sandbox without first registering their SSH key with Agentuity.
Changes:
agentuity cloud ssh sbx_xxxusageagentuity auth ssh addReview & Testing Checklist for Human
/Reference/CLI/getting-started#ssh-key-managementresolves correctly in the built docsagentuity auth ssh add,agentuity cloud ssh) match current CLI behaviorSuggested test: Run
npm run devand navigate to the sandbox documentation page to verify the new section renders correctly and the link works.Notes
Requested by: Rick Blalock (@rblalock)
Devin session: https://app.devin.ai/sessions/dd7191c1b2af43b78d515e101fd447af
Summary by CodeRabbit