CLI and Cloud
Connect the local vault to a workspace while keeping the direction and private-key scope under your control.
Authorize the device
ssher cloud login
The CLI creates a device key, opens a browser approval flow, and receives a managed CLI session after you approve the displayed code. The private device key remains on this computer.
Link a workspace
ssher cloud link --organization your-workspace ssher cloud status
You can use a workspace name, slug, or ID. One local CLI configuration links to one active workspace at a time.
Choose a sync direction
ssher cloud pullBring encrypted Cloud records into this local vault.ssher cloud pushEncrypt and send eligible local records to the linked workspace.ssher cloud syncReconcile local and Cloud changes, stopping on conflicts that need your decision.ssher cloud logoutRemove the local Cloud session without deleting workspace data.A normal push does not upload them. Use ssher cloud push --include-keys only when you intentionally want the encrypted key material available to browser SSH workflows.
Know which path your connection takes
SSH and SFTP started by the CLI connect directly from your computer to the server. A browser terminal connects through the managed Cloud gateway so the remote tmux session can remain available after the tab closes.
For teams, invitations, server scopes, portable access, and browser terminals, continue to the ssher Cloud documentation.