Cloud continuity
Off by default, on in a minute. With sync enabled, every live session mirrors end-to-end encrypted to Termuna Cloud, and the session follows you to any browser or phone.
Turning it on
Open the sessions area, find the Termuna Cloud section, and sign in or
create an account. The app registers this machine and live sessions start
syncing. The sign-in writes the [cloud] section of
config.toml for you; nothing about the
setup is hidden.
Continuity and device sync are part of the Solo and Team plans; the Free tier is the complete local terminal (plans).
What mirrors, and how
- Every output and input frame, sealed with XChaCha20-Poly1305 on your machine before it touches the network. The relay stores ciphertext it cannot read.
- The session layout - tabs, splits, working directories - so a viewer joining late draws the right picture immediately.
- Full scrollback history, which is what survives a reboot: processes die with the machine, the workspace and history do not (the honest version).
When a synced session needs you - a bell, or an agent waiting on a question - the relay can push a notification to your browser (how that works).
Devices and tokens
Each machine's daemon connects with a device token, stored only as a hash on the server. Revoke any device from the dashboard's devices page and its daemon immediately loses cloud access, while the local terminal on that machine keeps working.
Share links
Every synced session gets a share link; the decryption key rides in the
link's #fragment, which browsers never send to the server.
The link is also written next to the session file in
~/.local/share/termuna/sessions/ as
<id>.cloudurl, so scripts can find it. Anyone with the
link sees the session; the relay never can.
Your keys, your passphrase
Session keys are generated on your devices and reach your other devices through your encrypted vault, unlocked by an encryption passphrase that never leaves your machines. Your snippets are items in that same vault, so they sync with your hosts, sealed the same way, with no change to the protocol. Losing the passphrase does not mean losing history: a recovery kit is generated when you set it - store it offline (the full encryption path).