Standalone SSH binary
Use `cmdok ssh` without Node.js/npm. First run asks for API key and machine.
cmdok ssh
API key prompt -> saved config
host picker opens
Product / SSH (cmdok)
Standalone SSH, exec, and agent
The `cmdok` binary is a single install for terminal access — no Node at runtime. It complements the full Go `cmdop` CLI and the Python SDK; the docs explain when to use each.
Install cmdok (standalone binary)
cmdok CLI documentationSSH Session
Policy checked
$ cmdop ssh prod-eu-web-01
Connected to prod-eu-web-01
workspace policy: team-prod-access
deploy@prod-eu-web-01:~$ tail -n 50 /var/log/app.log
[warn] timeout on upstream payment-api
[info] retry success in 120ms
SSH + team safety
SSH sessions
14 today
Access checks
100%
History
saved
How cmdok behaves
API key resolution
Credential lookup is deterministic across flag, env, config, and interactive prompt.
--api-key
CMDOP_API_KEY
~/.config/cmdok/config.json
Recent host history
When hostname is omitted, `cmdok` shows recent targets for fast reconnect.
my-server (last used)
prod-01
staging
Remote access in three steps
Step 1
Install quickly
Use install script on macOS/Linux/Windows or download from GitHub Releases.
Step 2
Connect with `cmdok ssh`
Resolve API key, choose host, and start interactive remote session.
Step 3
Run adjacent ops
Use `cmdok exec` and `cmdok agent` for command and AI workflows.
Why teams standardize on cmdok
SSH session workflow
Interactive remote control with familiar terminal behavior and machine selection.
cmdok ssh <hostname>
interactive TTY
reconnect by recent host
Companion commands
Use the same binary for remote command execution and AI-assisted operations.
cmdok exec <host> <command>
cmdok agent <host> <prompt>
cmdok config
Operational defaults
Timeouts, debug mode, and server override are built-in for production usage.
--timeout 60
--debug
--server <grpc-addr>
Install once, connect everywhere
Use the same binary for interactive SSH, one-off exec, and AI agent tasks against registered machines.