Skip to content

docs(readme): visual refresh — real product screenshots, docs links, verified facts - #236

Merged
KrasimirKralev merged 3 commits into
ID-Robots:mainfrom
KrasimirKralev:docs/readme-refresh
Jul 4, 2026
Merged

KrasimirKralev merged 3 commits into
ID-Robots:mainfrom
KrasimirKralev:docs/readme-refresh

Conversation

@KrasimirKralev

@KrasimirKralev KrasimirKralev commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Repo-front refresh with real product assets and facts synced to the docs/code.

Visuals (all real, captured from a production ClawBox)

  • Hero: the actual desktop environment — English UI, full app grid
  • Agent chat: the on-device agent introducing itself while executing live tool calls (exec/glob chips visible) — the "AI-operated OS" claim, demonstrated
  • Device photo (from clawbox.tech) beside the hardware spec table
  • Theme-aware wordmark header (<picture> light/dark swap), Docs + latest-release badges
  • Assets committed under .github/assets/ (webp, 32–236 KB each)

Content

  • New Documentation section — docs.clawbox.tech, Technical Reference, Troubleshooting/Recovery, Agent Interface, and llms.txt for AI agents
  • New Update + Contributing sections — System Update app / sudo clawbox update; PRs target beta, CI + CodeRabbit
  • "How It Works" and the MCP tool dump condensed to summaries linking the docs (the old inline tool list had already drifted)
  • Community & Links folded into the footer (all links were duplicated in badges)

Facts verified against code/docs (four-angle review)

  • Port 18789 wording corrected (token-gated; not "localhost only" — the service runs --bind lan)
  • Wizard step order fixed to match SetupWizard.tsx (WiFi w/ language → updates → password → AI → Telegram)
  • API-route count 50+ → 90+ (93 actual); "~50 MCP tools" (48 actual); 10 languages ✓; hardware specs ✓ vs docs
  • ALLOWED_HOSTS default gains the 10.43.0.1 AP fallback; .env.example pointer corrected
  • Discord invite standardized to discord.gg/vsTsaY4Tuk (README + CONTRIBUTING). Note: 3 device-UI .tsx files still carry the old invite — that's device code, so it goes via a separate PR to beta.
  • All 8 badges verified live; all 9 docs links resolve; all 5 assets tracked; HTML verified GitHub-sanitizer-safe

Suggested follow-up for @yalexx: upload the desktop hero as the repo's Social preview (Settings) — GitHub link unfurls don't use README images.

Summary by CodeRabbit

  • Documentation
    • Refreshed the main README with updated visuals, badges, and community links.
    • Revised product overview and feature descriptions, plus a clearer high-level architecture section.
    • Updated setup guidance with new environment variable details and improved reference links.
    • Adjusted contributing and footer information for the latest project details.

- Real screenshots from a production device: the desktop environment (hero)
  and a live agent chat showing actual tool calls (exec/glob) — captured via
  Playwright against a ClawBox, English UI, personal data avoided
- Product photo (device on desk) from clawbox.tech into the Hardware section
- Theme-aware wordmark header (light/dark <picture> swap)
- New Documentation section: docs.clawbox.tech, Technical Reference,
  Troubleshooting/Recovery, Agent Interface, llms.txt for AI agents
