ssh-cli

• Historical note: 0.4.2 closed TUN-003 / IO-010; 0.5.0 was the EN/API rename + secrets force-init reencrypt; current product line is 0.5.2 (export/import agent roundtrip, wire schema v3 dual-read, secrets CLI flags, tunnel --bind).

Give any LLM remote SSH power in one memory-safe one-shot binary.

• Read this document in Portuguese (pt-BR).
• Install with cargo install ssh-cli --locked for a lockfile-aligned graph.
• Upgrade with cargo install ssh-cli --locked --force.
• Verify with ssh-cli --version.
• Read full history in CHANGELOG.md.
• Integrate agents via docs/AGENTS.md and INTEGRATIONS.md.
• Follow first use in docs/HOW_TO_USE.md.
• Copy recipes from docs/COOKBOOK.md.
• Check platforms in docs/CROSS_PLATFORM.md.
• Migrate from 0.3.3+ in docs/MIGRATION.md (target line 0.5.2).
• Run tests via docs/TESTING.md.
• Consume JSON contracts under docs/schemas/README.md.
• Teach LLMs with skills/ssh-cli-en/SKILL.md.

What is it?

One-shot multi-host SSH CLI for agents

• Ship a single Rust binary with zero Node runtime and zero daemon.
• Operate N VPS hosts from XDG storage without .env files.
• Authenticate with password or private key per host.
• Execute exec, sudo-exec, and su-exec as pure one-shot processes.
• Capture stdout and stderr with structured JSON for orchestration.
• Auto-detect locale between en-US and pt-BR.
• Disable telemetry completely in every build.

Why ssh-cli?

Replace long-lived SSH processes with a die-after-run binary

• Avoid resident Node processes that hold sockets open between tasks.
• Cut RAM and CPU waste from long-lived SSH sessions.
• Register multi-host credentials once under XDG with atomic writes.
• Align command packing and dual maxChars semantics with the one-shot agent contract.
• Trust host keys via TOFU known_hosts instead of always-trust.
• Route errors with sysexits codes that agents classify reliably.

Superpowers

Capabilities that make agents productive

• Multi-host CRUD with vps add|list|show|edit|remove|path|doctor|export|import
• One-shot remote execution with exec, sudo-exec, su-exec
• Safe sudo packing via sh -c and shell escape
• Private key auth with optional passphrase
• Dual limits max_command_chars and max_output_chars
• Timeout with best-effort remote abort
• Bounded tunnel via mandatory --timeout-ms; optional --bind (default 127.0.0.1)
• Wire schema v3: serialize English TOML keys; dual-read EN + legacy PT aliases on load
• vps export body is TOML by default (TTY and pipe); agent JSON envelope only with --json; redacted by default; empty secrets stay ""; non-empty redacted secrets mask as *** (FIXED_MASK); --include-secrets to pipe/non-TTY needs -o/--output or --i-understand-secrets-on-stdout
• vps import accepts TOML (EN keys + PT aliases) or JSON vps-export envelopes; redacted skeletons need --allow-incomplete
• SCP upload and download of regular files only (no recursive directories on SCP; first solid wire fix in 0.4.0; prefer 0.5.2+ — avoid crates.io 0.3.9 SCP)
• SFTP subsystem (ssh-cli sftp): upload/download (optional --recursive trees, symlink no-follow), ls/mkdir/rmdir/rm/stat/rename; JSON events sftp-transfer / sftp-list / sftp-fs-op / sftp-batch
• SCP flag parity with exec: --timeout, --password-stdin, --key, --key-passphrase / --key-passphrase-stdin, --json (contract docs/schemas/scp-transfer.schema.json)
• SCP download writes {path}.ssh-cli.partial then atomic rename; preserve remote mtime/mode bi-directional; upload streams 32 KiB chunks
• SCP JSON success requires event: "scp-transfer" (0.4.1 IO-009); missing remote → file not found: <path> exit 66
• tunnel --json emits structured tunnel_listening after local bind
• Tunnel post-bind deadline exits 0 after tunnel_listening (pre-bind timeout still 74) (0.4.1 TUN-002)
• Tunnel and health-check auth parity with exec/scp: --password-stdin, --key, --key-passphrase / --key-passphrase-stdin as applicable (0.4.1 CLI-005/006)
• Redacted vps export never emits sshcli-enc: for empty password — empty secrets serialize as empty strings (0.4.1 EXP-001)
• Health-check latency probe with optional --timeout
• Shell completions for bash zsh fish powershell
• Secrets via stdin flags to avoid argv leaks
• Default at-rest encryption (ChaCha20-Poly1305) with auto XDG secrets.key; CLI flags --allow-plaintext-secrets, --secrets-key-file, --use-keyring preferred over env
• Master-key UX: secrets status|init|reencrypt with --json events secrets-init / secrets-reencrypt; first secret write folds secrets_key_auto_created: true into the same vps-added JSON (one document)
• TOFU known_hosts and atomic config writes with flock
• Key-only hosts: empty password serializes as JSON null (not "***") in vps list / show
• Default tracing filter is error (agent-first clean stderr); use -v for debug (ambient RUST_LOG is ignored)
• Install with russh 0.62.2 for clean cargo install --locked

