Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tempest CLI as an SSH Login Entry Point (Alpha)

Configure Tempest CLI as an interactive SSH login entry point and use a Linux server as a jump host, with separate Tempest data for each Unix user.

This feature is in Alpha. Use a CLI build that includes tempest repl.

Run Tempest CLI on a Linux server to give SSH users an interactive prompt for connecting to their saved servers. Each Unix user keeps their own accounts and vault under ~/.tempest.

1. Install the CLI on the server

Follow the CLI installation guide, then check the executable path and REPL:

command -v tempest
tempest repl

Type exit to leave. The examples below use /usr/bin/tempest; replace it with your executable's absolute path.

2. Set Tempest as the login shell

Create a user with a home directory and Tempest as its login shell:

sudo useradd -m -s /usr/bin/tempest tempest

Configure the user's SSH public key in /home/tempest/.ssh/authorized_keys. The .ssh directory should have mode 700, and authorized_keys should have mode 600, both owned by tempest.

For an existing user, change its login shell:

sudo usermod -s /usr/bin/tempest alice

Use a separate Unix account for each person to keep their Tempest data separate. No changes to sshd_config or SSH service reload are needed.

3. Connect and use Tempest

From your computer:

You will enter the Tempest prompt. On first use, sign in and unlock your vault:

Follow the browser authorization instructions printed by login. You can also connect directly:

When the target connection ends, you return to tempest>. Type exit or press Ctrl+D to close the login session.

Per-user data

The example user's data lives under /home/tempest/.tempest. With separate Unix accounts, Alice's data lives under /home/alice/.tempest, while Bob's lives under /home/bob/.tempest. Vault directories are owner-only (700), and private files are created with mode 600. People sharing one Unix account also share its Tempest data.

This setup provides an interactive jump-host workflow using each user's normal Unix permissions. Users enter the Tempest prompt directly when they log in over SSH.

See also

Last updated