OpenClaw setup tips from a user's experience: Gmail MCP, profile flags, and networking issues
OpenClaw setup experience: specific issues and workarounds
A user running OpenClaw for several weeks documented their setup process and encountered issues that cost significant troubleshooting time. They used UTM on a Mac with an Ubuntu VM and bridged networking, implementing Telegram, Slack, Gmail integration, and cron jobs for automated tasks.
Key configuration problems and solutions
The user identified several specific issues:
- The Gmail MCP server ignores the body parameter when sending emails, resulting in blank messages. The workaround is to use html_body instead, which isn't documented.
- Without the --profile prod flag, OpenClaw loads a dev profile with a hardcoded C-3PO identity, causing the agent to ignore user configuration.
- API keys must be placed in auth-profiles.json using the paste-token command. Environment variables, service files, and other config files don't work, leading to cron jobs failing silently with "model not allowed" errors.
- UTM's NAT networking drops HTTPS connections when the Mac sleeps. Switching to bridged networking immediately resolved this issue.
The user noted encountering about 20 similar undocumented issues during setup and documented their experience as a guide with prompts for using ChatGPT or Claude as a deployment assistant.
📖 Read the full source: r/openclaw
👀 See Also
Modifying OpenClaw's default system prompt to bypass content restrictions
A user modified OpenClaw's configuration file to change the default system prompt from "You are a helpful, respectful and honest assistant" to a custom prompt that ignores external safety filters, effectively removing content restrictions. The process involves editing config.js in the node-llama-cpp installation directory.
OpenClaw's Gateway and Skills: Moving Beyond Chat to Automated Execution
OpenClaw's Gateway connects channels like Telegram and WhatsApp to skills that execute real-world actions such as running tests, calling APIs, and managing files, with cron jobs enabling scheduled background automation.
Post-Mortem: Claude Max + OpenClaw Billing Errors from Stale OAuth and Isolated Cron Jobs
OpenClaw agent breaks randomly due to stale OAuth token blacklisting the entire Anthropic provider and isolated cron jobs hitting the Extra Usage bucket. Full fix: remove manual profile, move cron to main session, clear billing lockout.
Replacing OpenClaw's Default Memory with Redis and Qdrant for Production Multi-Agent Systems
A developer replaced OpenClaw's default SQLite memory with Redis for ephemeral state and Qdrant for persistent vector memory to solve scaling issues in multi-agent setups, implementing semantic search, cross-agent sharing, and concurrent writes.