Konsolity CLI security
Can a token copied to another machine be used?
No. Every call sends the machine fingerprint, computed from the system identifier. A token used from another computer is refused, the event is written to the security log and you receive an alert. The local secret file is also encrypted with a key derived from the machine identifier: copied elsewhere, it is unreadable.
The only exception: the long-lived token of konsolity setup-token, made for ephemeral machines, is not bound to the fingerprint. Store it in your CI secret manager, give it the narrowest possible scope and a short expiry.
What is the fingerprint shown on activation for?
It proves that the request you approve really comes from the machine in front of you. It is computed from the public key of the machine; your device computes it again itself, without trusting the server. If the two fingerprints differ, refuse.
What does the Konsolity server see?
The server sees the name of the machine, its system, its IP address, its scope (domains, read-only or full), its sessions and the command log (command text, host, decision, exit code, duration). For the Claude connector (konsolity serve), it also carries, encrypted at rest and deleted one hour after the answer, the arguments and results of Claude's calls, as for the Claude connector.
It never sees the key of your vault, the machine key, your SSH keys, your passwords or the rules of the machine: the copies of the machine vault are end-to-end encrypted, and the server only stores them as opaque blobs. The output of commands run in a terminal does not go through the server.
Does the machine have access to my whole vault?
No. It never receives the vault key, only a machine key and encrypted copies of the hosts and snippets you chose. A host outside the scope has no copy: its SSH key does not leave your vault. The machine can neither write to the vault, nor change its own scope, nor touch your account or your subscription.
What happens if the machine is compromised?
Someone who takes full control of the machine can use what it received: the hosts and SSH keys of its scope, within its rules. Destructive commands still need your confirmation. In that case:
- Revoke the machine (Settings › CLI machines): it is cut off in less than 5 seconds and the server deletes the copies of its machine vault.
- Change the SSH keys of the hosts it could reach.
- Go through its command log.
- If the doubt is about the account, change your password while signing out the other devices: every CLI machine is revoked.
To reduce the risk from the start: the narrowest possible scope, read-only when it is enough, snippets rather than free commands, no "Any command", a short expiry, a dedicated and up to date machine.
How fast does a revocation take effect?
In less than 5 seconds. Every running command signals its presence to the server every 2 seconds; on revocation, the next signal is refused, the CLI cuts the SSH connections, stops the command, erases its secrets and exits with code 77.
I lost my phone: what should I do?
Your CLI machines do not depend on your phone: they keep working. From another device or from app.konsolity.com:
- Revoke the phone in the list of devices.
- If the phone held your TOTP app or your passkey, use a recovery code, then register a new second factor in Security.
- If in doubt, revoke the CLI machines too (Revoke all) and activate again the ones you need.
Without the second factor, nobody can approve a new machine or widen the scope of an existing machine, even with your phone unlocked.
Why a second factor to approve?
Because a CLI machine can act on your servers with nobody in front of it. The TOTP code or the passkey is checked in the same request as the approval: a browser session left open or an intercepted activation code is not enough. It is also asked to widen a scope; narrowing it asks for nothing.
What is the difference with the app?
| Desktop app | Konsolity CLI | |
|---|---|---|
| Interface | Graphical | Command line |
| Vault access | Whole vault | Only the chosen hosts and snippets |
| Must stay open | Yes | No, konsolity serve as a service |
| Approval of a Claude command | "Allow once", or always allow | Scope and rules, confirmation for destructive commands |
| Interactive terminal, files | Yes | No |
| Systems | macOS, Windows, Linux, iOS, Android | Linux, macOS, Windows |
Not to be confused with the remote terminal relay, an internal service that carries encrypted SSH bytes between your devices.
Which plan is needed?
The Studio plan, or its free trial. The server checks the plan on every call of the machine; the machine list and revocation always stay available. konsolity serve also uses the Claude connector, included in Studio.