docs: point 'Get ClawBox'/store links to clawbox.com#258
Conversation
clawbox.com is now the primary domain (clawbox.tech 301-redirects to it). Update all docs-site links — 'Get ClawBox' CTAs, store links, footer, and docs.clawbox.tech self-references — from clawbox.tech to clawbox.com so they point directly at the canonical domain instead of relying on the redirect. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
📝 WalkthroughWalkthroughDocumentation publishing instructions and site links were updated from ChangesDocumentation domain migration
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. Comment |
🦀 ClawReviewYour friendly reef crab, here with the lay of the land. Swaps every At a glance
Good to know
— ClawReview 🦀, your resident reef crab. Just orientation — CodeRabbit does the line-by-line, humans do the merge. Conventions: docs. |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs-site/llms.txt`:
- Around line 3-51: Update the docs deployment workflow’s CNAME generation and
Pages custom-domain configuration to use docs.clawbox.com consistently,
replacing docs.clawbox.tech. Ensure the exported _site/CNAME and published site
hostname match the URLs referenced by the documentation.
In `@docs-site/README.md`:
- Around line 48-59: Replace all stale docs.clawbox.tech references with
docs.clawbox.com in README.md, scripts/issue-triage.mjs, and
scripts/pr-review.mjs. The cited docs-site/README.md lines 48-59 and
docs-site/llms.txt lines 3-51 already use the correct domain and require no
direct change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 9af8731d-9fd1-4b2f-84e0-5a39caaa6faf
📒 Files selected for processing (8)
docs-site/README.mddocs-site/docs.jsondocs-site/hardware/clawbox-connect.mdxdocs-site/hardware/clawbox-workstation.mdxdocs-site/hardware/requirements.mdxdocs-site/llms.txtdocs-site/setup/openclaw-setup.mdxdocs-site/support/faq.mdx
| > ClawBox is pre-configured AI hardware (NVIDIA Jetson) running OpenClaw OS — a self-hosted AI assistant reachable from Telegram and the web. This documentation covers consumer setup, deep technical reference, troubleshooting, and recovery. Site: https://docs.clawbox.com · Source: https://github.com/ID-Robots/clawbox (docs live in docs-site/, releases are vX.Y.Z tags on main, integration branch is beta). | ||
|
|
||
| Key facts: web UI at http://<box-ip> port 80 (never :18789 — that's the token-gated gateway; it loads but rejects passwords); one Linux password (`clawbox` user) for both SSH and browser login; device state in /home/clawbox/clawbox/data and ~/.openclaw (survives updates; wiped by factory reset); updates are git-tag based and reboot the box at the end; provider credentials live in ~/.openclaw/agents/main/agent/auth-profiles.json. | ||
|
|
||
| ## Start Here | ||
|
|
||
| - [Quick Reference](https://docs.clawbox.tech/technical/quick-reference): the one-page fact sheet — ports, paths, services, commands, endpoints, gotchas. Best single page for agents. | ||
| - [ClawBox Overview](https://docs.clawbox.tech/): what ClawBox is, models, pricing | ||
| - [Quickstart](https://docs.clawbox.tech/quickstart): unbox → power → talk | ||
| - [Quick Reference](https://docs.clawbox.com/technical/quick-reference): the one-page fact sheet — ports, paths, services, commands, endpoints, gotchas. Best single page for agents. | ||
| - [ClawBox Overview](https://docs.clawbox.com/): what ClawBox is, models, pricing | ||
| - [Quickstart](https://docs.clawbox.com/quickstart): unbox → power → talk | ||
|
|
||
| ## Setup | ||
|
|
||
| - [First Boot](https://docs.clawbox.tech/setup/first-boot): unbox, connect, pair via QR code — the first-run guide | ||
| - [Connect to a Network](https://docs.clawbox.tech/setup/connect-network): joining Wi-Fi or Ethernet after setup | ||
| - [Choose Your AI Provider](https://docs.clawbox.tech/setup/choose-ai-provider): ClawBox AI, Claude, GPT, Gemini, OpenRouter, local models | ||
| - [OpenClaw Setup](https://docs.clawbox.tech/setup/openclaw-setup): gateway configuration | ||
| - [First Boot](https://docs.clawbox.com/setup/first-boot): unbox, connect, pair via QR code — the first-run guide | ||
| - [Connect to a Network](https://docs.clawbox.com/setup/connect-network): joining Wi-Fi or Ethernet after setup | ||
| - [Choose Your AI Provider](https://docs.clawbox.com/setup/choose-ai-provider): ClawBox AI, Claude, GPT, Gemini, OpenRouter, local models | ||
| - [OpenClaw Setup](https://docs.clawbox.com/setup/openclaw-setup): gateway configuration | ||
|
|
||
| ## Technical Reference | ||
|
|
||
| - [System Architecture](https://docs.clawbox.tech/technical/architecture): service topology, request routing, boot lifecycle, ClawBox↔OpenClaw relationship | ||
| - [Networking](https://docs.clawbox.tech/technical/networking): AP mode, captive portal, mDNS/clawbox.local reliability, full port map | ||
| - [Filesystem Layout](https://docs.clawbox.tech/technical/filesystem): where everything lives; what survives updates vs factory reset; where secrets are | ||
| - [Authentication & Security](https://docs.clawbox.tech/technical/authentication): browser login flow (unix_chkpwd), session cookies, gateway token, service tokens | ||
| - [AI Providers](https://docs.clawbox.tech/technical/ai-providers): every provider lane, credential storage map, the two OpenAI lanes (openai/ vs codex/), boot-time self-healing | ||
| - [Update System](https://docs.clawbox.tech/technical/update-system): tag-based updates, channels (main/beta), divergence/"Updates paused", manual-update pitfalls | ||
| - [Agent Interface (MCP)](https://docs.clawbox.tech/technical/agent-interface): the ~50 device tools the AI agent gets, clawbox CLI, auth model | ||
| - [System Architecture](https://docs.clawbox.com/technical/architecture): service topology, request routing, boot lifecycle, ClawBox↔OpenClaw relationship | ||
| - [Networking](https://docs.clawbox.com/technical/networking): AP mode, captive portal, mDNS/clawbox.local reliability, full port map | ||
| - [Filesystem Layout](https://docs.clawbox.com/technical/filesystem): where everything lives; what survives updates vs factory reset; where secrets are | ||
| - [Authentication & Security](https://docs.clawbox.com/technical/authentication): browser login flow (unix_chkpwd), session cookies, gateway token, service tokens | ||
| - [AI Providers](https://docs.clawbox.com/technical/ai-providers): every provider lane, credential storage map, the two OpenAI lanes (openai/ vs codex/), boot-time self-healing | ||
| - [Update System](https://docs.clawbox.com/technical/update-system): tag-based updates, channels (main/beta), divergence/"Updates paused", manual-update pitfalls | ||
| - [Agent Interface (MCP)](https://docs.clawbox.com/technical/agent-interface): the ~50 device tools the AI agent gets, clawbox CLI, auth model | ||
|
|
||
| ## Troubleshooting & Recovery | ||
|
|
||
| - [Troubleshooting](https://docs.clawbox.tech/support/troubleshooting): symptom-first diagnostic ladders — can't reach the box, browser rejects password (SSH works), updates stuck, provider 401s, gateway token mismatch, Telegram | ||
| - [Recovery](https://docs.clawbox.tech/support/recovery): ordered recovery options — password reset (sudo passwd clawbox), service restart, safe reinstall (hard-sync + install.sh), factory reset (password → clawbox, AP mode) | ||
| - [Updating ClawBox](https://docs.clawbox.tech/support/updating): the supported update paths | ||
| - [FAQ](https://docs.clawbox.tech/support/faq) | ||
| - [Troubleshooting](https://docs.clawbox.com/support/troubleshooting): symptom-first diagnostic ladders — can't reach the box, browser rejects password (SSH works), updates stuck, provider 401s, gateway token mismatch, Telegram | ||
| - [Recovery](https://docs.clawbox.com/support/recovery): ordered recovery options — password reset (sudo passwd clawbox), service restart, safe reinstall (hard-sync + install.sh), factory reset (password → clawbox, AP mode) | ||
| - [Updating ClawBox](https://docs.clawbox.com/support/updating): the supported update paths | ||
| - [FAQ](https://docs.clawbox.com/support/faq) | ||
|
|
||
| ## Hardware | ||
|
|
||
| - [ClawBox Connect](https://docs.clawbox.tech/hardware/clawbox-connect): Jetson Orin Nano model | ||
| - [ClawBox Workstation](https://docs.clawbox.tech/hardware/clawbox-workstation): DGX Spark model | ||
| - [Requirements](https://docs.clawbox.tech/hardware/requirements) | ||
| - [ClawBox Connect](https://docs.clawbox.com/hardware/clawbox-connect): Jetson Orin Nano model | ||
| - [ClawBox Workstation](https://docs.clawbox.com/hardware/clawbox-workstation): DGX Spark model | ||
| - [Requirements](https://docs.clawbox.com/hardware/requirements) | ||
|
|
||
| ## Using ClawBox | ||
|
|
||
| - [Messaging Channels](https://docs.clawbox.tech/guides/messaging-channels): Telegram (device-managed, pairing-approved) and OpenClaw's wider channel support | ||
| - [Subscriptions](https://docs.clawbox.tech/guides/subscriptions): ClawBox AI plans | ||
| - [Messaging Channels](https://docs.clawbox.com/guides/messaging-channels): Telegram (device-managed, pairing-approved) and OpenClaw's wider channel support | ||
| - [Subscriptions](https://docs.clawbox.com/guides/subscriptions): ClawBox AI plans | ||
|
|
||
| ## External | ||
|
|
||
| - [OpenClaw Documentation](https://docs.openclaw.ai): the upstream AI gateway ClawBox ships | ||
| - [ClawBox Store](https://clawbox.tech) | ||
| - [ClawBox Store](https://clawbox.com) |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== References to docs.clawbox domains ==\n'
rg -n "docs\.clawbox\.(com|tech)" . --hidden --glob '!.git' || true
printf '\n== docs-deploy workflow ==\n'
sed -n '1,220p' .github/workflows/docs-deploy.yml
printf '\n== issue-triage script ==\n'
sed -n '1,260p' scripts/issue-triage.mjsRepository: ID-Robots/clawbox
Length of output: 15367
Update the docs deploy CNAME to docs.clawbox.com
docs-site/README.md and docs-site/llms.txt point at docs.clawbox.com, but .github/workflows/docs-deploy.yml still writes docs.clawbox.tech to _site/CNAME and publishes that host. Align the deploy config and Pages custom-domain setting so the exported site and docs index resolve to the same URL.
🧰 Tools
🪛 LanguageTool
[grammar] ~11-~11: Ensure spelling is correct
Context: ...](https://docs.clawbox.com/quickstart): unbox → power → talk ## Setup - [First Boot](https://docs.clawb...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs-site/llms.txt` around lines 3 - 51, Update the docs deployment
workflow’s CNAME generation and Pages custom-domain configuration to use
docs.clawbox.com consistently, replacing docs.clawbox.tech. Ensure the exported
_site/CNAME and published site hostname match the URLs referenced by the
documentation.
| The intended public URL is **docs.clawbox.com**. | ||
|
|
||
| Two ways to publish: | ||
|
|
||
| 1. **Mintlify hosting (matches docs.openclaw.ai).** Install the Mintlify GitHub App on | ||
| the `ID-Robots/clawbox` repo, point it at this `docs-site/` directory, and set the | ||
| custom domain to `docs.clawbox.tech` in the Mintlify dashboard. Pushes to the docs | ||
| custom domain to `docs.clawbox.com` in the Mintlify dashboard. Pushes to the docs | ||
| branch auto-deploy. (Custom domain / removing Mintlify branding may require a paid | ||
| plan — confirm current Mintlify pricing.) | ||
|
|
||
| 2. **Self-host the static build.** Run `mint build` and deploy the output to Vercel (the | ||
| same place clawbox.tech lives) behind a `docs.clawbox.tech` subdomain. No SaaS fee. | ||
| same place clawbox.com lives) behind a `docs.clawbox.com` subdomain. No SaaS fee. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf 'Repo files of interest:\n'
git ls-files | rg '^(docs-site/(README\.md|llms\.txt)|README\.md|scripts/issue-triage\.mjs)$'
printf '\nREADME excerpt:\n'
sed -n '1,120p' docs-site/README.md
printf '\nllms.txt excerpt:\n'
sed -n '1,120p' docs-site/llms.txt
printf '\nSearch for docs.clawbox.tech / docs.clawbox.com references:\n'
rg -n 'docs\.clawbox\.(tech|com)' README.md docs-site scripts -g '!**/node_modules/**'Repository: ID-Robots/clawbox
Length of output: 13865
Update the remaining docs.clawbox.tech references. docs-site/README.md and docs-site/llms.txt already point at docs.clawbox.com; the stale links are in README.md, scripts/issue-triage.mjs, and scripts/pr-review.mjs.
📍 Affects 2 files
docs-site/README.md#L48-L59(this comment)docs-site/llms.txt#L3-L51
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs-site/README.md` around lines 48 - 59, Replace all stale
docs.clawbox.tech references with docs.clawbox.com in README.md,
scripts/issue-triage.mjs, and scripts/pr-review.mjs. The cited
docs-site/README.md lines 48-59 and docs-site/llms.txt lines 3-51 already use
the correct domain and require no direct change.
What
Updates every clawbox.tech link in
docs-site/to clawbox.com (37 refs across 8 files).Why
clawbox.com is now the primary domain (clawbox.tech 301-redirects into it via Porkbun). On docs.clawbox.com the Get ClawBox button and store cards pointed at
https://clawbox.tech, so clicking bounced through a redirect. This points them directly at the canonical domain.Scope
docs.json— top-bar 'Get ClawBox' CTA, nav href, footer websitesupport/faq.mdxstore linkllms.txt+README.md— docs.clawbox.tech self-references → docs.clawbox.comNo content/behaviour changes beyond the domain swap. Mintlify redeploys docs.clawbox.com on merge to main.
🤖 Generated with Claude Code
Summary by CodeRabbit
clawbox.comdomain.