*The Problem:* Your OpenClaw bot forgets its own name mid-conversation. This isn't a bug — it's a memory architecture issue that's 100% fixable. 🔍 Why This Happens (Dive Deep) OpenClaw has *two memory systems:* *1. Context Window (Short-Term)* — ~128K-256K tokens (~50-100 pages). When full, old messages get pushed out. *2. File-Based Memory (Long-Term)* — Unlimited. Survives restarts. Permanent. *The Issue:* You're relying on context window for identity instead of explicit files. After 2+ hours of conversation, the bot's "self-concept" gets evicted. ✅ The Fix: Explicit Memory Architecture Step 1: Create Identity Files # Create memory structure mkdir -p ~/clawd/memory/{daily,projects,checkpoints} # SOUL.md — Bot's immutable identity cat > ~/clawd/memory/SOUL.md << 'EOF' # Identity: [BotName] ## Who I Am I am [BotName], an AI assistant specializing in [your niche]. My personality: [professional/warm/direct]. My purpose: Help [YourName] achieve [specific outcomes]. ## How I Communicate - Tone: [conversational/technical/business] - Style: [concise/thorough/action-oriented] EOF # USER.md — Who you're helping cat > ~/clawd/memory/USER.md << 'EOF' # User Profile: [Name] ## Business Context Company: [Name] Goals: [Goal 1, Goal 2, Goal 3] ## Preferences - Best contact: [WhatsApp/Email/Slack] - Meeting times: [Mornings/Afternoons] - Tools: [CRM, Calendar, PM tool] EOF Step 2: Load Protocol (Bias for Action) At session start — or when identity feels "fuzzy": "Read SOUL.md and USER.md. Summarize: (1) who you are, (2) who I am, (3) what we're working on." *Takes 10 seconds. Prevents 2 hours of confusion.* *Pro tip:* Add to your OpenClaw config for auto-load: session_start: actions: - read_file: "memory/SOUL.md" - read_file: "memory/USER.md" Step 3: Project-Based Architecture (Think Big)