Break the Text-Only Ceiling: Bridge OpenClaw Skills to AppleScript and Automator on macOS (2026)

Most OpenClaw setups stop at shell and chat. macOS already ships AppleScript and Automator so an agent can open Keynote, change volume, or run a saved workflow—not just reply in Telegram.

Pattern: a SKILL.md tells the agent when to call a small bridge script that wraps osascript. See OpenClaw onboard, messenger channels, Rules vs Skills.

Why bridge OpenClaw to the desktop

CLI agents cannot click Keynote’s Export menu. A local bridge keeps data on-disk and uses the same TCC prompts as any macro tool.

Quotable: OpenClaw chooses the action; openclaw-mac-bridge.sh enforces an allowlist; AppleScript drives GUI apps.

Architecture

Eight-step runbook

Steps 1–2 — Prerequisites + skill folder

openclaw --version
mkdir -p ~/.openclaw/skills/mac-desktop

Step 3 — SKILL.md

Document allowed actions: keynote_export_pdf, set_volume, run_automator. Forbid destructive commands without explicit chat confirmation.

Steps 4–5 — Bridge script + Automation

#!/usr/bin/env bash
ACTION="${1:-}"
case "$ACTION" in
  set_volume) osascript -e "set volume output volume ${2:-40}" ;;
  run_automator) automator "$2" ;;
esac

Run once: ~/bin/openclaw-mac-bridge.sh set_volume 30 and approve **Automation** prompts.

Steps 6–8 — Test + Telegram trigger

1. osascript -e 'tell application "Music" to get name of current track'
2. Ask OpenClaw in chat; **approve** only matching allowlist commands.
3. Save Automator workflow under ~/Library/Services/; call via run_automator.

Troubleshooting

SSH without GUI: AppleScript needs a logged-in graphical session—use VNC or run the gateway on the Mac at the keyboard.

FAQ