Every command that talks to the device (except battery) needs an auth token.
The token is a 32-character hex string, unique to your device, captured once and stored permanently.
If you already have your token:
plaude auth set-token abcdef0123456789abcdef0123456789If you have an Android HCI snoop log containing a Plaud sync session:
plaude auth import /path/to/btsnoop_hci.logplaude auth show
# Token stored.
# Fingerprint: a82dcb11ff56d11dThe fingerprint is a SHA-256 hash — the raw token is never printed.
plaude auth clearThe bootstrap command makes your computer pretend to be a Plaud device. When the phone app connects and sends the token, we capture it.
- Your real Plaud device must be powered off or out of range
- The Plaud phone app must be installed on your phone
- Bluetooth must be enabled on both devices
- Turn off your real Plaud device (or move it far away)
- Run the bootstrap:
plaude auth bootstrap
- Open the Plaud app on your phone
- The app will find "PLAUD_NOTE" (your computer) and connect
- The token is captured and stored automatically:
Advertising as PLAUD_NOTE — open the Plaud app and pair with this device... Token captured. Fingerprint: a82dcb11ff56d11d - Turn your real device back on
Default wait is 120 seconds. Override with:
plaude auth bootstrap --timeout 60Tokens are stored in two places (first available wins):
- OS keyring — Linux Secret Service, macOS Keychain, Windows Credential Manager
- File fallback —
~/.config/plaude/token(mode 0600)
Override the file location with --config-dir:
plaude --config-dir /tmp/test auth show