sessions_spawn returns 'pairing required' after v2026.2.19 update
After updating from v2026.2.15 to v2026.2.19-2, sessions_spawn fails with:
gateway closed (1008): pairing required
The main agent session works fine (Discord messages, all tools). Only sessions_spawn is broken.
Gateway err.log shows:
security audit: device access upgrade requested reason=scope-upgrade device=39ae... scopesFrom=operator.admin,operator.approvals,operator.pairing scopesTo=operator.write
The gateway service is running (launchd, pid active). openclaw status shows everything OK. Discord channel is OK.
Setup: Mac mini, local gateway, bind=loopback, auth=token, Claude Max (anthropic:manual token auth).
Questions:
1. Is there a new pairing/device approval step required in 2.19?
2. How do we approve the scope upgrade from operator.pairing to operator.write?
3. Is there a CLI command or Control UI action needed?
Thanks!
gateway closed (1008): pairing required
The main agent session works fine (Discord messages, all tools). Only sessions_spawn is broken.
Gateway err.log shows:
security audit: device access upgrade requested reason=scope-upgrade device=39ae... scopesFrom=operator.admin,operator.approvals,operator.pairing scopesTo=operator.write
The gateway service is running (launchd, pid active). openclaw status shows everything OK. Discord channel is OK.
Setup: Mac mini, local gateway, bind=loopback, auth=token, Claude Max (anthropic:manual token auth).
Questions:
1. Is there a new pairing/device approval step required in 2.19?
2. How do we approve the scope upgrade from operator.pairing to operator.write?
3. Is there a CLI command or Control UI action needed?
Thanks!
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
