coderClaw

Node troubleshooting

Use this page when a node is visible in status but node tools fail.

Command ladder

coderclaw status
coderclaw gateway status
coderclaw logs --follow
coderclaw doctor
coderclaw channels status --probe

Then run node specific checks:

coderclaw nodes status
coderclaw nodes describe --node <idOrNameOrIp>
coderclaw approvals get --node <idOrNameOrIp>

Healthy signals:

Foreground requirements

canvas.*, camera.*, and screen.* are foreground only on iOS/Android nodes.

Quick check and fix:

coderclaw nodes describe --node <idOrNameOrIp>
coderclaw nodes canvas snapshot --node <idOrNameOrIp>
coderclaw logs --follow

If you see NODE_BACKGROUND_UNAVAILABLE, bring the node app to the foreground and retry.

Permissions matrix

Capability iOS Android macOS node app Typical failure code
camera.snap, camera.clip Camera (+ mic for clip audio) Camera (+ mic for clip audio) Camera (+ mic for clip audio) *_PERMISSION_REQUIRED
screen.record Screen Recording (+ mic optional) Screen capture prompt (+ mic optional) Screen Recording *_PERMISSION_REQUIRED
location.get While Using or Always (depends on mode) Foreground/Background location based on mode Location permission LOCATION_PERMISSION_REQUIRED
system.run n/a (node host path) n/a (node host path) Exec approvals required 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:

coderclaw devices list
coderclaw nodes status
coderclaw approvals get --node <idOrNameOrIp>
coderclaw approvals allowlist add --node <idOrNameOrIp> "/usr/bin/uname"

If pairing is missing, approve the node device first. If pairing is fine but system.run fails, fix exec approvals/allowlist.

Common node error codes

Fast recovery loop

coderclaw nodes status
coderclaw nodes describe --node <idOrNameOrIp>
coderclaw approvals get --node <idOrNameOrIp>
coderclaw logs --follow

If still stuck:

Related: