Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build the Clawdbot macOS menu bar app from source. Use when you need to install the Clawdbot.app companion (for menu bar status, permissions, and Mac hardware access like camera/screen recording). Handles dependency installation, UI build, Swift compilation, code signing, and app packaging automatically.
Build the Clawdbot macOS menu bar app from source. Use when you need to install the Clawdbot.app companion (for menu bar status, permissions, and Mac hardware access like camera/screen recording). Handles dependency installation, UI build, Swift compilation, code signing, and app packaging automatically.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
The macOS companion app provides menu-bar status, native notifications, and access to Mac hardware (camera, screen recording, system commands). This skill builds it from source.
macOS (10.14+) Xcode 15+ with Command Line Tools Node.js >= 22 pnpm package manager 30+ GB free disk space (Swift build artifacts) Internet connection (large dependencies)
# Clone repo cd /tmp && rm -rf clawdbot-build && git clone https://github.com/clawdbot/clawdbot.git clawdbot-build # Install + build cd /tmp/clawdbot-build pnpm install pnpm ui:build # Accept Xcode license (one-time) sudo xcodebuild -license accept # Build macOS app with ad-hoc signing ALLOW_ADHOC_SIGNING=1 bash scripts/package-mac-app.sh # Install to /Applications cp -r dist/Clawdbot.app /Applications/Clawdbot.app # Launch open /Applications/Clawdbot.app
Clones the latest Clawdbot source from GitHub. This includes the macOS app source in apps/macos/.
Installs Node.js dependencies for the entire workspace (~1 minute). Warnings about missing binaries in some extensions are harmless.
Compiles the Control UI (Vite โ TypeScript/React). Output goes to dist/control-ui/. Takes ~30 seconds.
Required once per Xcode update. If you get "license not agreed" errors during Swift build, run: sudo xcodebuild -license accept
Runs the full Swift build pipeline: Fetches Swift package dependencies (SwiftUI libraries, etc.) Compiles the macOS app for your architecture (arm64 for M1+, x86_64 for Intel) Bundles resources (model catalog, localizations, etc.) Code-signs the app Signing options: Ad-hoc signing (fastest): ALLOW_ADHOC_SIGNING=1 โ good for local testing, app won't notarize for distribution Developer ID signing (production): Set SIGN_IDENTITY="Developer ID Application: <name>" if you have a signing certificate This step takes 10-20 minutes depending on your Mac.
Copies the built app to the system Applications folder so it runs like any other macOS app.
Opens the app. On first run, you'll see permission prompts (Notifications, Accessibility, Screen Recording, etc.) โ approve them for full functionality.
Swift build requires 6.2+. Update Xcode: softwareupdate -i -a
sudo xcodebuild -license accept
Use ad-hoc signing for local builds: ALLOW_ADHOC_SIGNING=1 bash scripts/package-mac-app.sh
Ensure Xcode is fully updated: xcode-select --install or update via App Store Check disk space: df -h (need ~30GB free) Close other apps to free RAM
Check that it's properly signed: codesign -v /Applications/Clawdbot.app If signing failed, rebuild with ALLOW_ADHOC_SIGNING=1.
Menu bar status โ See Gateway health and receive notifications Permission management โ Owns TTC prompts for Notifications, Accessibility, Screen Recording, Microphone, etc. Local/Remote modes: Local: Gateway runs on your Mac; app manages launchd service Remote: App connects to Gateway on another machine (VPS, home server) via SSH/Tailscale; keeps your Mac accessible even while sleeping Mac hardware access: Camera, screen recording, Canvas, voice wake-word Deep linking: Trigger agent requests via clawdbot:// URL scheme See the official docs: https://docs.clawd.bot/platforms/macos
For production distribution, you'll need: Apple Developer ID certificate (paid) Notarization credentials See: https://docs.clawd.bot/platforms/mac/release For personal use, ad-hoc signing is fine.
After the app launches: Complete the permission checklist (TCC prompts) Choose Local or Remote mode If Local: ensure the Gateway is running (clawdbot gateway status) Open Clawdbot.app menu bar icon to configure Then from the terminal, you can manage the Gateway: clawdbot gateway status clawdbot gateway restart
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.