Persistent device token mismatch — how to force CLI re-pair with gateway?
Persistent device token mismatch on 2026.2.19-2. Survives: gateway stop/start, gateway install, doctor –fix, deleting paired.json, deleting pending.json, deleting all token files. No keychain entry found. Gateway runs fine (Telegram works), only CLI RPC fails. Gateway auth.token is set to ‘auto’ in config. How do I force the CLI to re-pair with a fresh token?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
