-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
Gateway diagnostics should surface pending node approval IDs and exact approve command #98045
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.Issue affects a taxonomy feature currently scored M4/M5.no-staleExclude from stale automationExclude from stale automation
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.Issue affects a taxonomy feature currently scored M4/M5.no-staleExclude from stale automationExclude from stale automation
Type
Fields
Priority
None yet
Summary
When an Android node is connected but waiting for node reapproval, the required approval target is an internal node UUID. That ID is not visible in the Android app and is not shown by the device-oriented CLI path, so a user has no clear way to know what to approve.
What happened
During Android reconnection, the app showed an authentication/approval state. The visible phone IP was
192.168.0.202, andopenclaw devices listshowed the paired device. Running:was the natural guess, but it was the wrong layer. The actual fix was:
The node UUID did not appear in the app or in the device list, so the user could not have discovered it from the visible information.
Expected behavior
Gateway diagnostics and/or the failed approval path should surface the exact pending node approval and command, for example:
Useful places to show this:
openclaw gateway diagnostic/ Android gateway diagnostic outputopenclaw devices listwhen a paired device has an associated node approval pendingopenclaw devices approve <ip>error output, if the IP matches a node connectionActual behavior
The user saw an app-side authentication-needed state and a device/IP in CLI output, but the required
nodes approve <uuid>command was only discoverable if the user already knew to runopenclaw nodes pendingoropenclaw nodes status.Why this matters
The
devicesandnodesapproval layers are easy to confuse during Android setup because the same physical phone appears as both a device and a node. The CLI should guide users from the wrong-but-obvious command to the right command.Related
Possibly adjacent to #91126 and #98038, but this report is specifically about user-facing discoverability and diagnostics for pending node approval IDs.