Summary

On OpenClaw 2026.4.15, openclaw devices approve --latest is preview-only and exits non-zero instead of approving the latest pending request, but the public docs still say it auto-approves when requestId is omitted or --latest is passed.

This creates a real operator trap during device pairing because the documented recovery flow says openclaw devices approve --latest, while the CLI actually requires a second explicit openclaw devices approve <requestId> command.

Version

• OpenClaw CLI: 2026.4.15

What I observed

CLI help / implementation

openclaw devices approve --help says:

• --latest Show the most recent pending request to approve explicitly

Bundled implementation also appears preview-only:

• dist/devices-cli-NyHAbrN-.js:307
• exits after returning selected + approveCommand when implicit selection / --latest is used

Changelog confirms this was intentional:

• CHANGELOG.md:466
• CLI/devices: make implicit openclaw devices approve selection preview-only and require approving the exact request ID, preventing latest-request races during device pairing. (#64160)

Docs still describe auto-approve

The current docs page says:

• https://docs.openclaw.ai/zh-CN/cli/devices
• "If requestId is omitted, OpenClaw will automatically approve the most recent pending request."
• and lists openclaw devices approve --latest

Additional stale guidance in bundled skill docs

Bundled skill docs still recommend:

• skills/node-connect/SKILL.md:107
• openclaw devices approve --latest

Repro

1. Create a pending device pairing request
2. Run:

   openclaw devices approve --latest --json

3. Observe output similar to:
   • selected
   • approveCommand
   • process exits with code 1
4. Then run:

   openclaw devices approve <requestId> --json

5. Observe that the explicit request ID command actually approves the device

Expected

One of these should be made consistent:

1. If the intended behavior is preview-only, update:

   • public docs
   • bundled skill docs / pairing guidance
   • any recovery text that suggests approve --latest is sufficient

2. If the intended behavior is auto-approve, restore that behavior in CLI

Why this matters

This showed up in a real device pairing flow. The user hit pairing required, I checked the latest request, and --latest looked like it should approve based on docs, but it only selected the request. Pairing only succeeded after running the explicit request-id approve command.