[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698XK7WM0M8YSHWTEW0GEFX":3,"skill-same:01M698XK7WM0M8YSHWTEW0GEFX":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":48,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M698XK7WM0M8YSHWTEW0GEFX","node-connect",null,"Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR\u002Fsetup-code, and reconnect states.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394302,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fnode-connect\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,9,31,32,33,34,35,36,37],"node connect","connect","node","browser","qr","connection","states","native","control","across","route","ios","ui","code","diagnose","setup","auth","android","control ui","macos","2026-11-10 10:12:30",false,"---\nname: node-connect\ndescription: \"Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR\u002Fsetup-code, and reconnect states.\"\n---\n\n# Node Connect\n\nGoal: fix one exact client against one exact Gateway, then prove that client's fresh connection.\n\n## 1. Lock the target\n\nRecord the target environment\u002Fprofile, OpenClaw binary, config\u002Fstate root, Gateway URL\u002Fport, and service before changing anything.\n\n- Use the named deployment wrapper\u002Fprofile for every config, log, service, device, and node command.\n- Never drift to a bare `openclaw`, proof environment, or similarly named deployment.\n- If the global executable is stale, invoke the target through its owner.\n- Verify status, config, logs, and process identity describe the same Gateway.\n\nIdentify the target Gateway before changing pairing or auth.\n\n## 2. Classify the client\n\nClassify from the request and Gateway log before choosing commands:\n\n- **Control UI browser:** the user says browser, dashboard, Control UI, or webchat; logs show `client=openclaw-control-ui` or `mode=webchat`.\n- **Native mobile\u002Fnode:** the official app shows Connect, Scan QR, or setup code; logs\u002Frequest metadata show a native client or `role=node`.\n\nA phone can be either client. Do not use `openclaw qr` or `openclaw nodes status` for a phone browser; those belong to native mobile\u002Fnode pairing.\n\n## 3. Observe the failing attempt\n\nRun these through the locked target:\n\n```bash\nopenclaw gateway status --deep\nopenclaw logs --follow --json\nopenclaw devices list\nopenclaw config get gateway.mode\nopenclaw config get gateway.bind\nopenclaw config get gateway.remote.url\nopenclaw config get gateway.auth.mode\nopenclaw config get gateway.auth.allowTailscale\nopenclaw config get gateway.tailscale.mode\n```\n\nHave the client retry once while logs are live. Correlate its client ID, mode, platform, address, auth result, device ID, user, and close code. Ignore other paired devices.\n\nInterpret the first failed transition:\n\n- No matching Gateway attempt: route, DNS, TLS, origin, or proxy problem.\n- `token_missing`, `password_missing`, mismatch, or Tailscale identity failure: auth failed **before** pairing, so an empty pending list is expected.\n- `pairing required`: route and auth succeeded; approve the exact pending request.\n- `client connected`: match `conn`, `client`, `mode`, and `role` to the exact client. Admission precedes the hello response; if followed by `1006`, preserve auth\u002Fpairing and inspect hello delivery, lifecycle, transport, proxy, or reconnect. Older builds use overlapping `authenticated user connected` \u002F `webchat connected` records that omit ephemeral clients.\n- `1006` without a matching application-level admission record does not prove auth\u002Fpairing; inspect the earlier handshake transition.\n\n## 4. Prove the route\n\nChoose one topology: same machine, LAN, tailnet, or public reverse proxy. Do not mix them.\n\n- Browser Control UI needs HTTPS or localhost for browser device identity. A remote plain-HTTP Tailnet\u002FLAN URL is not a valid substitute.\n- `gateway.tailscale.mode=off` means OpenClaw is not managing Serve\u002FFunnel. It does not prove that Tailscale or an externally managed Serve route is absent.\n- When Tailscale is involved, inspect live state rather than inferring it from OpenClaw config:\n\n```bash\ntailscale status --json\ntailscale serve status --json\n```\n\nMatch the client's URL to the listener\u002Fproxy route reaching the locked Gateway.\n\n## 5A. Control UI browser lane\n\nRestore browser auth before looking for a pairing request:\n\n- For token\u002Fpassword auth, enter the credential in Control UI settings. Never put permanent secrets in chat, logs, or URLs.\n- Prefer `openclaw dashboard` on the Gateway host for a one-time signed handoff. Use `--no-open` only when the operator can retrieve that host's clipboard, and keep the host browser\u002Fclipboard outside agent tooling. Never capture `dashboard --json`: it can expose the handoff and shared credentials. Never relay, rewrite, or send a loopback handoff URL to a remote phone.\n- For Tailscale Serve, verify the live route and forwarded identity. Enable `gateway.auth.allowTailscale` only for that intended trust boundary. Verified Tailscale Control UI auth with browser device identity can skip pairing.\n\nAfter auth succeeds:\n\n- Retry; never infer pairing from the pre-auth attempt. Token\u002Fpassword auth can reveal `pairing required`; verified Tailscale identity can skip it.\n- If logs say `pairing required`, re-list devices and approve the exact request ID.\n- A successful verified-Tailscale connection may correctly create no pending or paired-device row.\n- After a repeated `1006`, preserve auth\u002Fpairing and inspect reconnect evidence.\n\n## 5B. Native mobile\u002Fnode lane\n\nInspect the native route through the locked target without exposing the setup credential:\n\n```bash\nopenclaw qr --json | jq '{gatewayUrl, gatewayUrls, auth, access, accessDowngraded, urlSource}'\n```\n\nFor a CLI controlling a remote Gateway, add `--remote` before `--json`; it selects `gateway.remote.url` and remote credentials. If the redaction filter is unavailable, do not run raw QR JSON in agent-visible output.\n\nVerify `gatewayUrl` and `urlSource`. The setup code is password-equivalent: have the operator copy it from **Control UI → Devices → Pair device**, or run `openclaw qr --setup-code-only` in a terminal outside agent tooling and paste it directly into the official app. Never relay it through agent\u002Fchat\u002Ftool output. Generate a fresh code after a URL\u002Fauth fix or expiry.\n\nIf the app reports `pairing required`:\n\n```bash\nopenclaw devices list\nopenclaw devices approve --latest   # preview only; exits without approval\nopenclaw devices approve \u003CrequestId>\nopenclaw nodes status\n```\n\n`--latest` only previews the current request; never treat it as approval. Re-list immediately before the exact-ID command because retries can supersede the request. Never approve by position, age, or similarity.\n\n## 6. Correlate and finish\n\nBefore approval, match available request, device\u002Fpublic-key, client, mode\u002Frole, platform, address, user, and retry-time facts.\n\nDeclare success only after a new attempt made after the final change proves all applicable checks:\n\n- the exact client reaches the locked Gateway;\n- intended auth succeeds;\n- the browser completes initial requests, or the native node appears in `openclaw nodes status`;\n- approval used the exact request ID; and\n- no immediate auth, pairing, or reconnect failure follows.\n\nA QR\u002Fsetup code, launched browser, empty pending list, approval, paired-device count, or Tailscale ping proves only one transition.\n\nReport the diagnosis, chosen route\u002Fauth lane, exact-client evidence, and any remaining failed transition.\n","# Node Connect\n\nGoal: fix one exact client against one exact Gateway, then prove that client's fresh connection.\n\n## 1. Lock the target\n\nRecord the target environment\u002Fprofile, OpenClaw binary, config\u002Fstate root, Gateway URL\u002Fport, and service before changing anything.\n\n- Use the named deployment wrapper\u002Fprofile for every config, log, service, device, and node command.\n- Never drift to a bare `openclaw`, proof environment, or similarly named deployment.\n- If the global executable is stale, invoke the target through its owner.\n- Verify status, config, logs, and process identity describe the same Gateway.\n\nIdentify the target Gateway before changing pairing or auth.\n\n## 2. Classify the client\n\nClassify from the request and Gateway log before choosing commands:\n\n- **Control UI browser:** the user says browser, dashboard, Control UI, or webchat; logs show `client=openclaw-control-ui` or `mode=webchat`.\n- **Native mobile\u002Fnode:** the official app shows Connect, Scan QR, or setup code; logs\u002Frequest metadata show a native client or `role=node`.\n\nA phone can be either client. Do not use `openclaw qr` or `openclaw nodes status` for a phone browser; those belong to native mobile\u002Fnode pairing.\n\n## 3. Observe the failing attempt\n\nRun these through the locked target:\n\n```bash\nopenclaw gateway status --deep\nopenclaw logs --follow --json\nopenclaw devices list\nopenclaw config get gateway.mode\nopenclaw config get gateway.bind\nopenclaw config get gateway.remote.url\nopenclaw config get gateway.auth.mode\nopenclaw config get gateway.auth.allowTailscale\nopenclaw config get gateway.tailscale.mode\n```\n\nHave the client retry once while logs are live. Correlate its client ID, mode, platform, address, auth result, device ID, user, and close code. Ignore other paired devices.\n\nInterpret the first failed transition:\n\n- No matching Gateway attempt: route, DNS, TLS, origin, or proxy problem.\n- `token_missing`, `password_missing`, mismatch, or Tailscale identity failure: auth failed **before** pairing, so an empty pending list is expected.\n- `pairing required`: route and auth succeeded; approve the exact pending request.\n- `client connected`: match `conn`, `client`, `mode`, and `role` to the exact client. Admission precedes the hello response; if followed by `1006`, preserve auth\u002Fpairing and inspect hello delivery, lifecycle, transport, proxy, or reconnect. Older builds use overlapping `authenticated user connected` \u002F `webchat connected` records that omit ephemeral clients.\n- `1006` without a matching application-level admission record does not prove auth\u002Fpairing; inspect the earlier handshake transition.\n\n## 4. Prove the route\n\nChoose one topology: same machine, LAN, tailnet, or public reverse proxy. Do not mix them.\n\n- Browser Control UI needs HTTPS or localhost for browser device identity. A remote plain-HTTP Tailnet\u002FLAN URL is not a valid substitute.\n- `gateway.tailscale.mode=off` means OpenClaw is not managing Serve\u002FFunnel. It does not prove that Tailscale or an externally managed Serve route is absent.\n- When Tailscale is involved, inspect live state rather than inferring it from OpenClaw config:\n\n```bash\ntailscale status --json\ntailscale serve status --json\n```\n\nMatch the client's URL to the listener\u002Fproxy route reaching the locked Gateway.\n\n## 5A. Control UI browser lane\n\nRestore browser auth before looking for a pairing request:\n\n- For token\u002Fpassword auth, enter the credential in Control UI settings. Never put permanent secrets in chat, logs, or URLs.\n- Prefer `openclaw dashboard` on the Gateway host for a one-time signed handoff. Use `--no-open` only when the operator can retrieve that host's clipboard, and keep the host browser\u002Fclipboard outside agent tooling. Never capture `dashboard --json`: it can expose the handoff and shared credentials. Never relay, rewrite, or send a loopback handoff URL to a remote phone.\n- For Tailscale Serve, verify the live route and forwarded identity. Enable `gateway.auth.allowTailscale` only for that intended trust boundary. Verified Tailscale Control UI auth with browser device identity can skip pairing.\n\nAfter auth succeeds:\n\n- Retry; never infer pairing from the pre-auth attempt. Token\u002Fpassword auth can reveal `pairing required`; verified Tailscale identity can skip it.\n- If logs say `pairing required`, re-list devices and approve the exact request ID.\n- A successful verified-Tailscale connection may correctly create no pending or paired-device row.\n- After a repeated `1006`, preserve auth\u002Fpairing and inspect reconnect evidence.\n\n## 5B. Native mobile\u002Fnode lane\n\nInspect the native route through the locked target without exposing the setup credential:\n\n```bash\nopenclaw qr --json | jq '{gatewayUrl, gatewayUrls, auth, access, accessDowngraded, urlSource}'\n```\n\nFor a CLI controlling a remote Gateway, add `--remote` before `--json`; it selects `gateway.remote.url` and remote credentials. If the redaction filter is unavailable, do not run raw QR JSON in agent-visible output.\n\nVerify `gatewayUrl` and `urlSource`. The setup code is password-equivalent: have the operator copy it from **Control UI → Devices → Pair device**, or run `openclaw qr --setup-code-only` in a terminal outside agent tooling and paste it directly into the official app. Never relay it through agent\u002Fchat\u002Ftool output. Generate a fresh code after a URL\u002Fauth fix or expiry.\n\nIf the app reports `pairing required`:\n\n```bash\nopenclaw devices list\nopenclaw devices approve --latest   # preview only; exits without approval\nopenclaw devices approve \u003CrequestId>\nopenclaw nodes status\n```\n\n`--latest` only previews the current request; never treat it as approval. Re-list immediately before the exact-ID command because retries can supersede the request. Never approve by position, age, or similarity.\n\n## 6. Correlate and finish\n\nBefore approval, match available request, device\u002Fpublic-key, client, mode\u002Frole, platform, address, user, and retry-time facts.\n\nDeclare success only after a new attempt made after the final change proves all applicable checks:\n\n- the exact client reaches the locked Gateway;\n- intended auth succeeds;\n- the browser completes initial requests, or the native node appears in `openclaw nodes status`;\n- approval used the exact request ID; and\n- no immediate auth, pairing, or reconnect failure follows.\n\nA QR\u002Fsetup code, launched browser, empty pending list, approval, paired-device count, or Tailscale ping proves only one transition.\n\nReport the diagnosis, chosen route\u002Fauth lane, exact-client evidence, and any remaining failed transition.\n",{"name":5,"description":7},"main","f1c93577085244aa96aa87b53a2df9b59d293bd7","skills\u002Fnode-connect",82862,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-11 08:46:30",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add openclaw\u002Fopenclaw --skill node-connect",{"tool":58,"command":59},"bunx","bunx skills add openclaw\u002Fopenclaw --skill node-connect",{"tool":61,"command":62},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill node-connect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fnode-connect\u002FSKILL.md",true,[],[67,73,94,112,133,157],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":38},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[69],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":38},"01M698YY8QGQ7S8TJNKJG6VTPH","xurl","xurl CLI for authenticated X posts, replies, reads\u002Fsearch, DMs, media upload, followers, auth status, or raw v2 API calls.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[75,80,81,82,83,84,85,86,87,88,20,89,90,91,92,34,93],"for","api","calls","replies","posts","upload","tap","install","brew","Media","search","npm","status","cli",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":38},"01M698YWT1CJ0WK88WB909R9RT","weather","Current weather and forecasts with web_fetch, falling back to wttr.in curl for locations, rain, temperature, travel planning.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fweather\u002FSKILL.md",[],[96,101,102,87,103,88,104,105,106,107,108,109,80,110,111],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature","with",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":123,"publishedAt":38},"01M698YV2Q0R0JJKAWGFS21K0N","visualize","Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fvisualize\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[114,124,125,126,127,80,111,128,31,129,130,131,9,132],"widgets","openclaw dashboard","author","inline","show","create","visuals","dashboard","widget",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":147,"publishedAt":38},"01M698YS2TRJH9ENG28HD9CD87","trello","Manage Trello boards, lists, and cards via the Trello REST API.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftrello\u002FSKILL.md",[139,144],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":145,"categoryName":146,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000030","开发工程师",[135,105,148,149,150,151,152,153,87,88,154,104,81,155,156],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":38},"01M698YQ9Q3M4W78EWV2KSCSVW","tmux","Control tmux sessions\u002Fpanes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftmux\u002FSKILL.md",[],[159,87,164,165,80,166,167,168,26,169,170,171,88,172,173,174,175,176,177],"send","darwin","keys","paste","output","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]