The Complete Mastery Guide

Claude Chat, CoWork,
Code & OpenClaw

From your first conversation to autonomous agent systems. A structured, step-by-step progression covering the entire Claude ecosystem, designed for someone with zero programming experience.

Claude ChatCoWork11 Code LevelsOpenClawMarch 2026

How This Guide Works

This guide covers the entire Claude ecosystem plus OpenClaw. Start with Claude Chat (the conversational interface everyone uses), then CoWork (the autonomous desktop agent), then the 11-level Claude Code progression (from basic prompting to autonomous loops), and finally OpenClaw (the open-source personal AI agent). Every section includes step-by-step instructions, code examples, knowledge boxes, and interactive checklists.

Claude Chat

The conversational interface to Claude AI. Start here — no coding required.

Setup & Profile

Claude Chat is where most people start. It is available at claude.ai, the Desktop app (Mac/Windows), and the Mobile app (iOS/Android). No terminal, no code — just a conversation.

1

Choose Your Access Point

Claude Chat is available in three places: the browser at claude.ai, the Desktop app (Mac/Windows), and the Mobile app (iOS/Android). The Desktop app is recommended because it includes Cowork and Claude Code. The browser is the simplest way to start.

Tip:Install the Desktop app from claude.com/download — it's free and has features the browser doesn't.
2

Pick Your Plan

Free gives you Sonnet and Haiku with limited messages, plus web search, projects, artifacts, memory, and connectors. Pro ($20/month) adds Opus 4.6, 5x usage, Claude Code, Cowork, Research mode, and Excel/PowerPoint integration. Max ($100-$200/month) adds 5x-20x more usage and priority access.

Plan Comparison
Free  → Sonnet + Haiku, limited messages, no Code/Cowork
Pro   → All models, 5x usage, Code + Cowork ($20/mo)
Max   → 5x-20x Pro usage, priority access ($100-$200/mo)
Tip:Start with Pro. The free plan is fine for exploring, but Pro is where Claude becomes genuinely useful for work.
3

Set Up Your Profile

Go to Settings → General → Profile. Set your name, work function, and personal preferences. These apply to every conversation. Tell Claude how you like to work: your preferred response length, your field, your tools, and your communication style.

Profile Setup
Settings → General → Profile

Example preferences:
"I'm a marketing manager. I prefer concise, 
actionable responses. I work with Google Workspace 
and Slack. Always ask clarifying questions before 
starting complex tasks."
4

Enable All Capabilities

Go to Settings → Capabilities and turn everything ON: Search and reference chats, Generate memory from chat history, Artifacts, AI-powered artifacts, Inline visualizations, Cloud code execution and file creation. Set Tool access to 'Load tools when needed'.

Capabilities Checklist
Settings → Capabilities → Turn ON:
✓ Search and reference chats
✓ Generate memory from chat history
✓ Artifacts
✓ AI-powered artifacts
✓ Inline visualizations
✓ Cloud code execution and file creation
✓ Tool access → "Load tools when needed"
Tip:These are off by default. If you skip this step, you'll miss most of what Claude can do.

Models & Capabilities

Claude offers multiple models, each optimized for different tasks. Understanding when to use each one is key to getting the best results.

5

Understand the Models

Sonnet is the default workhorse — fast, smart, handles most tasks. Opus is the most powerful — deeper reasoning, complex multi-step tasks, but slower and uses more quota. Haiku is lightweight — very fast for simple questions. Both Opus and Sonnet support Extended Thinking, which lets Claude reason through problems before responding.

Model Comparison
Opus 4.6  → 1M context, 128k output, best reasoning
Sonnet 4.6 → 1M context, 64k output, best value
Haiku 4.5  → 200k context, fastest speed
Tip:Keep Extended Thinking on. It makes Claude significantly better at complex tasks with minimal speed cost.
6

Master the Chat Interface

The + button in the chat input bar gives you access to: file uploads (PDFs, images, spreadsheets, code), web search toggle, Research mode (deep multi-source research that runs in background), Writing Styles (presets for different tones), and Connectors (pull from Google Drive, Gmail, Slack, etc.).

Artifacts & Output

Artifacts are Claude's way of producing persistent, shareable, editable output — documents, code, apps, and visualizations that live alongside your conversation.

7

Use Artifacts

Artifacts appear in a side panel next to your conversation. They hold anything substantial Claude creates: documents, code, interactive apps, websites, dashboards, and visualizations. You can copy, download, share with a link, iterate, or fork them into variations. With AI-powered artifacts enabled, Claude can build apps that use AI themselves.

Tip:Ask Claude to 'create an artifact' for anything you want to keep, edit, or share. Artifacts are persistent — chat messages scroll away.

Projects & Memory

Projects let you organize conversations around a topic with custom instructions and knowledge files. Memory persists your preferences across all conversations.

8

Create Your First Project

Click Projects in the sidebar → Create new project → Give it a name → Add custom instructions (tell Claude what this project is about, how to approach it) → Upload knowledge files (documents, style guides, references). Every conversation inside the project starts with this context. Memory builds across all conversations in the same project.

Project Setup Example
Projects → New Project → "Client Work"

Custom Instructions:
"You are helping me manage client deliverables.
Always use formal tone. Reference the brand 
guidelines in the uploaded files. Ask before 
making assumptions about deadlines."

Knowledge Files:
→ Upload brand_guidelines.pdf
→ Upload project_timeline.xlsx

Connectors & Skills

Connectors pull live data from your tools (Google Drive, Gmail, Slack, Notion, etc.). Skills give Claude specialized expertise for specific tasks.

9

Set Up Writing Styles