Quick Start

Install and run the first remote command

cargo install ssh-cli --locked
ssh-cli secrets init   # optional explicit master-key; auto-created on first secret write
printf %s 'demo-password-not-real' | ssh-cli vps add \
  --name prod \
  --host prod.example.com \
  --port 22 \
  --user admin \
  --password-stdin
ssh-cli connect prod
ssh-cli exec prod "hostname" --json

Installation

Choose the install path that matches your environment

• Prefer crates.io with lockfile: cargo install ssh-cli --locked (0.5.2+ on crates.io; avoid 0.3.9 for SCP).
• Rebuild from a checkout: cargo install --path . --locked
• Do not use install without --locked unless you verified the crypto pins resolve cleanly.
• Force upgrade after a release: cargo install ssh-cli --locked --force
• Build musl with allocator feature when targeting Alpine: --features musl-allocator
• Require Rust MSRV 1.85.0 or newer

Features

Cargo feature flags

• Install path always enables defaults (ssh-real + tls).
• Disable real SSH / TLS only for dependency diagnosis: cargo build --no-default-features.
• docs.rs builds with all-features = true and --cfg docsrs (see Cargo.toml [package.metadata.docs.rs]).

Crypto policy (G-TLS)

• Default transport is SSH-2 on plain TCP (russh + aws-lc-rs). Host keys use TOFU under XDG (known_hosts).
• Optional SSH-over-TLS (vps add --tls, record fields tls / tls_sni / mTLS paths): rustls handshake then SSH on the TLS stream. Binary installs CryptoProvider (aws_lc_rs) once in main.
• mTLS / ACME: ssh-cli tls mtls … and ssh-cli tls acme … store material under XDG tls/ (no product env for cert storage).
• No OpenSSL / native-tls / dual ring provider. SSH channel compression forced to none.
• ACME validation / invalidContact / 4xx problem types → exit 64 non-retryable (G-E2E-01); rate limits remain transient exit 74.
• Details: SECURITY.md.

Targets

Platforms covered by docs.rs metadata

• x86_64-unknown-linux-gnu (default)
• x86_64-apple-darwin, aarch64-apple-darwin
• x86_64-pc-windows-msvc
• aarch64-unknown-linux-musl
• See docs/CROSS_PLATFORM.md for runtime notes.

Usage

Register hosts then execute one-shot commands

• Default at-rest encryption (ChaCha20-Poly1305): auto secrets.key on first secret write; prefer CLI flags --secrets-key-file, --use-keyring, --allow-plaintext-secrets (or XDG secrets.key); manage with ssh-cli secrets status|init|reencrypt. SSH_CLI_SECRETS_KEY / SSH_CLI_SECRETS_KEY_FILE are rejected fail-closed (not a store). Opt-out for tests only via --allow-plaintext-secrets.
• Prefer --password-stdin / --key over argv secrets.
• Add password hosts with vps add --password or --password-stdin.
• Add key hosts with vps add --key ~/.ssh/id_ed25519.
• On key-only hosts, empty password fields serialize as JSON null in vps list / show (non-empty secrets mask as "***").
• Mark active host with connect <name>.
• Run remote shells with exec <vps> "<cmd>".
• Elevate with sudo-exec or su-exec when configured.
• Diagnose XDG paths with doctor --json (or vps doctor --json).
• Discover contracts with ssh-cli schema / ssh-cli commands.
• Export redacted inventory with vps export (TOML default; --json for agent envelope).

Commands

Product surface for humans and agents

Configuration (CLI-only product store)

Product knobs are flags and XDG — not SSH_CLI_* env stores

