Migrating from OpenClaw to Cowork + Claude Code: A Developer's Experience

A developer shared their experience migrating from OpenClaw to Anthropic's Cowork with Claude Code sessions. After running OpenClaw for one month with 17 skills, daily automations, and a memory system that "sort of worked," they moved everything to Cowork in a weekend when Anthropic shipped Cowork with dispatch and Claude Code sessions.

Architecture: Cowork as Brain, Claude Code as Hands

Cowork serves as the orchestration layer—receiving instructions, deciding what to route where, running cron jobs, and maintaining memory across conversations. Claude Code handles execution—reading files, writing code, running scripts, and performing git operations. You interact with Cowork, which dispatches to Claude Code when code execution is needed, then returns results.

Three-Layer Context Design

The developer implemented a context system based on the insight that "agent quality is mostly context quality."

• Layer 1: Cowork Global Instructions – Loaded into every conversation via desktop app settings, kept minimal (about 5 lines covering user identity, language, and work habits).
• Layer 2: CLAUDE.md – Located in workspace root, read by Claude Code on startup. This serves as the operating manual (under 200 lines) covering how to work, which files matter, and how memory works.
• Layer 3: context/ folder – Contains user profile, agent personality, and business documents. Not loaded every time—the agent pulls what it needs based on the task.

Workspace Structure

agent-workspace/
├── CLAUDE.md
├── context/
│   ├── USER.md ← User profile & preferences
│   ├── SOUL.md ← Agent personality
│   ├── IDENTITY.md ← Agent identity
│   └── business/ ← Business context docs
├── agents/
│   ├── default.md
│   ├── code-reviewer.md
│   ├── seo-analyst.md
│   └── ceo-agent.md
├── skills/
│   ├── README.md
│   └── x-scanner/
│       ├── SKILL.md
│       └── x-scan.js
├── memory/
├── data/
└── .gitignore

Memory Implementation

The system uses two memory layers:

• Cowork auto-memory – Handles conversation persistence across chats, storing preferences, project context, and resource pointers. Auto-loaded and described as "knowing you as a person."
• Workspace memory/ – Stores daily session logs in the git repo, read by Claude Code during runs. This represents "remembering what was done."

Test Scenarios

The developer tested four scenarios:

• X-KOL Scanner – Dispatched to Claude Code, reads skill config, runs script, scrapes X accounts, finds 135 signals, outputs summary. Set up as a daily 9 AM cron job.
• CEO Strategy Review – Loads agent config plus business context, runs Socratic questioning from four angles (investor, user, competitor, team). With minimal context, it gave generic questions; after adding actual financials and competitive intel, questions became specific enough to be useful.
• Daily Briefing – Cowork handled this entirely by itself—opened Gmail and Calendar via Chrome, pulled inbox and schedule, searched for industry news, compiled briefing. Never dispatched to Claude Code.
• YouTube Clipper – Third-party skill from GitHub that downloads a full podcast (59 minutes), analyzes subtitles for chapter breaks, picks the 3 best segments, clips video, burns in bilingual subtitles. Required debugging subtitle timing offsets in skill config.

Advantages Over OpenClaw

• Real cron jobs – Cowork has actual cron scheduling versus OpenClaw's HEARTBEAT.md checklist that required manual triggering.
• Dispatch routing – Cowork decides whether to handle tasks itself or send to Claude Code, while OpenClaw ran everything through the same path.
• Memory persistence – Cowork remembers things across conversations without instructions, while OpenClaw needed paragraphs of memory management instructions in MEMORY.md and still dropped context.
• Role switching mid-conversation – The developer mentions this capability but the source cuts off mid-sentence.