Go to Settings → Styles to create presets for different types of writing. Apply them per conversation from the + menu. Think of them as tone presets: one for formal client emails, one for casual social posts, one for technical documentation.

Writing Styles
Settings → Styles → Create New

Example styles:
• "Client Email" → Formal, concise, professional
• "Social Post" → Casual, engaging, short
• "Technical Doc" → Precise, structured, detailed
10

Connect Your Tools

Go to Customize → Connectors and connect the tools you use: Google Drive, Gmail, Calendar, Slack, Notion, Canva, Gamma, and more. Each takes about 30 seconds — authorize by logging into that platform. Once connected, toggle them on/off per conversation from the + menu.

Tip:Connect Google Drive and Gmail first. These are the most immediately useful connectors for most people.

What is Claude Chat?

Claude Chat is the conversational interface to Anthropic's Claude AI, available at claude.ai, the Desktop app, and the Mobile app. It's where you have conversations, create projects, generate artifacts, and access all of Claude's features through a visual interface — no terminal required.

Inline Visualizations (NEW March 2026)

Claude can now build interactive charts, diagrams, flowcharts, and timelines right inside the conversation. Sometimes it does this automatically; you can also ask directly: 'draw this as a diagram' or 'chart this data'. Save them as images or convert to artifacts.

Try it at claude.ai

1 Million Token Context Window

As of March 2026, Opus 4.6 and Sonnet 4.6 support 1 million token context windows — roughly 750,000 words in a single conversation. This means you can process entire codebases, year-long document histories, or hundreds of contracts in one session.

Memory is Persistent

Claude remembers your name, preferences, work context, and style across conversations. You control what it remembers. Go to Settings → Memory to view, edit, or delete anything. Memory is now available to ALL users including the free tier.

Research Mode

Research mode searches multiple sources, cross-references findings, and produces a detailed report with citations. It runs in the background (5-45 minutes) so you can keep working. Think of it as Claude's version of deep research.

Claude in Chrome, Excel, and PowerPoint

The Chrome extension lets Claude see and interact with your current webpage. In Excel, Claude reads workbooks, suggests formulas, and creates charts. In PowerPoint, it reads your templates and creates on-brand presentations. All available on paid plans.

Skills in Claude Chat

Skills are pre-built instruction sets that give Claude specialized expertise. They work everywhere: chat, projects, Cowork, and Code. Create them in the Desktop app under Customize → Skills. There's a 50-skill limit, so prioritize your own custom skills over community ones.

Claude Chat Learning Checklist

Learning Checklist

0% Complete
Initial Setup
Chat Mastery
Artifacts & Output
Projects & Personalization

Claude CoWork

Claude's autonomous desktop agent. Delegate tasks and let Claude work independently.

What is CoWork?

CoWork is Claude's autonomous mode. You give it a task, it breaks it into steps, reads and creates files, pulls in your skills and connectors, and delivers the finished work. Think of it as delegating to a capable assistant who has access to your computer.

1

Understand What CoWork Is

CoWork is Claude's autonomous mode — it works independently on your behalf. You give it a task, it breaks it into steps, reads and creates files, pulls in your skills and connectors, and delivers the finished work. Think of it as delegating to a capable assistant who has access to your computer.

Tip:CoWork requires a paid plan (Pro or Max). It's available in the Desktop app only — not in the browser.
2

Install and Update Claude Desktop

CoWork runs inside the Claude Desktop app. Download or update to the latest version from claude.com/download. Make sure you're on macOS or Windows x64. Your computer must be awake and the app must be open for Claude to work on tasks.

CoWork Requirements
# Download from:
https://claude.com/download

# Requirements:
• macOS or Windows x64
• Pro or Max plan
• Computer must be awake
• Desktop app must be open
3

Switch to the CoWork Tab

In the Desktop app, you'll see tabs at the top: Chat, Cowork, and Code. Click Cowork to enter the autonomous mode. Give it a task and be clear about what you want — like you would when delegating to a person. Then come back when it's done.

Starting a CoWork Task
Desktop App → Cowork tab

Example task:
"Create a competitive analysis of the top 5 
project management tools. Compare pricing, 
features, and user reviews. Output as a 
formatted spreadsheet."

Dispatch (Phone + Desktop)

Dispatch creates one continuous conversation between your phone and desktop. Assign a task from your phone, Claude works on your desktop, and pushes a notification when done.

4

Set Up Global Instructions

Go to Settings → Cowork → Global Instructions. This is where you tell Claude how you like to work. Your preferred document format, communication style, default tools, and any standing rules. These apply to every CoWork task.

Global Instructions
Settings → Cowork → Global Instructions

Example:
"Always save files to my ~/Documents/Claude/ folder.
Use formal tone for all documents.
Prefer Google Sheets over Excel.
Ask before deleting any files.
Summarize what you did at the end of each task."
Tip:Folder-specific instructions also exist. When you select a local folder, those instructions apply only when working in that folder.
5

Set Up Dispatch (Phone + Desktop)

Dispatch gives you one continuous conversation with Claude that syncs across your phone and desktop. Assign a task from your phone, Claude works on your desktop, and messages you the result. Open Cowork → click 'Dispatch' in the left panel → click 'Get started' → toggle on file access and keep-awake → click 'Finish setup'.

Dispatch Setup
Setup steps:
1. Update Claude Desktop (latest version)
2. Update Claude Mobile app (iOS/Android)
3. Open Cowork → click "Dispatch"
4. Click "Get started"
5. Toggle ON: file access + keep awake
6. Click "Finish setup"
7. Start messaging from phone or desktop
Tip:After setup, your conversation syncs automatically. Message from your phone on the commute, follow up from desktop when you sit down.

