OpenClaw can already call shell scripts directly. Use this in your prompts:
# Instead of relying on default model, explicitly call the bridge
exec:./scripts/claude-cli-bridge.sh "your prompt here" /tmpexport OPENCLAW_MODEL="shell:/Users/andy/.openclaw/workspace/scripts/claude-cli-bridge.sh"
openclaw gateway restartIn any OpenClaw session, you can override the model:
/model shell:/Users/andy/.openclaw/workspace/scripts/claude-cli-bridge.sh
Create a skill that wraps the bridge:
{
"name": "claude-max",
"description": "Use Claude Code CLI with Max plan",
"command": "/Users/andy/.openclaw/workspace/scripts/claude-cli-bridge.sh"
}cd ~/.openclaw/workspace
./scripts/claude-cli-bridge.sh "What is 2+2?" /tmp- Slower than API: CLI has ~2-3s startup time
- Uses Max plan: No per-call charges
- Good for: Heavy usage sessions where startup time doesn't matter
- Not ideal for: Quick queries where latency matters
✅ Bridge script: Working (authenticated with Max plan)
✅ Direct test: claude --print responds correctly