One Month with OpenClaw: Personalization Successes and Stability Challenges

What Worked: Personalized OpenClaw Implementation

After replacing ChatGPT Plus with OpenClaw for approximately one month, several functional implementations were achieved:

• Personalized chatbot: Fed ten years of digital journals from Apple Notes and Obsidian to create USER.md and PERSONAL_MODEL.md files. The PERSONAL_MODEL.md file contains personality traits, communication style, preferences, life goals, and a model of the user, and gets pulled into context for every session.
• Daily check-in agent: Checks calendar, email, and YouTube channels three times daily, filtering YouTube content based on relevance rather than summarizing all subscriptions. Setup involved asking the agent to configure it after providing API access.
• Daily spending report: Monitors API token expenditure after running up a $12 bill in one day. The agent sometimes estimates based on provider pricing instead of OpenClaw logs due to occasional zeroing of stored expenditure data.
• Vibe coding interface: Connected to Claude Code ACP through back-and-forth debugging, allowing OpenClaw to offload coding implementation work to Claude Code.

What Broke: Stability Issues and Workarounds

Several stability challenges emerged during implementation:

• Frequent breakage requiring terminal switching to Claude Code for fixes, particularly for automation work.
• Current workflow pattern: Ask OpenClaw → breaks → ask Claude Code to fix → works temporarily → breaks again → back to Claude Code.
• A job posting scraper that checks multiple websites for relevant jobs never worked consistently despite attempts.
• OpenClaw doesn't feel sufficient to stand alone without Claude Code intervention.

Interface and History Limitations

The user found Discord to be the best UI for OpenClaw compared to Telegram, but misses ChatGPT's one-click new chat conversation history handling.