Computer Use

Computer Use lets Claude interact directly with your screen — clicking, typing, and navigating desktop apps. This is a research preview with safety guardrails.

6

Enable Computer Use

Computer Use lets Claude interact directly with your screen — clicking, typing, and navigating desktop apps. Go to Settings → General → Computer use toggle → ON. Claude will ask permission before accessing each app. It prioritizes: 1) Connectors (fastest), 2) Browser via Claude in Chrome, 3) Direct screen interaction.

Computer Use Setup
Settings → General → Computer use → ON

Priority order:
1. Connectors (Gmail, Slack, etc.) → fastest
2. Browser (Claude in Chrome) → medium
3. Screen interaction → slowest, most flexible

Claude asks permission for each new app.
Tip:Start with simple tasks. Close sensitive apps (banking, healthcare) before enabling computer use.

Plugins & Scheduling

Plugins turn CoWork into a specialist. Scheduled tasks let Claude run recurring work automatically.

7

Install Plugins

Plugins bundle skills, connectors, and commands into specialized packages. They turn CoWork into a specialist for marketing, sales, finance, or whatever your work requires. Go to Customize → Plugins → click + → browse and install Anthropic's plugins, or create your own.

Plugin Installation
Customize → Plugins → + button

Available plugin categories:
• Writing & Content
• Marketing & Social
• Sales & CRM
• Finance & Analytics
• Development & DevOps
• Custom (build your own)
8

Set Up Scheduled Tasks

Type /schedule in any Cowork chat to create a recurring task. Set the recurrence and Claude runs it automatically. Manage all scheduled tasks in the Scheduled section of Cowork. Examples: daily email summary, weekly metrics report, Friday team briefing.

Scheduled Tasks
# In any Cowork chat, type:
/schedule

# Then describe the task:
"Every Monday at 9am, pull my calendar for the week,
check unread emails, and create a briefing document
with priorities and deadlines."

# Manage tasks:
Cowork → Scheduled section → view/edit/delete
Tip:Your computer must be awake and the Desktop app open for scheduled tasks to run. Consider enabling keep-awake in Dispatch settings.
9

Understand Memory in CoWork

CoWork has persistent memory — Claude learns how you work and retains context across sessions. Sensitive data (passwords, financial details, health info) is excluded automatically. You can view, edit, and delete what Claude remembers at any time in Settings.

Memory Management
Settings → Memory

• View all stored memories
• Edit individual memories
• Delete specific memories
• Toggle memory on/off

Sensitive data is automatically excluded:
✗ Passwords
✗ Financial details
✗ Health information

What is Claude CoWork?

CoWork is Claude's autonomous desktop agent, launched January 12, 2026 as a research preview. You give Claude access to a folder, it reads files, executes multi-step workflows, and produces deliverables independently. No coding required. It's the non-developer equivalent of 'vibe coding' — Anthropic calls it 'vibe working'.

Dispatch: Phone-to-Desktop (NEW March 2026)

Dispatch creates one continuous conversation between your phone and desktop. Assign a task from your phone while commuting, Claude works on your desktop, and pushes a notification when done. Development tasks route to Claude Code; knowledge work routes to Cowork. Same context, same memory, wherever you are.

Official Dispatch Guide

Computer Use: Research Preview

Computer Use lets Claude navigate your screen directly — clicking, typing, opening apps. It runs OUTSIDE the CoWork sandbox, meaning Claude interacts with your actual desktop. Per-app permissions, an app blocklist, and action review provide safeguards, but this is still early. Don't use it with banking, healthcare, or sensitive apps.

Computer Use Safety Guide

CoWork vs. Claude Code

CoWork is for knowledge workers who don't code. Claude Code is for developers. When you assign a task via Dispatch, Claude automatically routes development tasks to Code and knowledge work to Cowork. They share the same memory, skills, and connectors.

Safety: Think Before You Connect

Giving a mobile AI agent remote control of a desktop AI agent creates a chain where instructions from your phone trigger real actions on your computer. This includes reading, moving, or deleting files, interacting with connected services, and controlling your browser. Only connect agents if you're comfortable with what they COULD do, not just what you intend.

Current Limitations

CoWork is a research preview. Your desktop must be active (awake, app open). Computer use runs outside the sandbox. There's only one continuous thread (no multiple threads). Complex tasks sometimes need a second try. Screen interaction is slower than connectors.

Claude CoWork Learning Checklist

Learning Checklist

0% Complete
Initial Setup
Dispatch (Phone + Desktop)
Task Mastery
Advanced Features
Part 0

Foundational Knowledge

Before diving into the tools, build a solid understanding of the essential concepts.

Foundations

The Command-Line Interface (CLI)

The command-line interface is a text-based way to interact with your computer. On a Mac, this is done through Terminal. Instead of clicking icons, you type commands.

How to Open Terminal on Your Mac

Press Cmd + Space to open Spotlight, type "Terminal", and press Enter.

Basic Terminal Commands
ls        # List files and folders
pwd       # Show current directory
cd folder # Navigate to a folder
cd ..     # Move up one level

Node.js & npm

Node.js is a runtime that lets you run JavaScript outside a browser. npm comes bundled with it and is used to install packages.

Checking Node.js
node --version   # Check Node.js
npm --version    # Check npm
# Download from: https://nodejs.org/

APIs & API Keys

An API allows software to communicate with other software. An API Key authenticates you. Keep it secret.

Where to Get API Keys

Anthropic: console.anthropic.com | OpenAI: platform.openai.com

Daemons (Background Services)