- New badges: Docs + latest GitHub release
- Facts synced with the docs: port 18789 is token-gated (not 'localhost
  only'), ChatGPT-subscription lane and llama.cpp listed under Flexible AI,
  ~50 MCP tools (was 40+)
- Discord invite standardized to the canonical discord.gg/vsTsaY4Tuk
- 'How It Works' + MCP tool dump condensed to summaries linking the docs
  (single source — the old inline tool list had already drifted)
- New Update section (System Update app / sudo clawbox update) and
  Contributing section (PRs target beta, CI + CodeRabbit)
- Assets live in .github/assets/ (webp, 32-236 KB each)
Four-angle review applied:
- Facts: wizard step order corrected (WiFi w/ language -> updates -> password
  -> AI -> Telegram, per SetupWizard.tsx); ALLOWED_HOSTS default gains the
  10.43.0.1 AP fallback; .env.example pointer reworded (the tabled vars
  aren't in it); '50+' API routes -> 90+ (93 actual route.ts files);
  CONTRIBUTING.md stale Discord invite -> vsTsaY4Tuk (the 3 device-UI .tsx
  occurrences go via a separate beta PR)
- Dedup: setup-wizard flow now enumerated once (was 3x with 3 orderings);
  built-in app list once (Layer 3 no longer re-lists); Layer 4 count
  dropped (stated twice above); Community & Links section removed (every
  link was already in badges/footer) with OpenClaw credit folded into the
  footer; privacy claim stated once in the intro
- Polish: chat screenshot width unified with hero (920); caption trimmed;
  Tech Stack Bun rows merged + architecture-reference pointer added;
  Technical Reference docs-table row tightened; language list -> count

Verified by the review: all 8 badges live (release badge reads v3.1.5), all
9 docs.clawbox.tech links resolve, all 5 assets tracked, <picture> theme
swap + floated img are GitHub-sanitizer-safe, '~50 MCP tools' = 48 actual.
@KrasimirKralev
KrasimirKralev requested a review from a team as a code owner July 4, 2026 15:58
@coderabbitai

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@KrasimirKralev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 20da2e2d-0b58-4b7a-a577-db86a779d99d

📥 Commits

Reviewing files that changed from the base of the PR and between 3da0a48 and 6bcc436.

📒 Files selected for processing (1)
  • README.md
📝 Walkthrough

Walkthrough

This PR updates documentation content across README.md and CONTRIBUTING.md, including a new dark-mode logo, refreshed badges, rewritten product/feature descriptions, a revised architecture explanation, updated environment variables and project structure, and a new Discord invite link.

Changes

Documentation Updates

Layer / File(s) Summary
Header branding and badges
README.md
Logo switched to a dark-mode-aware picture element; header badges updated to link Docs, Discord, and latest release with refreshed platform badges.
Product description and hardware/docs sections
README.md
"What is ClawBox" and key features rewritten with updated claims and wording; hardware section adds workstation mention; documentation link table expanded.
Update flow and architecture explanation
README.md
Update section and "How it Works" replaced with a concise four-layer overview; architecture diagram, port mappings, and token-gating notes revised; Node.js vs Bun WebSocket explanation and refreshed Tech Stack section added.
Project structure, environment variables, contributing, and footer
README.md, CONTRIBUTING.md
Project structure tree updated; environment variable table expanded with new entries; contributing section revised with beta branch guidance; footer/community links reformatted; Discord invite link updated in CONTRIBUTING.md.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description covers the change, but it omits the required template sections like Type of change, Testing, Checklist, and Screenshots/logs. Reformat it to match the template and add the missing sections with concrete test steps, checklist items, and screenshots/logs if applicable.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the README visual refresh and documentation/content updates.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 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 `@README.md`:
- Around line 38-56: The privacy claim in the README is too absolute because the
`ClawBox is **OpenClaw OS**` intro and `**Privacy-first**` feature text say data
never leaves the device, while the `**Flexible AI**` section explicitly mentions
external providers like Claude, GPT, Gemini, and OpenRouter. Update this copy to
describe the product as local-first or on-device by default, and clearly qualify
that cloud providers may process prompts externally when those options are
enabled; keep the wording consistent across the intro and the key features
table.
🪄 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: 628b772f-4a9c-4fe7-b5c3-06396efa9469

📥 Commits

Reviewing files that changed from the base of the PR and between 653ecab and 3da0a48.

⛔ Files ignored due to path filters (2)
  • .github/assets/wordmark-dark.png is excluded by !**/*.png
  • .github/assets/wordmark-light.png is excluded by !**/*.png
📒 Files selected for processing (5)
  • .github/assets/chat-agent.webp
  • .github/assets/clawbox-device.webp
  • .github/assets/desktop.webp
  • CONTRIBUTING.md
  • README.md

Comment thread README.md Outdated
…CodeRabbit)

'Your data never leaves the device' contradicted offering Claude/GPT/Gemini,
which process prompts externally. Reworded the intro and the feature row to
local-first: data lives on the box, nothing leaves with local models, cloud
providers are strictly opt-in.
@KrasimirKralev
KrasimirKralev merged commit fe6be9d into ID-Robots:main Jul 4, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant