Switch identity backends
Goal: move between the session keyring and the keyfile — or pick the right backend for a headless box — without losing the identity.
Prerequisites
tardigradainstalled;tardigrada backendshows the current resolved backend.
The modes
TARDIGRADA_IDENTITY_BACKEND selects the store:
| Value | Behavior |
|---|---|
keyring (default) | Platform session secret store, entry tardigrada/age-identity. Fail closed — no reachable store is an error. |
auto | Keyring when reachable, keyfile fallback with a stderr note. |
file | Keyfile only; the store is never probed. |
An explicit --identity-file/TARDIGRADA_IDENTITY_FILE pin always means file and wins over every mode.
Steps
Check where the identity lives today:
shtardigrada backend # keyring — or file + the resolved keyfile pathTo move a keyfile identity into the keyring: just run
tardigrada init(or setTARDIGRADA_IDENTITY_BACKEND=autoand run any verb). Underkeyring/auto,initadopts the keyfile's identity into the store — the file stays as a backup, nothing is orphaned. Verify:shtardigrada backend # → keyring tardigrada show # same age1… as beforeTo move a keyring identity to a keyfile (another machine, a headless box):
shtardigrada export --out ~/.config/tardigrada/identity.txtthen on the target,
tardigrada import <path>— or setTARDIGRADA_IDENTITY_BACKEND=fileand let thefilebackend read the keyfile directly.For headless/CI, opt out of the keyring probe entirely:
shexport TARDIGRADA_IDENTITY_BACKEND=auto # or =fileautostill uses the keyring when a session store exists;filenever probes.
You should see
tardigrada backendprints the resolved backend;--jsonaddsmode(the configured selection) andpinned.tardigrada showprints the sameage1…recipient before and after a backend switch — the identity moved, it didn't change.
Deeper link
- Environment variables — every var and the resolution order.
- Decisions — why keyring is the fail-closed default.