A daemon is a program that runs in the background. OpenClaw runs as a daemon so it is available 24/7.

Self-Hosted vs. Cloud-Hosted

Cloud-Hosted means software runs on a company's servers. Self-Hosted means you run it on your own machine. OpenClaw is self-hosted. Claude Code is cloud-hosted.

Open Source Software

Open-source software has source code anyone can inspect. OpenClaw is open source (MIT License). Claude Code is proprietary.

Beginner Tier

Levels 0-2: Get installed, configured, and connected to external tools.

0
Beginner — Level 0

Basic Prompting

You type prompts and hope for the best.

At Level 0, you install Claude Code and learn to have a basic conversation with it. You have no configuration, no memory, and no customization. Every session starts from scratch.

1

Install Claude Code

Open your Mac Terminal and run the install command. You need Node.js 18+ installed.

Install Command
npm install -g @anthropic-ai/claude-code
If you get a permission error, prefix with sudo. If you don't have Node.js: brew install node
2

Launch Claude Code

Navigate to any project folder, then type claude and press Enter.

Launch
cd ~/my-project
claude
3

Ask your first question

Inside the session, type a natural-language prompt. Claude reads your project files and responds.

Example Prompt
You: "What does this project do?"
4

Understand permissions

Claude asks for permission before editing files or running commands. Always review before approving.

Permission Prompt
Claude wants to run: npm test

  [Allow] [Deny] [Allow always]
5

Learn basic slash commands

Type slash commands for quick actions. Memorize these to start.

Essential Commands
/help     - Show all commands
/clear    - Clear conversation
/cost     - Show token usage
/model    - Switch AI models
/compact  - Compress context
/quit     - Exit

What is Claude Code?

Claude Code is an agentic coding tool by Anthropic that lives in your terminal. It runs on your machine, sees your files, runs commands, and edits your code directly.

What is a context window?

Every AI model has a limit on how much text it can process at once. Claude's is up to 200,000 tokens. Every file read, message, and response consumes tokens.

Tokens cost money

Claude Code uses API tokens which cost money. Use /cost frequently. A typical session costs $0.50-$5.00. The /compact command reduces costs.

Learning Checklist

0% Complete
Setup
First Usage
1
Beginner — Level 1

CLAUDE.md & Slash Commands

You have a CLAUDE.md file. You know /compact and /cost.

At Level 1, you give Claude persistent memory. The CLAUDE.md file is a markdown document Claude reads at the start of every session containing your project's rules, coding standards, and architecture decisions.

1

Generate CLAUDE.md with /init

Run /init inside a Claude Code session. Claude scans your codebase and creates a CLAUDE.md.

Generate CLAUDE.md
cd ~/my-project
claude

# Inside the session:
/init
2

Understand CLAUDE.md locations

CLAUDE.md files can live in several locations. Project-level is shared via git. User-level is personal.

File Locations
# Project-level (shared with team)
./CLAUDE.md

# User-level (personal, all projects)
~/.claude/CLAUDE.md
3

Write effective instructions

Keep it under 200 lines. Use markdown headers and bullets. Be specific.

Example CLAUDE.md
# Project: My App

## Build & Test
- Install: `npm install`
- Dev: `npm run dev`
- Test: `npm test`

## Code Standards
- TypeScript strict mode
- 2-space indentation
- Named exports over defaults
4

Use @imports for references

Reference other files with @path/to/file syntax to keep CLAUDE.md concise.

@imports
# In CLAUDE.md:
See @README.md for overview.
See @docs/api-guide.md for API docs.
5

Master auto memory

Claude writes notes for itself based on your corrections. Stored at ~/.claude/projects/<project>/memory/.

Auto Memory
# View auto memory:
/memory

# Browse files:
ls ~/.claude/projects/my-project/memory/
When you correct Claude - 'No, always use pnpm' - it saves that automatically.

CLAUDE.md is context, not enforcement

CLAUDE.md is loaded into the context window. The more specific your instructions, the more consistently Claude follows them.

What /compact actually does

When you run /compact, Claude summarizes the conversation into compressed form, freeing context space. It then re-reads CLAUDE.md from disk fresh.

The .claude/rules/ directory

For larger projects, organize instructions into .claude/rules/ files. Rules can be scoped to specific file paths using YAML frontmatter.

Learning Checklist

0% Complete
CLAUDE.md Mastery
Slash Commands
2
Beginner — Level 2

MCP Servers

You connected MCP servers. Slack, Notion, Drive - pulling live data.

The Model Context Protocol (MCP) is an open standard that connects Claude Code to external tools, databases, and APIs. By adding MCP servers, Claude can read Notion docs, send Slack messages, query databases, and more.

1

Understand what MCP is

MCP servers are plugins that give Claude new abilities. Each server exposes tools Claude can call.

MCP Capabilities
# MCP gives Claude the ability to:
# - Read/write Notion pages
# - Send/read Slack messages
# - Query databases
# - Pull Figma designs
# - Create GitHub PRs
2

Add your first MCP server

Run this in your regular terminal (not inside Claude Code).

Add Notion
claude mcp add --transport http notion \
  https://mcp.notion.com/mcp
3

Add more servers

Each server is a single command. Only install the ones you use.

Popular Servers
# Slack
claude mcp add slack --transport http \
  https://mcp.slack.com/mcp

# GitHub
claude mcp add --transport http github \
  https://api.githubcopilot.com/mcp/

# Context7 (library docs)
claude mcp add --transport http context7 \
  https://mcp.context7.com/mcp
4

Manage your servers

View, test, and remove servers with these commands.

Manage
# List all servers
claude mcp list

# Remove a server
claude mcp remove notion
5

Use MCP in practice

Just ask Claude to do things that require those tools. It knows which server to use.

Example Prompts
"Find the latest design specs in Figma
 and implement the button component."

"Read the PRD from Notion and create
 GitHub issues for each feature."

Security warning

Use third-party MCP servers at your own risk. Anthropic has not verified all servers. Be careful with servers that fetch untrusted content.

What is OAuth?

When you add a remote MCP server, Claude opens a browser for you to log in and grant permissions. This is OAuth - the same 'Sign in with Google' flow.

Learning Checklist

0% Complete
MCP Servers

Intermediate Tier

Levels 3-5: Build repeatable workflows, manage context, and orchestrate subagents.

Claude Code
3
Intermediate — Level 3

Custom Skills

You built custom skills. Repeatable workflows, one command.

Skills are reusable workflow templates stored as Markdown files. They let you package complex, multi-step processes into a single command.

1

Understand what a skill is

A skill is a Markdown file with optional YAML frontmatter that defines a reusable workflow.

Example Skill
# File: .claude/skills/deploy.md
---
name: deploy
description: Deploy the app
---

## Steps
1. Run `npm run build`
2. Run `npm test` - abort if fail
3. Run `npm run deploy`
4. Verify at production URL
2

Create the skills directory

Create the directory structure for project or personal skills.

Create Directory
# Project skills (shared)
mkdir -p .claude/skills

# Personal skills (all projects)
mkdir -p ~/.claude/skills
3

Write your first skill

Create a simple skill that automates a common task.

Code Review Skill
# .claude/skills/code-review.md
---
name: code-review
description: Review staged changes
---

Review staged git changes:
1. Run `git diff --staged`
2. Check for security, performance,
   error handling, style issues
3. Provide summary with severity
4

Invoke a skill

Inside a Claude Code session, invoke your skill with the / prefix.

Invoke Skills
# Inside Claude Code session:
/deploy
/code-review
5

Add supporting files

Skills can include templates and scripts in a subdirectory.

Supporting Files
.claude/skills/
  generate-api/
    generate-api.md  # The skill
    template.ts      # Template
    schema.json      # Config

Skills vs. CLAUDE.md

CLAUDE.md is always-on context loaded every session. Skills are on-demand. Use CLAUDE.md for rules; use skills for specific workflows.

Frontmatter options

Skills support YAML frontmatter with fields like name, description, tools (restrict tools), model (specific model), and invocation (user, agent, or both).

Learning Checklist

0% Complete
Custom Skills
4
Intermediate — Level 4

Context Engineering

You have memory files, patterns, examples. Context engineering.

Context engineering is the art of curating the optimal set of tokens in Claude's context window. Instead of just writing better prompts, you manage the entire information environment.

1

Understand the attention budget

LLMs have an attention budget that gets stretched thin with more tokens. The goal is finding the smallest possible set of high-signal tokens.

Attention Budget
# Context window: ~200,000 tokens
# Sweet spot: 20,000-80,000 tokens
# Above that: diminishing returns
# Near limit: significant degradation
2

Create topic-specific memory files

Split knowledge into topic files. Claude loads MEMORY.md automatically and pulls topic files on demand.

Topic Memory Files
# ~/.claude/projects/my-app/memory/
MEMORY.md              # Index
debugging-patterns.md  # On demand
api-conventions.md     # On demand
test-strategies.md     # On demand
3

Store code style examples

Show Claude examples of your preferred style with good and bad patterns.

Style Examples
# .claude/rules/react-patterns.md
---
globs: ["src/components/**/*.tsx"]
---

Good:
```tsx
export function UserCard({ user }: Props) {
  return <Card>...</Card>;
}
```

Bad:
```tsx
export default function(props: any) {
  return <div>...</div>;
}
```
4

Use path-scoped rules

Rules with glob patterns only load when Claude works with matching files.

Path-Scoped Rules
# .claude/rules/api-routes.md
---
globs: ["src/api/**/*.ts"]
---
All API routes must:
- Validate input with Zod
- Return typed responses
- Include error handling
5

Practice the smallest context principle

Before adding anything to context, ask: 'Does Claude actually need this right now?'

Context Audit
# Audit your context:
# 1. Is this still relevant?
# 2. Can this be a scoped rule?
# 3. Can this be a skill (on-demand)?
# 4. Is this duplicating other context?

Context rot

As the context window fills, Claude's ability to recall information decreases. This is why /compact exists and why you should keep context lean.

The three context strategies

1) Naive drop-in: Load everything upfront. 2) Retrieval-based: Pull context on demand. 3) Hybrid: Core rules upfront, specialized knowledge on demand. The hybrid approach is best.

Anthropic's Context Engineering Guide

Learning Checklist

0% Complete
Context Engineering
5
Intermediate — Level 5

Subagents & Chaining

Multi-phase skills. Subagents. Systems that chain together.

Subagents are specialized AI assistants that run in their own context window within your Claude Code session. Each has a custom system prompt, specific tool access, and independent permissions.

1

Understand subagent architecture

Subagents run inside your session but with their own context. They report results back to the main agent but don't talk to each other.

Built-in Subagents
# Built-in subagents:
# Explore - Fast, read-only (Haiku model)
# Plan    - Creates structured plans
# General - Handles delegated tasks
2

Create a custom subagent

Subagents are Markdown files with YAML frontmatter stored in .claude/agents/.

Custom Subagent
# .claude/agents/code-reviewer.md
---
name: code-reviewer
description: Reviews code for quality
tools:
  - Read
  - Glob
  - Grep
model: sonnet
---
You are a code reviewer. Focus on:
- Security vulnerabilities
- Performance issues
- Error handling gaps
3

Use the Explore subagent

The built-in Explore subagent uses the fast Haiku model for quick codebase searches. It is read-only and costs much less.

Explore
# Claude uses Explore automatically:
"Where is the authentication middleware?"
"Find all files that import User model."
4

Chain subagent output

The output of one subagent can feed into another task, creating multi-phase workflows.

Chaining
# Multi-phase skill:
# Phase 1: Explore scans codebase
# Phase 2: code-reviewer reviews each
# Phase 3: Main agent implements fixes
# Phase 4: Run tests to verify
5

Configure subagent permissions

Control what subagents can do with frontmatter fields.

Permissions
---
name: safe-researcher
tools: [Read, Glob, Grep]
disallowedTools: [Edit, Bash]
permissionMode: plan
maxTurns: 20
---

Subagent context isolation

Each subagent gets its own fresh context window. It does not see your main conversation. You must provide all necessary information in the delegation prompt.

Cost implications

Each subagent consumes its own tokens. A session with 3 subagents uses roughly 4x the tokens of a single session. Use the Explore subagent (Haiku) for cheap read-only tasks.

Learning Checklist

0% Complete
Subagents & Chaining

Advanced Tier

Levels 6-8: Programmatic control, browser automation, and parallel agent teams.

Advanced
6
Advanced — Level 6

Headless Mode

Scripts calling Claude Code. JSON piping.

Headless mode lets you run Claude Code from shell scripts, CI/CD pipelines, and other programs without an interactive terminal. You pass a prompt, get structured output, and pipe it into the next step. This is where Claude Code becomes a programmable tool.

1

Run a one-shot prompt

The -p flag runs Claude with a single prompt and exits. No interactive session.

One-Shot
# Simple one-shot
claude -p "Explain what this project does"

# With a specific model
claude -p "Summarize README.md" --model sonnet
2

Get JSON output

Use --output-format json to get structured, parseable output instead of plain text.

JSON Output
# JSON output
claude -p "List all TODO comments" \
  --output-format json

# Stream JSON messages
claude -p "Analyze this file" \
  --output-format stream-json
3

Use JSON schemas for typed extraction

Force Claude to return data matching a specific schema.

JSON Schema
claude -p "Extract all API endpoints" \
  --output-format json \
  --json-schema '{
    "type": "object",
    "properties": {
      "endpoints": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "method": {"type":"string"},
            "path": {"type":"string"}
          }
        }
      }
    }
  }'
4

Pipe into other commands

Chain Claude's output with standard Unix tools.

Piping
# Pipe to jq for filtering
claude -p "List files" --output-format json \
  | jq '.result'

# Pipe to another script
claude -p "Generate SQL migration" \
  | psql my_database

# Use in a bash script
RESULT=$(claude -p "What is the main entry?")
echo "Entry point: $RESULT"
5

Control tool access for CI/CD

Use --allowedTools to restrict what Claude can do in automated environments.

Tool Restrictions
# CI/CD safe mode - read only
claude -p "Review this PR" \
  --allowedTools Read,Glob,Grep \
  --output-format json

# Allow specific tools
claude -p "Fix linting errors" \
  --allowedTools Read,Edit,Bash
6

Resume sessions

Continue a previous session or the most recent one.

Resume
# Resume last session
claude --resume

# Resume specific session
claude --resume session_abc123

Headless = non-interactive

In headless mode, Claude cannot ask you questions. It must complete the task autonomously. Make your prompts very specific and include all necessary context.

Max turns

Use --max-turns to limit how many steps Claude takes. This prevents runaway sessions in CI/CD. Default is unlimited in interactive mode.

Learning Checklist

0% Complete
Headless / Programmatic Mode
7
Advanced — Level 7

Playwright Browser Control

Screenshots, scraping, PDF generation.

By connecting the Playwright MCP server, Claude Code gains the ability to control a real web browser. It can navigate to URLs, click buttons, fill forms, take screenshots, scrape data, and generate PDFs. This turns Claude into a web automation powerhouse.

1

Install the Playwright MCP server

Add the Playwright MCP server to Claude Code. This gives Claude browser control tools.

Install
# Install Playwright MCP
npx @anthropic-ai/claude-code mcp add \
  playwright \
  --transport stdio \
  -- npx @playwright/mcp@latest
2

Navigate and screenshot

Ask Claude to visit a URL and take a screenshot.

Navigate
# In a Claude Code session:
"Navigate to https://example.com and
 take a screenshot of the homepage."

"Go to our staging site and screenshot
 the login page on mobile viewport."
3

Scrape data from websites

Claude can read page content, extract data, and save it to files.

Scraping
"Go to our competitor's pricing page
 and extract all plan names and prices
 into a JSON file."

"Scrape the top 10 results from
 Hacker News and summarize them."
4

Fill and submit forms

Claude can interact with web forms like a real user.

Forms
"Go to our signup page, fill in test
 data, and verify the form submits
 without errors."

"Log into the admin panel and check
 if there are any pending approvals."
5

Generate PDFs

Claude can render pages and save them as PDFs.

PDFs
"Navigate to our invoice page for
 order #12345 and save it as a PDF."

"Generate a PDF report of the
 analytics dashboard."

Browser runs locally

Playwright runs a real Chromium browser on your machine. It is not headless by default, so you can watch Claude interact with pages. This is great for debugging.

Authentication

For sites that require login, you can pre-authenticate in the browser or ask Claude to log in with test credentials. Never share production passwords with Claude.

Learning Checklist

0% Complete
Playwright Browser Control
8
Advanced — Level 8

Agent Teams

Parallel sessions. Orchestrator + specialist agents.

Agent Teams let you run multiple Claude Code instances simultaneously, each working on a different part of your project. An orchestrator agent coordinates the work, while specialist agents handle focused tasks in parallel. This is like having a team of developers.

1

Enable Agent Teams

Set the environment variable to enable the experimental feature.

Enable
# Enable agent teams
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

# Add to your shell profile for persistence:
echo 'export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1' \
  >> ~/.zshrc
2

Start a team session

Launch Claude Code and ask it to work with teammates.

Start Team
claude

# Inside the session:
"I need you to work with 2 teammates.
 Agent A: Implement the user API.
 Agent B: Write tests for the API.
 You: Coordinate and review."
3

Choose a display mode

Control how teammate output is shown.

Display Modes
# Inline (default) - output in main terminal
# tmux - each agent in a tmux pane
# hidden - agents work silently

# Set in .claude/settings.json:
{
  "agentTeams": {
    "display": "tmux"
  }
}
4

Assign focused tasks

Each teammate gets a specific, well-defined task. The orchestrator coordinates.

Task Assignment
"Create a team of 3:

 Teammate 1 (Frontend):
   Build the React components for
   the dashboard page.

 Teammate 2 (Backend):
   Create the API endpoints for
   dashboard data.

 Teammate 3 (Tests):
   Write integration tests for
   the dashboard feature."
5

Run parallel code reviews

Use teams for parallel review of different parts of a codebase.

Parallel Review
"Review this PR with 3 specialists:
 Agent 1: Security review
 Agent 2: Performance review
 Agent 3: Code style review

 Combine all findings into one report."

Experimental feature

Agent Teams is experimental as of March 2026. Enable it with the environment variable. Behavior may change in future releases.

Cost multiplier

Each teammate is a separate Claude session consuming its own tokens. A 3-agent team costs roughly 3-4x a single session. Use teams for large, parallelizable tasks where the time savings justify the cost.

Coordination overhead

The orchestrator agent spends tokens coordinating. For small tasks, a single agent is faster and cheaper. Teams shine on tasks that take 30+ minutes sequentially.

Learning Checklist

0% Complete
Parallel Agent Teams

Expert Tier

Levels 9-10: Background agents, autonomous loops, and agents that build agents.

9
Expert — Level 9

Cron Jobs & Background Agents

Background agents running 24/7. Claude Code as infrastructure.

At Level 9, Claude Code runs on a schedule without you. It monitors your codebase, runs nightly reviews, generates reports, and responds to events. Claude becomes infrastructure that works while you sleep.

1

Use the /loop command

Schedule a recurring prompt inside a Claude Code session.

/loop Command
# Inside Claude Code session:
/loop every 4 hours: Check for new
  GitHub issues labeled 'bug' and
  create a summary in BUGS.md
2

Set one-time reminders

Schedule a task for a specific time.

Reminders
/remind at 5pm: Run the test suite
  and email me the results.

/remind in 2 hours: Check if the
  deployment completed successfully.
3

Manage scheduled tasks

List and cancel scheduled tasks.

Manage Tasks
/tasks          # List all scheduled
/tasks cancel 3  # Cancel task #3
4

GitHub Actions cron workflow

Run Claude Code on a schedule using GitHub Actions for maximum durability.

GitHub Actions Cron
# .github/workflows/nightly-review.yml
name: Nightly Code Review
on:
  schedule:
    - cron: '0 2 * * *'  # 2 AM daily
jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm i -g @anthropic-ai/claude-code
      - run: |
          claude -p "Review all changes
          from the last 24 hours.
          Create a summary report." \
          --output-format json \
          --allowedTools Read,Glob,Grep \
          > report.json
    env:
      ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
5

Desktop scheduled tasks

For tasks that need your local environment, use Claude Desktop's scheduled tasks feature.

Desktop Scheduling
# Claude Desktop supports:
# - Scheduled prompts at specific times
# - Recurring tasks (daily, weekly)
# - Tasks survive app restarts
# - Access to all your MCP servers

Durability matters

In-session /loop tasks die when the session ends. For production scheduling, use GitHub Actions, cron jobs, or Claude Desktop's scheduled tasks. These survive restarts.

Cost control

Background agents can accumulate significant costs. Always set --max-turns and use --allowedTools to prevent runaway sessions. Monitor with /cost or API usage dashboards.

Learning Checklist

0% Complete
Cron & Background Agents
10
Expert — Level 10

Autonomous Loops

Agents that build agents. A handful of people on the planet.

Level 10 is the frontier. You build systems where Claude Code agents operate autonomously for extended periods, create their own skills, spawn their own subagents, and even generate new agents. This is meta-programming with AI — building systems that build systems.

1

Understand the Ralph Loop

The Ralph Loop is a pattern where Claude Code runs continuously, checking for work, executing it, and looping back. Named after an early practitioner.

Ralph Loop
# The Ralph Loop pattern:
# 1. Check for new work (GitHub issues,
#    Slack messages, file changes)
# 2. Prioritize and plan
# 3. Execute the highest-priority task
# 4. Commit results and report
# 5. Loop back to step 1

# Implementation:
while true; do
  claude -p "Check GitHub for new issues
    labeled 'auto'. Pick the highest
    priority one. Implement it. Create
    a PR. Move to next." \
    --allowedTools Read,Edit,Bash,Glob,Grep \
    --max-turns 50
  sleep 300  # Wait 5 minutes
done
2

Run multi-hour autonomous sessions

Give Claude a large task and let it work autonomously for hours.

