docs: simplify macOS app overview#97120
Conversation
|
Codex review: needs maintainer review before merge. Reviewed June 26, 2026, 10:19 PM ET / 02:19 UTC. Summary PR surface: Docs -95. Total -95 across 5 files. Reproducibility: not applicable. This PR changes documentation only and does not report a runtime bug. The prior docs accuracy concerns are source-checkable and appear resolved on the latest head. Review metrics: none identified. Stored data model Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Risk before merge
Maintainer options:
Next step before merge
Security Review detailsBest possible solution: Keep the overview/router rewrite open for maintainer review and merge it after the current docs check completes successfully, since the relocated operational claims are source-backed on the latest head. Do we have a high-confidence way to reproduce the issue? Not applicable: this PR changes documentation only and does not report a runtime bug. The prior docs accuracy concerns are source-checkable and appear resolved on the latest head. Is this the best way to solve the issue? Yes: making AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 552ec2b49d4a. Label changesLabel justifications:
Evidence reviewedPR surface: Docs -95. Total -95 across 5 files. View PR surface stats
What I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
* docs: simplify macOS app docs * docs: preserve macOS app detail links * docs: address macOS review feedback
* docs: simplify macOS app docs * docs: preserve macOS app detail links * docs: address macOS review feedback
* docs: simplify macOS app docs * docs: preserve macOS app detail links * docs: address macOS review feedback
* docs: simplify macOS app docs * docs: preserve macOS app detail links * docs: address macOS review feedback
What Problem This Solves
The macOS platform overview was acting like a second runtime reference: it repeated launchd, IPC, exec approvals, deep links, remote tunnel, and dev details that already live under the narrower macOS pages. It also did not give readers an obvious path to download the macOS app from OpenClaw releases.
Why This Change Was Made
This rewrites
docs/platforms/macos.mdas a short overview/router page. It adds a prominent download section that points to OpenClaw GitHub Releases and tells readers to look forOpenClaw-<version>.dmgor.zipassets when a release includes macOS builds. Detailed launchd, remote, permissions, Canvas, IPC, logging, and exec approval content remains linked from the child pages instead of duplicated on the overview.User Impact
macOS readers get a clearer first stop: what the app is for, where to download it, how to start, how to choose local vs remote Gateway mode, and which detail page to open next. The published
/platforms/macosroute stays in place.AI-assisted docs PR.
Evidence
pnpm docs:listpnpm format:docs:checkpnpm lint:docspnpm docs:check-mdxpnpm docs:check-linkspnpm docs:check-i18n-glossarygit diff --checkgh release view/listshowed macOS assets exist on some releases (OpenClaw-<version>.dmg/.zip) but not every latest release, so the docs avoid hardcoding one versioned download URL.