OpenClaw User Details Setup Challenges and Abandonment After Mac Switch

OpenClaw Installation and Configuration Hurdles

A developer documented their experience attempting to use OpenClaw after switching from Windows to macOS, ultimately deciding to abandon the project due to technical challenges and limited practical utility.

Environment and Setup Issues

The transition from Windows to macOS presented immediate obstacles: differences in window management, command operations, Finder file system, and tools like brew install, npm install, oh my zsh, and tmux ls required significant adaptation.

OpenClaw installation proved more complex than advertised. While the official website presents multiple installation methods (npm, curl, git, bun, etc.), the actual process required: installing Node.js first, then OpenClaw, configuring npm mirror sources for access outside certain networks, and extensive command-line work.

Channel Configuration and Cost Surprises

Configuring communication channels revealed further complications:

• Telegram configuration failed due to SMS verification issues with Chinese phone numbers
• iMessage setup worked initially, allowing basic "hello" responses, but quickly revealed hidden costs
• AI model API expenses became apparent: Kimi-K2.5 charges 4元 for 2.5 million token input and 18元 for output, GLM-5 is more expensive, MiniMax costs 49元 monthly
• Multiple budget plans emerged: Qianwen offers a 7.9元 first-month codePlan, with similar offerings from Volcano and Tencent
• Additional configuration required: setting up URLs, API keys, and cc-switch for managing multiple 9.9元 plan subscriptions

Practical Implementation Failures

Despite getting basic functionality operational, practical use cases consistently failed:

• Automated daily news briefing configured in HEARTBEAT.md delivered incorrect content from unspecified websites
• Feishu multi-bot configuration resulted in nonsensical responses: bots introducing themselves as "小可爱" (little cutie), "小傻瓜" (little fool), or asking "你到底要干啥？" (what exactly do you want to do?)
• Xiaohongshu skill for automatic posting failed at the publish button stage due to either full context windows or infinite loops
• Feishu bots couldn't coordinate, consistently reporting "群成员数1，算上🤖2个" (group member count 1, including bot 2 total)

Limited Working Functionality

The only reliably working features were:

• File operations: finding files and executing copy/move operations via chat interface
• Scheduled daily briefings (though with incorrect content)
• Basic Feishu responses: "Boss好" (Hello boss), "我来了" (I'm here), "你又要干啥？" (What do you want now?)

The developer noted these limited successes didn't justify the time investment, as actual work tasks (PPT preparation, CRUD code, gaming) remained uncompleted.

Technical Issues Identified

Specific bugs and documentation problems were noted:

• OpenClaw 3.13 bug: Management interface chat window displays incorrect context usage (shows cumulative input tokens instead of current context window usage)
• Outdated documentation: Official iMessage configuration instructions are obsolete, with BlueBubbles now recommended instead

The developer expressed appreciation for OpenClaw as a groundbreaking product but cited excessive complexity, hundreds of openclaw gateway commands, countless GitHub/Google tabs, and late-night debugging sessions as reasons for abandonment.