Autonomous Session
# Long-running autonomous task:
claude -p "Refactor the entire auth
  module to use the new token system.
  1. Read all auth-related files
  2. Create a migration plan
  3. Implement changes file by file
  4. Update all tests
  5. Run full test suite
  6. Fix any failures
  7. Create a detailed PR description" \
  --max-turns 200 \
  --allowedTools Read,Edit,Bash,Glob,Grep
3

Build skills that generate skills

Create a meta-skill that analyzes your workflow and generates new skills.

Meta-Skill
# .claude/skills/skill-generator.md
---
name: skill-generator
description: Generates new skills
---

Analyze the user's recent Claude Code
sessions (from memory files) and:
1. Identify repeated patterns
2. For each pattern, generate a skill
3. Save to .claude/skills/
4. Test each skill with a dry run
5. Report what was created
4

Create orchestration systems

Build a master agent that coordinates multiple specialized agents.

Orchestrator
# orchestrator.sh
#!/bin/bash
# Master orchestrator that runs nightly

# Phase 1: Triage
claude -p "Review all open issues and
  categorize by: bug, feature, docs" \
  --output-format json > triage.json

# Phase 2: Assign to specialists
for issue in $(jq -r '.bugs[]' triage.json); do
  claude -p "Fix bug: $issue" \
    --max-turns 30 &
done
wait

# Phase 3: Review all changes
claude -p "Review all uncommitted changes
  and create a summary PR"
5

Deploy Claude Code as infrastructure

Run Claude Code as a service that responds to events.

Event-Driven
# Event-driven architecture:
# 1. GitHub webhook triggers
# 2. Script receives event
# 3. Claude Code processes it
# 4. Results posted back

# Example: Auto-review every PR
# In GitHub Actions:
on:
  pull_request:
    types: [opened, synchronize]
jobs:
  auto-review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: |
          claude -p "Review this PR.
          Focus on security and perf.
          Post review comments." \
          --allowedTools Read,Glob,Grep

Safety guardrails are critical

Autonomous agents can cause real damage. Always use --max-turns, --allowedTools, and run in sandboxed environments. Never give autonomous agents production database write access without human review.

This is the frontier

Level 10 techniques are used by a very small number of practitioners. They require deep understanding of all previous levels. Do not attempt these until you are fully comfortable with Levels 0-9.

The future is agentic

As models improve, autonomous loops will become more reliable and common. Building these skills now positions you at the cutting edge of AI-assisted development.

Learning Checklist

0% Complete
Autonomous Loops
Part 2

OpenClaw / ClawBot

The open-source autonomous personal AI assistant. Formerly known as Clawdbot and Moltbot.

OpenClaw

What is OpenClaw?

OpenClaw (formerly Clawdbot, then Moltbot) is an open-source, self-hosted personal AI agent. Unlike Claude Code which focuses on coding, OpenClaw automates your entire digital life through messaging apps like WhatsApp, Telegram, and Discord.

ClawBot = OpenClaw

ClawBot (Clawdbot) was the original name. It was renamed to Moltbot, then to OpenClaw. All three names refer to the same project.

Installation

1

Prerequisites

You need Node.js v22+ and an API key from any supported provider (Anthropic, OpenAI, or Ollama for local models).

2

Install OpenClaw

Install
npm install -g openclaw@latest
3

Run the onboarding wizard

Onboard
openclaw onboard --install-daemon

This walks you through API key setup, messaging app connections, and daemon installation.

4

Verify it's running

Verify
openclaw status
# Should show: Gateway running on port 3000

Core Concepts

GatewayThe always-running background service that listens for messages and routes them to the AI.
ChannelsMessaging platforms (WhatsApp, Telegram, Discord, SMS) that connect to the Gateway.
SkillsReusable task templates. Browse and install from ClawHub, or write your own.
MemoryPersistent knowledge files that survive between conversations.
HeartbeatA scheduler that triggers OpenClaw to perform tasks at set intervals, even without a message.
Control UIA web dashboard for managing skills, memory, channels, and viewing logs.

OpenClaw Learning Checklist

Learning Checklist

0% Complete
Installation & Setup
First Steps
Advanced
Part 3

Comparison & Synergy

How Claude Code and OpenClaw compare, and how to use them together.

Feature Comparison

FeatureClaude CodeOpenClaw
Core FunctionAgentic coding assistantAutonomous personal AI assistant
Primary Use CaseSoftware developmentPersonal digital automation
User InterfaceCommand-line (Terminal/IDE)Messaging apps + Web UI
Operating ModeOn-demand sessionsAlways-on background daemon
AutonomyUser-driven onlyAutonomous via heartbeat scheduler
Model SupportClaude models onlyClaude, GPT, local models (Ollama)
Data PrivacyCode processed by AnthropicFully self-hosted, data stays local
LicensingProprietary (subscription)Open Source (MIT License)
CostMonthly subscription ($20-200+)Free software + API usage costs

Decision Guide

Use Claude Code when...
  • 1. You are working on a software project.
  • 2. You want AI in your terminal/IDE.
  • 3. Your workflow revolves around coding and Git.
  • 4. You want the latest Claude models.
Use OpenClaw when...
  • 1. You want to automate digital tasks.
  • 2. You value data privacy (local data).
  • 3. You want to interact via messaging apps.
  • 4. You need an always-on agent.

Use Both Together

Claude Code and OpenClaw are complementary. Use Claude Code for development and OpenClaw for personal automation. For example, create an OpenClaw skill that triggers Claude Code to generate a daily codebase report and sends it to you via Slack.

Resources & Links

All the official documentation, tutorials, and community links.

Last updated: March 2026. Built with care for beginners.