Move your identity to another machine
Goal: carry your tardigrada identity — and therefore every store it unlocks — to a new machine, or adopt a keyfile another tool already holds. export/import always move keyfile material: export reads from whichever backend is configured (the session keyring by default) and import writes to it. To switch where the identity lives on one machine, see Switch backends.
Prerequisites
tardigradainstalled on both machines.- A safe channel for the keyfile (encrypted volume, password manager,
scpover ssh — never email or chat).
Steps
On the source machine, write the keyfile out:
shtardigrada export --out ~/tardigrada-identity.txtVerify it was written mode
0600:shls -l ~/tardigrada-identity.txt # -rw-------Copy it to the destination machine.
On the destination, adopt it:
shtardigrada import ~/tardigrada-identity.txt tardigrada show # same age1… as the sourceimportoverwrites whatever identity the destination held — there is no undo, so be sure the source file is the right one.Clean up the copy when done:
shrm ~/tardigrada-identity.txt # on both machines
Pipeable variant
Bare export prints just the AGE-SECRET-KEY-… line — usable as a stream:
ssh newmachine 'cat > ~/identity.txt && chmod 600 ~/identity.txt' \
< <(tardigrada export)
# on the destination: tardigrada import ~/identity.txtThe stream holds just the AGE-SECRET-KEY-… line — import parses it fine (comments are optional).
Deeper link
- CLI reference — every flag and env var.
- Concepts — what the keyfile actually is.