3.2.0-beta.10). Features may change before the next stable release.Switch to stable →sync
ak secrets sync enable
Create a synced vault from this device's secrets
Use ak secrets sync enable for the operation described below. The command help records its arguments, effects, and options.
Command contract
Create a synced vault from this device's secrets
Synopsis
Create a synced vault from this device's secrets. You choose a vault password and receive a recovery key; keep both offline. Losing both, with no enrolled device left, makes the vault unrecoverable. Use ak secrets devices add instead if the account already syncs elsewhere. Needs an email sign-in (ak login), or an API-key sign-in whose key has vault sync turned on, and the keychain or file backend. An API-key sign-in creates the vault without a recovery bundle, password or kit, and warns on stderr (and in warnings with --json) until an email sign-in seals one with ak secrets sync rotate-recovery. --resume continues an enable that stopped, or turns sync back on after ak secrets sync disable. --accept-sealed lets this device apply the sealed writes a remote MCP client queued on the vault server (each one is written as this device's own signed record and audited); on a device that already syncs it only changes that setting, and --accept-sealed=false turns it off. A compromised vault server cannot read these writes but can forge one, so an agent may not turn --accept-sealed on; run it in a terminal you opened yourself. The setting is this device's own; an older AgentKit cannot read a config with it on, so turn it off before installing one here. An older AgentKit also refuses this version's sync state; see the secrets guide before going back.
Effects: Generates this device's keys and a vault key, stores them in the keystore, writes sync state under AgentKit home, uploads the encrypted vault, and shows the recovery kit once on the terminal (stderr), or writes it only to --recovery-kit-out with mode 0600.
Exit status: 0 success 1 the server refused (quota, unsupported protocol) 2 invalid invocation: no kit destination, short password, memory backend, or the store moved 4 sync is already enabled (and no --accept-sealed change was asked), a partial enable needs --resume, or the kit file exists 5 local storage failure 6 refused: an AI agent is turning --accept-sealed on 7 the file-backend passphrase is unavailable 10 --resume with nothing to resume 11 the vault server is unavailable or busy; retry 12 enabled, but something needs attention 13 integrity alarm; sync halted 14 not logged in, or the session cannot mint vault tokens
ak secrets sync enable [flags]Examples
ak secrets sync enable --recovery-kit-out ./vault-recovery-kit.txt
ak secrets sync enable --password-file - --recovery-kit-out ./kit.txt --json < password.txt
ak secrets sync enable --accept-sealedOptions
--accept-sealed Apply sealed writes queued by remote MCP clients on this device's sync cycles
--backend string Storage backend: keychain (default), file (age-encrypted vault), or memory (dev/test; values and its index are throwaway)
-h, --help help for enable
--json Emit machine-readable JSON (implies --no-interactive)
--no-interactive Disable interactive prompts (CI-safe)
--password-file string Read the vault password from this file, or - for stdin (default: prompt twice on the terminal)
-q, --quiet Suppress non-error output on stderr
--recovery-kit-out string Write the recovery kit only to this new file (mode 0600), not the terminal; required with --json or without a terminal
--resume Continue a stopped enable, or re-enable after disable
--unlock-with-recovery Open the file backend's vault with a recovery private key and set a new passphrase
-V, --verbose Extra diagnostic output on stderr (loses to --quiet)
-y, --yes Assume yes for all promptsSEE ALSO
- ak secrets sync - Sync secrets across your machines with end-to-end encryption (preview)