Why this is a good first issue
The CLI already has sotto setup (see crates/cli/src/main.rs: "Set up this device from the server using your Emergency Kit (run after `login`)"). The README Quick start shows `init` / `login` / `push` on one machine and never says how a second laptop gets the vault. That is a real hole: without setup, `login` on a new device is not enough.
Copy only. No CLI changes.
What to do
In README.md, after the Quick start block (after the team snippet is fine), add a short subsection, for example:
Another device
sotto login # same account as the first machine
sotto setup # unpack the Emergency Kit onto this device
sotto pull # download the ciphertext you already pushed
One or two sentences: you need the Emergency Kit printed by `sotto init`; without it a new device cannot decrypt. British English, no em dashes.
Do not document `sotto reset` here (that is the lost-kit path, and it is destructive).
Out of scope
Do not change setup/login behaviour. Do not add screenshots. Skip the landing page unless the extra lines still read as one transcript.
Why this is a good first issue
The CLI already has
sotto setup(seecrates/cli/src/main.rs: "Set up this device from the server using your Emergency Kit (run after `login`)"). The README Quick start shows `init` / `login` / `push` on one machine and never says how a second laptop gets the vault. That is a real hole: without setup, `login` on a new device is not enough.Copy only. No CLI changes.
What to do
In README.md, after the Quick start block (after the team snippet is fine), add a short subsection, for example:
Another device
One or two sentences: you need the Emergency Kit printed by `sotto init`; without it a new device cannot decrypt. British English, no em dashes.
Do not document `sotto reset` here (that is the lost-kit path, and it is destructive).
Out of scope
Do not change setup/login behaviour. Do not add screenshots. Skip the landing page unless the extra lines still read as one transcript.