Migrating OpenClaw agents to Claude Code after third-party harness deprecation
Anthropic ended support for third-party harnesses, requiring users to migrate their OpenClaw agents to Claude Code. One developer successfully moved 17 agents (10 platform promo agents and 7 content pipeline crons) running on a Max subscription in about four hours.
Migration steps
The developer created a CLAUDE.md file in each OpenClaw workspace directory as the entry point, telling Claude "you are this agent, read HEARTBEAT.md, follow it step by step." Each file was about 20 lines.
A bash wrapper script was created to run:
claude -p --model sonnet --dangerously-skip-permissionswith output piped to Slack via curl. OpenClaw heartbeats were replaced with macOS crontab entries using the same intervals and schedule.
Technical details
The claude binary is located at ~/.local/bin/claude, which isn't in cron's default PATH. Since cron can't access macOS Keychain, the OAuth token must be set as an environment variable with CLAUDE_CODE_OAUTH_TOKEN in crontab.
The --bare flag breaks authentication for subscription users by skipping OAuth.
The one-liner per agent was:
claude -p --model sonnet --dangerously-skip-permissions --append-system-prompt "You are the Reddit agent. Read CLAUDE.md first, follow HEARTBEAT.md." "Execute your heartbeat."Browser automation
Agents using OpenClaw's CDP browser can continue using the same exec openclaw browser commands if the gateway remains running, or switch to Claude in Chrome or Playwright MCP.
The migration preserved all existing agent logic files: HEARTBEAT.md, PLAYBOOK.md, SOUL.md, and BROWSER-*.md files required zero rewriting.
📖 Read the full source: r/openclaw
👀 See Also
Claude Code LSP Setup Guide: Structural Code Understanding
A Reddit post details how to configure Claude Code to use Language Server Protocol for structural code understanding instead of text matching, reducing query times from 30-60 seconds to ~50ms with go-to-definition, find-references, and call hierarchy features.
Practical fixes for OpenClaw reliability issues
A developer shares eight specific techniques that improved their OpenClaw setup, including a 3-tier memory system with daily logs and a knowledge graph, activation score management, and file-based rule enforcement.
OpenClaw: Your Ultimate Quick Reference Cheatsheet
Dive into the nitty-gritty of OpenClaw with our handy reference cheatsheet. Extract critical features and functionalities to streamline your AI coding experience.
OpenClaw Failure Patterns: 42 Real Incidents in 28 Days
A developer running OpenClaw daily documented 42 specific failures across eight categories, including AI hallucinations, authentication breakdowns, and automation that costs more time than it saves. The source provides concrete examples like Google OAuth 7-day token expiration and Opus 4.6 adding unwanted metadata to files.