Fail-closed secrets env (not a store)

OS / host boundary (detection only — not product config store)

• Default tracing filter is error so agent stderr stays clean; pass -v for debug (ambient RUST_LOG is ignored).
• Never put host passwords in environment variables; use registry + stdin.
• Product does not read SSH_CLI_HOME, SSH_CLI_LANG, SSH_CLI_FORCE_TEXT, or SSH_CLI_MAX_CONCURRENCY as config stores.

Integration Patterns

Wire agents with one-shot subprocesses only

• Invoke ssh-cli as a subprocess with explicit argv.
• Prefer --json or --output-format json for machine parsing.
• Parse stdout only; default log level is error so stderr stays silent for JSON pipelines — pass -v when diagnosing (ambient RUST_LOG is ignored).
• Map non-zero exits with sysexits semantics before retry.
• Store hosts once via vps add then call exec per task.
• Pass secrets through --password-stdin when argv history is risky.
• Read INTEGRATIONS.md for agent-specific notes.

Exit Codes

Sysexits-style codes agents must map before retry

• Prefer --json or auto JSON when stdout is not a TTY (--output-format overrides).
• Default tracing is error, so exit handling and JSON stdout stay free of INFO noise; use -v only when diagnosing (ambient RUST_LOG is ignored).
• Retry only on transient IO/timeout (74), never on auth (77) or usage (64).

Performance

Cold start and memory goals

• Target cold start under 100 ms on modern Linux hosts.
• Keep process memory far below a resident long-lived Node SSH process.
• Die after each command so RAM returns to the OS immediately.
• Avoid long-lived tunnels without --timeout-ms.

Memory Requirements

Plan capacity for multi-host registries

• Config TOML size grows with host count and path lengths.
• Output buffers respect max_output_chars per stream.
• Known_hosts file grows slowly with unique host:port pairs.
• No embedding model and no Node heap are required.

Troubleshooting FAQ

Fix common install and runtime failures

• Install fails on crypto RC drift: rerun with --locked or use release 0.5.2+ (russh 0.62.2) (scripts/verify_install_resolve.sh).
• Auth fails on key-only hosts: set --key on vps add or pass --key / --password-stdin to exec (rejected auth exits 77).
• Auth fails with passphrase keys: use --key-passphrase-stdin (exit 77 on reject).
• Host key changed: confirm legitimacy then rerun with --replace-host-key.
• Command rejected as too long: raise max_command_chars or shorten the command.
• Config has encrypted secrets but no key: run ssh-cli secrets init or restore secrets.key / env master-key / --secrets-key-file.
• sudo-exec disabled: remove --disable-sudo and set disable_sudo=false on the host.
• Unexpected stderr noise in JSON pipelines: default log level is already error; pass -v when diagnosing (ambient RUST_LOG is ignored).
• SCP from crates.io 0.3.9 fails or writes 0-byte remotes: upgrade to 0.5.2+ (wire fix since 0.4.0); only regular files, not directories.
• SCP remote missing: message is file not found: <path> and exit 66 (prefer 0.5.2+; 0.4.2 IO-010).
• SCP download fails mid-transfer: destination stays absent or previous file intact (partial uses .ssh-cli.partial).
• Redacted vps export on 0.4.0 wrote fake sshcli-enc: blobs for empty secrets: upgrade to 0.5.2+ (empty secrets stay empty strings since 0.4.1).
• Tunnel emitted ok: true / tunnel_listening then process exit 74 when the post-bind deadline hit on 0.4.0: upgrade to 0.5.2+ (post-bind deadline exits 0 since 0.4.1; pre-bind timeout still 74).
• Import bad TOML: parse errors map to exit 65 (TomlDe / data error).
• Import redacted skeleton without secrets: pass --allow-incomplete.
• macOS Gatekeeper blocks binary: run xattr -d com.apple.quarantine /path/to/ssh-cli.
• Permission denied on config: ensure chmod 600 on the XDG config.toml and secrets.key.

Contributing

• Read CONTRIBUTING.md before opening a pull request.
• Follow the bilingual documentation framework for every public doc change.

Security

• Read SECURITY.md for private vulnerability reporting.
• Prefer stdin secret flags and key files over argv passwords.

Changelog

• Read version history in CHANGELOG.md.
• Do not paste release notes into this README.

License

• Dual-licensed under MIT or Apache-2.0.
• See LICENSE, LICENSE-MIT, and LICENSE-APACHE.