Skip to main content

​
Node troubleshooting

Use this page when a node is visible in status but node tools fail. Start in the Control UI:
  1. Open Advanced > Nodes and confirm the node is paired, connected, and advertising the capability you are trying to use.
  2. Open Logs and filter for node, NODE_, camera, canvas, screen, location, or SYSTEM_RUN_DENIED.
  3. If an Agent cannot use an otherwise healthy node tool, check Agent > Tools for that selected Agent’s allow/deny policy.

​
Command ladder

Then run node specific checks:
Healthy signals:
  • Node is connected and paired for role node.
  • nodes describe includes the capability you are calling.
  • Exec approvals show expected mode/allowlist.
  • Advanced > Nodes shows matching capability and last-seen state.

​
Foreground requirements

canvas.*, camera.*, and screen.* are foreground only on iOS/Android nodes. Quick check and fix:
If you see NODE_BACKGROUND_UNAVAILABLE, bring the node app to the foreground and retry.

​
Permissions matrix

  • camera.snap, camera.clip
    • iOS/Android/macOS: Camera permission; microphone permission for clip audio.
    • Typical failure: *_PERMISSION_REQUIRED.
  • screen.record
    • iOS/macOS: Screen Recording permission.
    • Android: screen capture prompt; microphone permission if audio is included.
    • Typical failure: *_PERMISSION_REQUIRED.
  • location.get
    • iOS/macOS: While Using or Always, depending on requested mode.
    • Android: foreground/background location, depending on requested mode.
    • Typical failure: LOCATION_PERMISSION_REQUIRED.
  • system.run
    • Uses the node host path and exec approvals.
    • Typical failure: SYSTEM_RUN_DENIED.

​
Pairing versus approvals

These are different gates:
  1. Device pairing: can this node connect to the gateway?
  2. Exec approvals: can this node run a specific shell command?
Quick checks:
If pairing is missing, approve the node device first. If pairing is fine but system.run fails, fix exec approvals/allowlist. If both are fine but the Agent still cannot use the tool, fix Agent > Tools for that Agent.

​
Common node error codes

  • NODE_BACKGROUND_UNAVAILABLE → app is backgrounded; bring it foreground.
  • CAMERA_DISABLED → camera toggle disabled in node settings.
  • *_PERMISSION_REQUIRED → OS permission missing/denied.
  • LOCATION_DISABLED → location mode is off.
  • LOCATION_PERMISSION_REQUIRED → requested location mode not granted.
  • LOCATION_BACKGROUND_UNAVAILABLE → app is backgrounded but only While Using permission exists.
  • SYSTEM_RUN_DENIED: approval required → exec request needs explicit approval.
  • SYSTEM_RUN_DENIED: allowlist miss → command blocked by allowlist mode. On Windows node hosts, shell-wrapper forms like cmd.exe /c ... are treated as allowlist misses in allowlist mode unless approved via ask flow.

​
Fast recovery loop

If still stuck:
  • Re-approve device pairing.
  • Re-open node app (foreground).
  • Re-grant OS permissions.
  • Recreate/adjust exec approval policy.
Related: