Troubleshooting

This is the deep runbook. Start at /help/troubleshooting for the fast triage flow first.

Command ladder

Run in this order:

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

Healthy signals:

• remoteclaw gateway status shows Runtime: running, Connectivity probe: ok, and a Capability: ... line.
• remoteclaw doctor reports no blocking config/service issues.
• remoteclaw channels status --probe shows live per-account transport status and, where supported, works or audit ok.

After an update

Use when an update finishes but the Gateway is down, channels are empty, or model calls fail with 401s.

remoteclaw status --all
remoteclaw update status --json
remoteclaw gateway status --deep
remoteclaw doctor --fix
remoteclaw gateway restart

Look for:

• Update restart in remoteclaw status / remoteclaw status --all. Pending or failed handoffs include the next command to run.
• plugin load failed: dependency tree corrupted; run remoteclaw doctor --fix under Channels: the channel config still exists, but plugin registration failed before the channel could load.
• Provider 401s after re-auth: remoteclaw doctor --fix checks for stale per-agent OAuth auth shadows and removes old copies so all agents resolve the current shared profile.

Split brain installs and newer config guard

Use when a gateway service unexpectedly stops after an update, or logs show one remoteclaw binary is older than the version that last wrote remoteclaw.json.

RemoteClaw stamps config writes with meta.lastTouchedVersion. Read-only commands can inspect a config written by a newer RemoteClaw, but process and service mutations refuse to run from an older binary. Blocked actions: gateway service start/stop/restart/uninstall, forced service reinstall, service-mode gateway startup, and gateway --force port cleanup.

which remoteclaw
remoteclaw --version
remoteclaw gateway status --deep
remoteclaw config get meta.lastTouchedVersion

Fix `PATH` so `remoteclaw` resolves to the newer install, then rerun the action. Reinstall the intended gateway service from the newer install:

```bash
remoteclaw gateway install --force
remoteclaw gateway restart
```

Remove stale system package or old wrapper entries that still point at an old `remoteclaw` binary. For intentional downgrade or emergency recovery only, set `REMOTECLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1` for the single command. Leave it unset for normal operation.

Protocol mismatch after rollback

Use when logs keep printing protocol mismatch after a downgrade or rollback. An older Gateway is running, but a newer local client process is still reconnecting with a protocol range the older Gateway cannot speak.

remoteclaw --version
which -a remoteclaw
remoteclaw gateway status --deep
remoteclaw doctor --deep
remoteclaw logs --follow

Look for:

• protocol mismatch ... client=... v<version> min=<n> max=<n> expected=<n> in Gateway logs.
• Established clients: in remoteclaw gateway status --deep or Gateway clients in remoteclaw doctor --deep: active TCP clients connected to the Gateway port, with PIDs and command lines when the OS allows it.
• A client process whose command line points at the newer RemoteClaw install or wrapper you rolled back from.

Fix:

1. Stop or restart the stale RemoteClaw client process shown by gateway status --deep.
2. Restart apps or wrappers that embed RemoteClaw: local dashboards, editors, app-server helpers, or long-running remoteclaw logs --follow shells.
3. Re-run remoteclaw gateway status --deep or remoteclaw doctor --deep and confirm the stale client PID is gone.

Do not make an older Gateway accept a newer incompatible protocol. Protocol bumps protect the wire contract; rollback recovery is a process/version cleanup problem.

Skill symlink skipped as path escape

Use when logs include:

Skipping escaped skill path outside its configured root: ... reason=symlink-escape

Every skill root is a containment boundary. A symlink under ~/.agents/skills, <workspace>/.agents/skills, <workspace>/skills, or ~/.remoteclaw/skills is skipped when its real target resolves outside that root, unless the target is explicitly trusted.

Inspect the link:

ls -l ~/.agents/skills/<name>
realpath ~/.agents/skills/<name>
remoteclaw config get skills.load

If the target is intentional, configure both the direct skill root and the allowed symlink target:

{
  skills: {
    load: {
      extraDirs: ["~/Projects/manager/skills"],
      allowSymlinkTargets: ["~/Projects/manager/skills"],
    },
  },
}

Then start a new session or wait for the skills watcher to refresh. Restart the gateway if the running process predates the config change.

Do not use broad targets such as ~, /, or a whole synced project folder. Keep allowSymlinkTargets scoped to the real skill root that contains trusted SKILL.md directories.

If Skill Workshop apply should also write through those trusted symlinked workspace skill paths, enable skills.workshop.allowSymlinkTargetWrites. Keep it disabled for read-only shared skill roots.

Related:

• Skills config
• Configuration examples

Anthropic 429 extra usage required for long context

Use when logs/errors include: HTTP 429: rate_limit_error: Extra usage is required for long context requests.

remoteclaw logs --follow
remoteclaw models status
remoteclaw config get agents.defaults.models

Look for:

• Selected Anthropic model is a GA-capable 1M Claude 4.x model (Opus 4.6/4.7/4.8, Sonnet 4.6), or the model config still carries legacy params.context1m: true.
• Current Anthropic credential is not eligible for long-context usage.
• Requests fail only on long sessions/model runs that need the 1M context path.

Fix options:

Switch to a standard-window model, or remove legacy `context1m` from older model config that is not GA-capable for 1M context. Use an Anthropic credential that is eligible for long-context requests, or switch to an Anthropic API key. Configure fallback models so runs continue when Anthropic long-context requests are rejected.

Related:

• Anthropic
• Token use and costs
• Why am I seeing HTTP 429 from Anthropic?

Upstream 403 blocked responses

Use when an upstream LLM provider returns a generic 403 such as Your request was blocked.

Do not assume this is always an RemoteClaw configuration issue. The response can come from an upstream security layer such as a CDN, WAF, bot-management rule, or reverse proxy in front of an OpenAI-compatible endpoint.

remoteclaw status
remoteclaw gateway status
remoteclaw logs --follow

Look for:

• Multiple models under the same provider failing the same way.
• HTML or generic security text instead of a normal provider API error.
• Provider-side security events for the same request time.
• A tiny direct curl probe succeeding while normal SDK-shaped requests fail.

Fix the provider-side filtering first when evidence points to a WAF/CDN block. Prefer a narrowly scoped allow or skip rule for the API path RemoteClaw uses, and avoid disabling protection for the whole site.

A successful minimal `curl` does not guarantee that real SDK-style requests will pass through the same upstream security layer.

Related:

• OpenAI-compatible endpoints
• Provider configuration
• Logs

Local OpenAI-compatible backend passes direct probes but agent runs fail

Use when:

• curl ... /v1/models works.
• Tiny direct /v1/chat/completions calls work.
• RemoteClaw model runs fail only on normal agent turns.

curl http://127.0.0.1:1234/v1/models
curl http://127.0.0.1:1234/v1/chat/completions \
  -H 'content-type: application/json' \
  -d '{"model":"<id>","messages":[{"role":"user","content":"hi"}],"stream":false}'
remoteclaw infer model run --model <provider/model> --prompt "hi" --json
remoteclaw logs --follow

Look for:

• Direct tiny calls succeed, but RemoteClaw runs fail only on larger prompts.
• model_not_found or 404 errors even though direct /v1/chat/completions works with the same bare model id.
• Backend errors about messages[].content expecting a string.
• Intermittent incomplete turn detected ... stopReason=stop payloads=0 warnings with an OpenAI-compatible local backend.
• Backend crashes that appear only with larger prompt-token counts or full agent runtime prompts.

- `model_not_found` with a local MLX/vLLM-style server: verify `baseUrl` includes `/v1`, `api` is `"openai-completions"` for `/v1/chat/completions` backends, and `models.providers..models[].id` is the bare provider-local id. Select it with the provider prefix once, for example `mlx/mlx-community/Qwen3-30B-A3B-6bit`; keep the catalog entry as `mlx-community/Qwen3-30B-A3B-6bit`. - `messages[...].content: invalid type: sequence, expected a string`: backend rejects structured Chat Completions content parts. Fix: set `models.providers..models[].compat.requiresStringContent: true`. - `validation.keys` or allowed message keys like `["role","content"]`: backend rejects OpenAI-style replay metadata on Chat Completions messages. Fix: set `models.providers..models[].compat.strictMessageKeys: true`. - `incomplete turn detected ... stopReason=stop payloads=0`: the backend completed the Chat Completions request but returned no user-visible assistant text for that turn. RemoteClaw retries replay-safe empty OpenAI-compatible turns once; persistent failures usually mean the backend is emitting empty/non-text content or suppressing final-answer text. - Direct tiny requests succeed, but RemoteClaw agent runs fail with backend/model crashes (for example Gemma on some `inferrs` builds): RemoteClaw transport is likely already correct; the backend is failing on the larger agent-runtime prompt shape. - Failures shrink after disabling tools but do not disappear: tool schemas were part of the pressure, but the remaining issue is still upstream model/server capacity or a backend bug. 1. Set `compat.requiresStringContent: true` for string-only Chat Completions backends. 2. Set `compat.strictMessageKeys: true` for strict Chat Completions backends that only accept `role` and `content` on each message. 3. Set `compat.supportsTools: false` for models/backends that cannot handle RemoteClaw's tool schema surface reliably. 4. Lower prompt pressure where possible: smaller workspace bootstrap, shorter session history, lighter local model, or a backend with stronger long-context support. 5. If tiny direct requests keep passing while RemoteClaw agent turns still crash inside the backend, treat it as an upstream server/model limitation and file a repro there with the accepted payload shape.

Related:

• Configuration
• Local models
• OpenAI-compatible endpoints

No replies

If channels are up but nothing answers, check routing and policy before reconnecting anything.

remoteclaw status
remoteclaw channels status --probe
remoteclaw pairing list --channel <channel> [--account <id>]
remoteclaw config get channels
remoteclaw logs --follow

Look for:

• Pairing pending for DM senders.
• Group mention gating (requireMention, mentionPatterns).
• Channel/group allowlist mismatches.

Common signatures:

• drop guild message (mention required → group message ignored until mention.
• pairing request → sender needs approval.
• blocked / allowlist → sender/channel was filtered by policy.

Related:

• Channel troubleshooting
• Groups
• Pairing

Dashboard control UI connectivity

When the dashboard/control UI will not connect, validate URL, auth mode, and secure context assumptions.

remoteclaw gateway status
remoteclaw status
remoteclaw logs --follow
remoteclaw doctor
remoteclaw gateway status --json

Look for:

• Correct probe URL and dashboard URL.
• Auth mode/token mismatch between client and gateway.
• HTTP usage where device identity is required.

If a local browser cannot connect to 127.0.0.1:18789 after an update, first recover the local Gateway service and confirm it is serving the dashboard:

remoteclaw gateway restart
lsof -i :18789
curl http://127.0.0.1:18789

If curl returns RemoteClaw HTML, the Gateway is working and the remaining issue is likely browser cache, an old deep link, or stale tab state. Open http://127.0.0.1:18789 directly and navigate from the dashboard. If restart does not leave the service running, run remoteclaw gateway start and recheck remoteclaw gateway status.

- `device identity required` → non-secure context or missing device auth. - `origin not allowed` → browser `Origin` is not in `gateway.controlUi.allowedOrigins` (or you are connecting from a non-loopback browser origin without an explicit allowlist). - `device nonce required` / `device nonce mismatch` → client is not completing the challenge-based device auth flow (`connect.challenge` + `device.nonce`). - `device signature invalid` / `device signature expired` → client signed the wrong payload (or stale timestamp) for the current handshake. - `AUTH_TOKEN_MISMATCH` with `canRetryWithDeviceToken=true` → client can do one trusted retry with cached device token. - That cached-token retry reuses the cached scope set stored with the paired device token. Explicit `deviceToken` / explicit `scopes` callers keep their requested scope set instead. - `AUTH_SCOPE_MISMATCH` → the device token was recognized, but its approved scopes do not cover this connect request; re-pair or approve the requested scope contract instead of rotating a shared gateway token. - Outside that retry path, connect auth precedence is explicit shared token/password first, then explicit `deviceToken`, then stored device token, then bootstrap token. - On the async Tailscale Serve Control UI path, failed attempts for the same `{scope, ip}` are serialized before the limiter records the failure. Two bad concurrent retries from the same client can therefore surface `retry later` on the second attempt instead of two plain mismatches. - `too many failed authentication attempts (retry later)` from a browser-origin loopback client → repeated failures from that same normalized `Origin` are locked out temporarily; another localhost origin uses a separate bucket. - Repeated `unauthorized` after that retry → shared token/device token drift; refresh token config and re-approve/rotate device token if needed. - `gateway connect failed:` → wrong host/port/url target.

Auth detail codes quick map

Use error.details.code from the failed connect response to pick the next action:

Detail code	Meaning	Recommended action
AUTH_TOKEN_MISSING	Client did not send a required shared token.	Paste/set token in the client and retry. For dashboard paths: remoteclaw config get gateway.auth.token then paste into Control UI settings.
AUTH_TOKEN_MISMATCH	Shared token did not match gateway auth token.	If canRetryWithDeviceToken=true, allow one trusted retry. Cached-token retries reuse stored approved scopes; explicit deviceToken / scopes callers keep requested scopes. If still failing, run the token drift recovery checklist.
AUTH_DEVICE_TOKEN_MISMATCH	Cached per-device token is stale or revoked.	Rotate/re-approve device token using devices CLI, then reconnect.
AUTH_SCOPE_MISMATCH	Device token is valid, but its approved role/scopes do not cover this connect request.	Re-pair the device or approve the requested scope contract; do not treat this as shared-token drift.
PAIRING_REQUIRED	Device identity needs approval. Check error.details.reason for not-paired, scope-upgrade, role-upgrade, or metadata-upgrade, and use requestId / remediationHint when present.	Approve pending request: remoteclaw devices list then remoteclaw devices approve <requestId>. Scope/role upgrades use the same flow after you review the requested access.

Direct loopback backend RPCs authenticated with the shared gateway token/password should not depend on the CLI's paired-device scope baseline. If subagents or other internal calls still fail with `scope-upgrade`, verify the caller is using `client.id: "gateway-client"` and `client.mode: "backend"` and is not forcing an explicit `deviceIdentity` or device token.

Device auth v2 migration check:

remoteclaw --version
remoteclaw doctor
remoteclaw gateway status

If logs show nonce/signature errors, update the connecting client and verify it:

Client waits for the gateway-issued `connect.challenge`. Client signs the challenge-bound payload. Client sends `connect.params.device.nonce` with the same challenge nonce.

If remoteclaw devices rotate / revoke / remove is denied unexpectedly:

• Paired-device token sessions can manage only their own device unless the caller also has operator.admin.
• remoteclaw devices rotate --scope ... can only request operator scopes that the caller session already holds.

Related:

• Configuration (gateway auth modes)
• Control UI
• Devices
• Remote access
• Trusted proxy auth

Gateway service not running

Use when the service is installed but the process does not stay up.

remoteclaw gateway status
remoteclaw status
remoteclaw logs --follow
remoteclaw doctor
remoteclaw gateway status --deep   # also scan system-level services

Look for:

• Runtime: stopped with exit hints.
• Service config mismatch (Config (cli) vs Config (service)).
• Port/listener conflicts.
• Extra launchd/systemd/schtasks installs when --deep is used.
• Other gateway-like services detected (best effort) cleanup hints.

- `Gateway start blocked: set gateway.mode=local` or `existing config is missing gateway.mode` → local gateway mode is not enabled, or the config file was clobbered and lost `gateway.mode`. Fix: set `gateway.mode="local"` in your config, or re-run `remoteclaw onboard --mode local` / `remoteclaw setup` to restamp the expected local-mode config. If you are running RemoteClaw via Podman, the default config path is `~/.remoteclaw/remoteclaw.json`. - `refusing to bind gateway ... without auth` → non-loopback bind without a valid gateway auth path (token/password, or trusted-proxy where configured). - `another gateway instance is already listening` / `EADDRINUSE` → port conflict. - `Other gateway-like services detected (best effort)` → stale or parallel launchd/systemd/schtasks units exist. Most setups should keep one gateway per machine; if you do need more than one, isolate ports + config/state/workspace. See [/gateway#multiple-gateways-same-host](/gateway#multiple-gateways-same-host). - `System-level RemoteClaw gateway service detected` from doctor → a systemd system unit exists while the user-level service is missing. Remove or disable the duplicate before allowing doctor to install a user service, or set `REMOTECLAW_SERVICE_REPAIR_POLICY=external` if the system unit is the intended supervisor. - `Gateway service port does not match current gateway config` → the installed supervisor still pins the old `--port`. Run `remoteclaw doctor --fix` or `remoteclaw gateway install --force`, then restart the gateway service.

Related:

• Background exec and process tool
• Configuration
• Doctor

macOS gateway silently stops responding, then resumes when you touch the dashboard

Use when channels (Telegram, WhatsApp, etc.) on a macOS host go quiet for minutes to hours at a time, and the gateway appears to come back the moment you open the Control UI, SSH in, or otherwise interact with the host. There is usually no obvious symptom in remoteclaw status because by the time you look the gateway is alive again.

ls ~/.remoteclaw/logs/stability/ | tail -5
remoteclaw gateway stability --bundle latest
pmset -g log | grep -iE "sleep|wake|maintenance" | tail -50
launchctl print gui/$UID/org.remoteclaw.gateway | grep -E "state|last exit|runs"

Look for:

• One or more *-uncaught_exception.json bundles in ~/.remoteclaw/logs/stability/ with error.code set to a transient network code such as ENETDOWN, ENETUNREACH, EHOSTUNREACH, or ECONNREFUSED.
• pmset -g log lines like Entering Sleep state due to 'Maintenance Sleep' or en0 driver is slow (msg: WillChangeState to 0) aligned with the crash timestamps. Power Nap / Maintenance Sleep briefly puts the Wi-Fi driver into state 0; any outbound connect() that lands in that window can fail with ENETDOWN even on a host that otherwise has full network connectivity.
• launchctl print output showing state = not running with multiple recent runs and an exit code, especially when the gap between crash and the next launch is on the order of an hour rather than seconds. macOS launchd applies an undocumented respawn-protection gate after a crash burst that can stop honoring KeepAlive=true until an external trigger such as interactive login, dashboard connection, or launchctl kickstart re-arms it.

Common signatures:

• A stability bundle whose error.code is ENETDOWN or a sibling code, with the call stack pointing into Node net lookupAndConnect / Socket.connect. RemoteClaw 2026.5.26 and newer classify these as benign transient network errors so they no longer propagate to the top-level uncaught handler; if you are on an older release, upgrade first.
• Long quiet periods that end the instant you connect to the Control UI or SSH into the host: the user-visible activity is what re-arms launchd’s respawn gate, not anything the dashboard does to the gateway.
• runs count incrementing across the day with no corresponding received SIG*; shutting down line in ~/Library/Logs/remoteclaw/gateway.log: clean shutdowns log a signal; transient crashes do not.

What to do:

1. Upgrade the gateway if you are running a release before 2026.5.26. After upgrading, future ENETDOWN errors are logged as warnings instead of terminating the process.

2. Reduce maintenance sleep activity on Mac mini / desktop hosts meant to run as always-on servers:

   sudo pmset -a sleep 0 disksleep 0 standby 0 powernap 0

   This significantly reduces, but does not entirely eliminate, the underlying driver flap. The system can still perform some maintenance sleeps for TCP keepalive and mDNS upkeep regardless of these flags.

3. Add a liveness watchdog so a future crash burst that gets parked by launchd is caught quickly:

   # Example launchd-aware liveness check, suitable for a 5-minute cron or LaunchAgent
   state=$(launchctl print gui/$UID/org.remoteclaw.gateway 2>/dev/null | awk -F'= ' '/state =/ {print $2; exit}')
   if [ "$state" != "running" ]; then
     launchctl kickstart -k gui/$UID/org.remoteclaw.gateway
   fi

   The point is to externally re-arm the respawn gate; KeepAlive=true alone is not sufficient on macOS after a crash burst.

Related:

• macOS platform notes
• Logging
• Doctor

Gateway exits during high memory use

Use when the Gateway disappears under load, the supervisor reports an OOM-style restart, or logs mention critical memory pressure bundle written.

remoteclaw gateway status --deep
remoteclaw logs --follow
remoteclaw gateway stability --bundle latest
remoteclaw gateway diagnostics export

Look for:

• Reason: diagnostic.memory.pressure.critical in the latest stability bundle.
• Memory pressure: with critical/rss_threshold, critical/heap_threshold, or critical/rss_growth.
• V8 heap: values near the heap limit.
• Largest session files: entries such as agents/<agent>/sessions/<session>.jsonl or sessions/<session>.jsonl.
• Linux cgroup memory counters when the gateway runs inside a container or memory-limited service.

Common signatures:

• critical memory pressure bundle written appears shortly before restart → RemoteClaw captured a pre-OOM stability bundle. Inspect it with remoteclaw gateway stability --bundle latest.
• memory pressure: level=critical ... memoryPressureSnapshot=disabled appears in gateway logs → RemoteClaw detected critical memory pressure, but the pre-OOM stability snapshot is off.
• Largest session files: points at a very large redacted transcript path → reduce retained session history, inspect session growth, or move old transcripts out of the active store before restarting.
• V8 heap: used bytes are close to the heap limit → lower prompt/session pressure, reduce concurrent work, or raise the Node heap limit only after confirming the workload is expected.
• Memory pressure: critical/rss_growth → memory grew quickly inside one sampling window. Check the latest logs for a large import, runaway tool output, repeated retries, or a batch of queued agent work.
• Critical memory pressure appears in logs but no bundle exists → this is the default. Set diagnostics.memoryPressureSnapshot: true to capture the pre-OOM stability bundle on future critical memory pressure events.

The stability bundle is payload-free. It includes operational memory evidence and redacted relative file paths, not message text, webhook bodies, credentials, tokens, cookies, or raw session ids. Attach the diagnostics export to bug reports instead of copying raw logs.

Related:

• Gateway health
• Diagnostics export
• Sessions

Gateway rejected invalid config

Use when Gateway startup fails with Invalid config or hot reload logs say it skipped an invalid edit.

remoteclaw logs --follow
remoteclaw config file
remoteclaw config validate
remoteclaw doctor

Look for:

• Invalid config at ...
• config reload skipped (invalid config): ...
• Config write rejected: ...
• A timestamped remoteclaw.json.rejected.* file beside the active config.
• A timestamped remoteclaw.json.clobbered.* file if doctor --fix repaired a broken direct edit.
• RemoteClaw keeps the latest 32 .clobbered.* files for each config path and rotates older ones.

- The config did not validate during startup, hot reload, or an RemoteClaw-owned write. - Gateway startup fails closed instead of rewriting `remoteclaw.json`. - Hot reload skips invalid external edits and keeps the current runtime config active. - RemoteClaw-owned writes reject invalid/destructive payloads before commit and save `.rejected.*`. - `remoteclaw doctor --fix` owns repair. It can remove non-JSON prefixes or restore the last-known-good copy while preserving the rejected payload as `.clobbered.*`. - When many repairs happen for one config path, RemoteClaw rotates older `.clobbered.*` files so the newest repaired payload is still available. ```bash CONFIG="$(remoteclaw config file)" ls -lt "$CONFIG".clobbered.* "$CONFIG".rejected.* 2>/dev/null | head diff -u "$CONFIG" "$(ls -t "$CONFIG".clobbered.* 2>/dev/null | head -n 1)" remoteclaw config validate remoteclaw doctor ``` - `.clobbered.*` exists → doctor preserved a broken external edit while repairing the active config. - `.rejected.*` exists → an RemoteClaw-owned config write failed schema or clobber checks before commit. - `Config write rejected:` → the write tried to drop required shape, shrink the file sharply, or persist invalid config. - `config reload skipped (invalid config):` → a direct edit failed validation and was ignored by the running Gateway. - `Invalid config at ...` → startup failed before Gateway services booted. - `missing-meta-vs-last-good`, `gateway-mode-missing-vs-last-good`, or `size-drop-vs-last-good:*` → an RemoteClaw-owned write was rejected because it lost fields or size compared with the last-known-good backup. - `Config last-known-good promotion skipped` → the candidate contained redacted secret placeholders such as `***`. 1. Run `remoteclaw doctor --fix` to let doctor repair prefixed/clobbered config or restore last-known-good. 2. Copy only the intended keys from `.clobbered.*` or `.rejected.*`, then apply them with `remoteclaw config set` or `config.patch`. 3. Run `remoteclaw config validate` before restarting. 4. If you edit by hand, keep the full JSON5 config, not just the partial object you wanted to change.

Related:

• Config
• Configuration: hot reload
• Configuration: strict validation
• Doctor

Gateway probe warnings

Use when remoteclaw gateway probe reaches something, but still prints a warning block.

remoteclaw gateway probe
remoteclaw gateway probe --json
remoteclaw gateway probe --ssh user@gateway-host

Look for:

• warnings[].code and primaryTargetId in JSON output.
• Whether the warning is about SSH fallback, multiple gateways, missing scopes, or unresolved auth refs.

Common signatures:

• SSH tunnel failed to start; falling back to direct probes. → SSH setup failed, but the command still tried direct configured/loopback targets.
• multiple reachable gateway identities detected → distinct gateways answered, or RemoteClaw could not prove reachable targets are the same gateway. An SSH tunnel, proxy URL, or configured remote URL to the same gateway is treated as one gateway with multiple transports, even when transport ports differ.
• Read-probe diagnostics are limited by gateway scopes (missing operator.read) → connect worked, but detail RPC is scope-limited; pair device identity or use credentials with operator.read.
• Gateway accepted the WebSocket connection, but follow-up read diagnostics failed → connect worked, but the full diagnostic RPC set timed out or failed. Treat this as a reachable Gateway with degraded diagnostics; compare connect.ok and connect.rpcOk in --json output.
• Capability: pairing-pending or gateway closed (1008): pairing required → the gateway answered, but this client still needs pairing/approval before normal operator access.
• Unresolved gateway.auth.* / gateway.remote.* SecretRef warning text → auth material was unavailable in this command path for the failed target.

Related:

• Gateway
• Multiple gateways on the same host
• Remote access

Channel connected, messages not flowing

If channel state is connected but message flow is dead, focus on policy, permissions, and channel specific delivery rules.

remoteclaw channels status --probe
remoteclaw pairing list --channel <channel> [--account <id>]
remoteclaw status --deep
remoteclaw logs --follow
remoteclaw config get channels

Look for:

• DM policy (pairing, allowlist, open, disabled).
• Group allowlist and mention requirements.
• Missing channel API permissions/scopes.

Common signatures:

• mention required → message ignored by group mention policy.
• pairing / pending approval traces → sender is not approved.
• missing_scope, not_in_channel, Forbidden, 401/403 → channel auth/permissions issue.

Related:

• Channel troubleshooting
• Discord
• Telegram
• WhatsApp

Cron and heartbeat delivery

If cron or heartbeat did not run or did not deliver, verify scheduler state first, then delivery target.

remoteclaw cron status
remoteclaw cron list
remoteclaw cron runs --id <jobId> --limit 20
remoteclaw system heartbeat last
remoteclaw logs --follow

Look for:

• Cron enabled and next wake present.
• Job run history status (ok, skipped, error).
• Heartbeat skip reasons (quiet-hours, requests-in-flight, cron-in-progress, lanes-busy, alerts-disabled, empty-heartbeat-file, no-tasks-due).

- `cron: scheduler disabled; jobs will not run automatically` → cron disabled. - `cron: timer tick failed` → scheduler tick failed; check file/log/runtime errors. - `heartbeat skipped` with `reason=quiet-hours` → outside active hours window. - `heartbeat skipped` with `reason=empty-heartbeat-file` → `HEARTBEAT.md` exists but only contains blank, comment, header, fence, or empty-checklist scaffolding, so RemoteClaw skips the model call. - `heartbeat skipped` with `reason=no-tasks-due` → `HEARTBEAT.md` contains a `tasks:` block, but none of the tasks are due on this tick. - `heartbeat: unknown accountId` → invalid account id for heartbeat delivery target. - `heartbeat skipped` with `reason=dm-blocked` → heartbeat target resolved to a DM-style destination while `agents.defaults.heartbeat.directPolicy` (or per-agent override) is set to `block`.

Related:

• Heartbeat
• Scheduled tasks
• Scheduled tasks: troubleshooting

Node paired, tool fails

If a node is paired but tools fail, isolate foreground, permission, and approval state.

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

Look for:

• Node online with expected capabilities.
• OS permission grants for camera/mic/location/screen.
• Exec approvals and allowlist state.

Common signatures:

• NODE_BACKGROUND_UNAVAILABLE → node app must be in foreground.
• *_PERMISSION_REQUIRED / LOCATION_PERMISSION_REQUIRED → missing OS permission.
• SYSTEM_RUN_DENIED: approval required → exec approval pending.
• SYSTEM_RUN_DENIED: allowlist miss → command blocked by allowlist.

Related:

• Exec approvals
• Node troubleshooting
• Nodes

Browser tool fails

Use when browser tool actions fail even though the gateway itself is healthy.

remoteclaw browser status
remoteclaw browser start --browser-profile remoteclaw
remoteclaw browser profiles
remoteclaw logs --follow
remoteclaw doctor

Look for:

• Whether plugins.allow is set and includes browser.
• Valid browser executable path.
• CDP profile reachability.
• Local Chrome availability for existing-session / user profiles.

- `unknown command "browser"` or `unknown command 'browser'` → the bundled browser plugin is excluded by `plugins.allow`. - Browser tool missing / unavailable while `browser.enabled=true` → `plugins.allow` excludes `browser`, so the plugin never loaded. - `Failed to start Chrome CDP on port` → browser process failed to launch. - `browser.executablePath not found` → configured path is invalid. - `browser.cdpUrl must be http(s) or ws(s)` → the configured CDP URL uses an unsupported scheme such as `file:` or `ftp:`. - `browser.cdpUrl has invalid port` → the configured CDP URL has a bad or out-of-range port. - `Playwright is not available in this gateway build; '' is unsupported.` → the current gateway install lacks the core browser runtime dependency; reinstall or update RemoteClaw, then restart the gateway. ARIA snapshots and basic page screenshots can still work, but navigation, AI snapshots, CSS-selector element screenshots, and PDF export stay unavailable. - `Could not find DevToolsActivePort for chrome` → Chrome MCP existing-session could not attach to the selected browser data dir yet. Open the browser inspect page, enable remote debugging, keep the browser open, approve the first attach prompt, then retry. If signed-in state is not required, prefer the managed `remoteclaw` profile. - `No browser tabs found for profile="user"` → the Chrome MCP attach profile has no open local Chrome tabs. - `Remote CDP for profile "" is not reachable` → the configured remote CDP endpoint is not reachable from the gateway host. - `Browser attachOnly is enabled ... not reachable` or `Browser attachOnly is enabled and CDP websocket ... is not reachable` → attach-only profile has no reachable target, or the HTTP endpoint answered but the CDP WebSocket still could not be opened. - `fullPage is not supported for element screenshots` → screenshot request mixed `--full-page` with `--ref` or `--element`. - `element screenshots are not supported for existing-session profiles; use ref from snapshot.` → Chrome MCP / `existing-session` screenshot calls must use page capture or a snapshot `--ref`, not CSS `--element`. - `existing-session file uploads do not support element selectors; use ref/inputRef.` → Chrome MCP upload hooks need snapshot refs, not CSS selectors. - `existing-session file uploads currently support one file at a time.` → send one upload per call on Chrome MCP profiles. - `existing-session dialog handling does not support timeoutMs.` → dialog hooks on Chrome MCP profiles do not support timeout overrides. - `existing-session type does not support timeoutMs overrides.` → omit `timeoutMs` for `act:type` on `profile="user"` / Chrome MCP existing-session profiles, or use a managed/CDP browser profile when a custom timeout is required. - `existing-session evaluate does not support timeoutMs overrides.` → omit `timeoutMs` for `act:evaluate` on `profile="user"` / Chrome MCP existing-session profiles, or use a managed/CDP browser profile when a custom timeout is required. - `response body is not supported for existing-session profiles yet.` → `responsebody` still requires a managed browser or raw CDP profile. - Stale viewport / dark-mode / locale / offline overrides on attach-only or remote CDP profiles → run `remoteclaw browser stop --browser-profile ` to close the active control session and release Playwright/CDP emulation state without restarting the whole gateway.

Related:

• Browser (RemoteClaw-managed)
• Browser troubleshooting

If you upgraded and something suddenly broke

Most post-upgrade breakage is config drift or stricter defaults now being enforced.

```bash remoteclaw gateway status remoteclaw config get gateway.mode remoteclaw config get gateway.remote.url remoteclaw config get gateway.auth.mode ```

What to check:

- If `gateway.mode=remote`, CLI calls may be targeting remote while your local service is fine.
- Explicit `--url` calls do not fall back to stored credentials.

Common signatures:

- `gateway connect failed:` → wrong URL target.
- `unauthorized` → endpoint reachable but wrong auth.

```bash remoteclaw config get gateway.bind remoteclaw config get gateway.auth.mode remoteclaw config get gateway.auth.token remoteclaw gateway status remoteclaw logs --follow ```

What to check:

- Non-loopback binds (`lan`, `tailnet`, `custom`) need a valid gateway auth path: shared token/password auth, or a correctly configured non-loopback `trusted-proxy` deployment.
- Old keys like `gateway.token` do not replace `gateway.auth.token`.

Common signatures:

- `refusing to bind gateway ... without auth` → non-loopback bind without a valid gateway auth path.
- `Connectivity probe: failed` while runtime is running → gateway alive but inaccessible with current auth/url.

```bash remoteclaw devices list remoteclaw pairing list --channel [--account ] remoteclaw logs --follow remoteclaw doctor ```

What to check:

- Pending device approvals for dashboard/nodes.
- Pending DM pairing approvals after policy or identity changes.

Common signatures:

- `device identity required` → device auth not satisfied.
- `pairing required` → sender/device must be approved.

If the service config and runtime still disagree after checks, reinstall service metadata from the same profile/state directory:

remoteclaw gateway install --force
remoteclaw gateway restart

Related:

• Authentication
• Background exec and process tool
• Gateway-owned pairing

Related

• Doctor
• FAQ
• Gateway runbook