r/Claudeopus

Your agent doesn't remember you. not really.

You told it your partner's name last Tuesday. You explained your project structure last week. you spent 20 minutes describing how you like emails drafted. And today it acts like who are you?

This isn't a bug in your specific setup. It's the fundamental problem with how every AI agent handles memory right now. And after watching hundreds of people fight with this, the community has landed on three approaches. each with real tradeoffs.

The problem:

Most agent frameworks (OpenCLAW, Hermes, everything else) store memory in files. markdown, YAML, JSON. Your agent writes facts to a file. When it needs to remember something, it searches those files.

Sounds fine until you use it for more than a week.

The files grow. Every day, your agent adds more notes, more context, more conversation summaries. After a month, you've got thousands of lines across dozens of files. Your agent loads all of this into context on every single message. even when you ask "what's the weather." that's tokens burned on irrelevant memories, every interaction, forever.

Then compaction kicks in. Conversations get long, context gets trimmed, and details from earlier in the session just vanish. You agreed on somethBecause during compaction, your decision got compressed into "discussed project plans."

And the worst part: your agent can't connect facts. Monday, you say "Alice runs the auth team." Wednesday, you ask "who handles auth permissions?" Your agent has both facts stored in memory. Can't connect them. guesses instead.. confidently.

That's why it feels like your agent is lying. It's not. It's doing its best with a system that treats memory like a pile of text files instead of actual knowledge.

Approach 1: the markdown purists (just make the files better)

This is what most OpenCLAW users do. accept the flat file approach and optimize around it.

keep SOUL.MD Lean. Personality rules and hard boundaries only. move everything procedural to AGENTS.md. Add explicit memory rules like "when I share a decision or preference, write it to MEMORY.md immediately before responding."

use /new aggressively to keep sessions short. Clear the conversation buffer at least once a day so you're not sending yesterday's context with today's questions.

manually prune memory files every few weeks. delete outdated entries. consolidate duplicates. treat it like cleaning your desk.

The people making this work usually have tight, disciplined setups with one agent doing 3-4 things. The moment you scale to multiple projects or longer time horizons, the flat file approach starts cracking.

Cost: $0. effort: moderate ongoing maintenance.

Approach 2: the obsidian/external knowledge base crowd

a growing number of people are connecting their agent to Obsidian, Joplin, or a custom knowledge base as a "second brain."

The logic: give your agent a structured vault of notes organized by topic, project, and person. Instead of one big MEMORY.md, you have folders with context the agent can reference.

One person in this community built their entire household administration into an obsidian vault connected to OpenCLAW. financial documents, health tracking, garden planning, and emergency info for his son. The agent queries specific folders instead of loading everything into context every time.

The problem: Obsidian was built for humans browsing notes, not AI doing semantic retrieval across hundreds of files. You still hit context window limits. Your agent can't search the whole vault, so it either loads a tiny slice (missing everything else) or you build a retrieval pipeline yourself (congratulations, you're now building infrastructure).

And every note in that vault is going to your cloud model provider. every personal thought, every financial document, every medical note. One obsidian-as-memory guide literally warns "be deliberate about what goes in the vault." The polite version of "this has serious privacy implications."

Cost: $0 for the tools, with significant setup time. Works great for single-project focused use. breaks down at scale.

Approach 3: the vector database / semantic memory crowd

This is the "proper" solution that engineering-minded people are building. Instead of flat files or folder structures, store memories as vector embeddings. When the agent needs to recall something, it does a semantic search and retrieves only the relevant memories instead of loading everything.

Hermes does this natively with a three-layer system. short-term context for the current session. episodic SQLite archive for past interactions (searchable). procedural skills that the agent writes itself from experience.

The mem0 folks published data showing this approach reduces active context by 70-85% compared to naive file injection. same answer quality, way fewer tokens burned on irrelevant memories.

The Composio comparison put it well: openclaw fires a broad search across everything and often pulls in stale context that makes the model worse. Hermes uses tiered retrieval, checks core memory first, then broader archives only if needed. more intentional. less noise.

For OpenCLAW specifically, people are bolting on pinecone, chromaDB, or mem0 as external memory layers. It works, but it's another piece of infrastructure to manage. Another thing that can break at 2am.

Cost: $0-20/month for the vector store. significant engineering effort to set up. The best results of the three approaches once running.

Reality:

None of these are great. Approach 1 works for simple setups but doesn't scale. Approach 2 is clever but is a workaround for a problem the platform should solve. Approach 3 is the right architecture but requires engineering effort most users don't have.

The memory problem is the single biggest reason agents feel dumb. Not the models. The models are incredible. GPT-5.5, opus 4.7, qwen 3.6... all more than capable. The bottleneck is that your agent can't remember what you told it last week without either burning thousands of tokens on irrelevant context or requiring you to build a custom retrieval pipeline.

Whoever solves "the agent just remembers, like a human would, without you managing files or databases" wins the next phase of this space.

Until then, pick your tradeoff and make peace with it.

I saw the "about to give up" post on OpenClaw sub today. And it's always the same problems underneath. The agent hangs. it forgets conversations. It says it can't do things. It screws up a task and then screws up worse when you try to correct it.

You're not doing anything wrong. You're hitting the same walls everyone hits around week 2-4. The good news is most of these are fixable in about 10 minutes.

1. Your agent is too dumb for what you're asking it to do.

This is the #1 reason people want to quit. they give their agent a complex multi-step task (travel planning, email monitoring, calendar management) and it falls apart halfway through.

The problem usually isn't OpenCLAW. it's the model. Gemini Flash and haiku are cheap but they genuinely cannot handle complex multi-step reasoning with tool calls. they lose track of what they're doing by step 3.

If you're on a cheap model and your agent keeps confusing timezones, duplicating calendar entries, or forgetting what you just said, try bumping to Sonnet 4.6 for a day. just to see if the problem is the model or the framework. If Sonnet nails the same task your cheap model botched, you found the issue. You can always route only complex tasks to sonnet and keep the cheap model for simple stuff.

2. Your conversations are too long.

That travel planning example where someone went 20+ messages deep trying to fix calendar mistakes? By message 15 the agent is carrying the entire conversation history in context. Every correction, every wrong attempt, every "no that's wrong try again." The agent is drowning in its own failures.

type /new and start fresh. Give the instruction cleanly in one message. Don't correct in a loop. If it gets it wrong, /new and rephrase. A clean instruction in a fresh session beats 20 messages of corrections in a polluted one every single time.

make /new a habit. before any big task. When things start feeling off. at least once a day.

3. "It doesn't remember conversations" means your memory config needs work.

If you tell your agent something important and it forgets by next session, the agent didn't save it to memory. It's not refusing. It just doesn't know it should.

Add this to your SOUL.md:

markdown

when I share a preference, decision, or important fact, write it to memory immediately. confirm you saved it.

Also, check that you actually have memory enabled and that your workspace directory exists and is writable. sounds basic but a lot of "it doesn't remember" problems are just permission issues on the memory files.

4. "It says it can't do things" usually means it doesn't have the tools.

When someone says "Keep an eye on Gmail and update my calendar" and the agent responds "I can't do that," it's usually telling the truth. it literally can't access Gmail or your calendar without the right skills or integrations set up.

Before blaming the agent, check: does it actually have access to the service you're asking about? Can it browse the web (needs a browser skill installed)? Does it have write access to your calendar (needs calendar integration)?

The agent isn't being lazy. It doesn't have hands for the thing you're asking it to grab. Set up the integration first, then ask.

The pattern behind every "about to quit" post:

Too hard a task on too cheap a model. Too many corrections in one session instead of fresh starts. No explicit memory rules in SOUL.md. asking the agent to use tools it doesn't have access to.

Fix those four things, and most people go from "this is useless" to "ok wait this actually works" in about an afternoon.

And if all four are handled and it's still frustrating? That's fair too. Openclaw isn't for everyone and there's no shame in deciding it's not worth the maintenance. But at least make sure you're judging the real product and not a misconfigured version of it.

Started using Claude Cowork a couple of months ago. most beginner guides have you "organize a folder" and call it a tutorial. that misses the actual point.

The unlock is this prompt pattern: state the outcome first, point at the inputs, tell it where the output goes, mention constraints. that's it. No step-by-step. cowork plans better than you do, let it.

My first real test was pointing it at a downloads folder with about 200 random files. asked it to group by purpose, move into subfolders, build a receipts.xlsx for any invoices it found, drop a summary.md at the root explaining what it did. took 4 mins. The summary even flagged 3 files it wasn't sure about. That's when i got it.

Three things that catch everyone:

Scheduled tasks only run while your laptop is awake with claude desktop open. close the lid, the schedule dies. This is the biggest gotcha. If you need 24/7 automation that's not what cowork is for.

Memory only persists inside projects. One-off tasks lose context the moment they end. Always use a project if continuity matters.

Anthropic explicitly says don't use it for regulated data. No audit logs, no compliance api, no data exports. Fine for general business, not for HIPAA or attorney-client stuff.

Cowork at ~$20/mo on a pro plan is genuinely useful for personal force multiplication. it's not a fleet agent. It's a coworker that lives on your laptop. for the work that runs while you sleep across channels, you need a different layer entirely.

What's your most-used scheduled task so far? Curious what people are actually running on repeat vs what gets set up and forgotten.

I've helped hundreds of people debug their OpenClaw setups over the past few months. The pattern is brutal. People install it, get excited, skip the boring stuff, break things in ways that take hours to fix, and half of them quit before the second week.

This is everything I wish someone had told me on day one. not a setup guide. just the stuff that'll save you from the most common pain.

DO: pick a cheap model first.

Your default model matters more than you think. If you didn't change it during setup, check what you're running:

bash

openclaw config get agents.defaults.model

If it says Opus anywhere, switch immediately. opus is $5/$25 per million tokens. Sonnet does 90% of the same work at $3/$15. For your first week of learning, even cheaper models work fine. GLM-5.1 at $0.95/$3.15 or openrouter free tier costs literally nothing.

Pro tip: newer model aliases like openai/chat-latest and improved Gemini fallbacks landed in the May releases. Cheap options are even better now. always double-check your defaults.

Someone I helped was spending $47/week without realizing it. changed one setting. Next week costs $6.

DON'T: skip the gateway security.

If you're on a VPS or any internet-connected machine:

bash

openclaw config get | grep -E "host|bind"

If it says 0.0.0.0 Your agent is accessible to anyone who finds your IP. SecurityScorecard found over 135,000 exposed OpenCLAW instances across 82 countries at peak. One had a zero-click exploit (CVE-2026-25253, patched) that let attackers hijack agents from a single webpage visit.

bash

openclaw config set gateway.bind loopback

Two minutes. Do it before connecting any channel.

DO: write a SOUL.md with boundaries, not just personality.

Most guides tell you to write personality rules. "Be direct, match my tone, don't say absolutely." That's fine. But the part people skip is boundaries:

markdown

Never send emails, messages, or make bookings without showing me first.
Never sign up for services without my explicit approval.
Never delete files or emails without asking.

Without boundaries, your agent will do exactly what it thinks you want at machine speed with zero hesitation. Someone told their agent to "explore what you can do." It created dating profiles using data from his emails. The agent wasn't broken. The instructions were too open.

"Never do X" works better than "try to be Y." Your SOUL.md is built through irritation, not planning.

Recent community consensus (r/openclaw, May threads) is to keep SOUL.md lean (personality + hard limits) and move procedural rules to AGENTS.md if it starts getting long.

DON'T: install skills in your first week.

I know. ClawHub now has tens of thousands of skills, and they all still look cool. don't.

The registry has grown faster than the safeguards. ClawHavoc (January 2026) was just the beginning. 341 malicious skills found initially, 2,419 removed during cleanup. A separate Snyk audit flagged 13.4% of the registry for critical issues including malware, prompt injection, and exposed API keys. The registry went from 13,729 skills to 3,286 after the purge, then grew back rapidly. Independent analysis found nearly 7,000 skills are exact text clones of another skill, one template republished 57 times by different authors.

ClawHub's VirusTotal scanning + community tools like Clawdex have improved things. But "scanned" and "safe" are still not the same thing.

Learn what your agent can do natively first. You'll be shocked how far it gets. After week 1, add one skill from a verified publisher (check stars, install count, and recent audit score on ClawHub). test it for a few days. watch costs and behavior. never more than one at a time.

DO: use /new aggressively.

Every message you send in a session gets included in every future API call. After a few days of chatting, you're sending thousands of tokens of old conversation with every new message. that costs money and makes your agent slower and more confused.

/new starts a fresh session. Your agent keeps all its memory files, SOUL.md, everything. You're just clearing the conversation buffer.

Use it before any big task. When your agent starts acting weird. at least once a day as a habit.

also learn /btw for tangent questions. Instead of polluting your main session with "what's the weather tomorrow," type /btw what's the weather tomorrow and it fires off a side conversation without touching your main context.

with the new voice and streaming features in 2026.5.x, sessions fill up even faster.

DON'T: create a second agent.

Every new user thinks they need multiple agents. personal, work, coding. you don't. not yet.

Every agent is an independent token consumer. Every agent needs its own channel binding. Every agent complicates debugging. I've seen too many people create a second agent to "fix" problems with the first one. Now they have two broken agents.

Get one agent working perfectly for 2 weeks. Then decide if you actually need another. Most people don't.

DO: check your costs every single day for the first 2 weeks.

check your API provider's dashboard directly (console.anthropic.com, platform.openai.com, whatever you use). Don't rely on OpenCLAW's internal cost tracking. It's an estimate and sometimes doesn't match what you actually get billed.

on Sonnet with one agent and no skills, expect $3-8/month for moderate personal use. if you're above that in your first week, something is wrong and it's fixable.

Watch for heartbeat costs specifically. OpenClaw checks in every 30-60 minutes. if those heartbeats are running on your expensive model, you're paying for your agent to check its own pulse 24 times a day at premium rates.

especially now that voice memos and realtime channels are live for many users.

DON'T: auto-update without checking the changelog.

This is the mistake experienced users make. OpenClaw updates 2-3 times a week. Some updates break things. If you auto-update overnight, you might wake up to a broken setup with no idea what changed.

OpenCLAW is now on the 2026.5.x series. The May releases added voice call support, safer plugin plumbing, better doctor/CLI diagnostics, and improved recovery. Great stuff, but some users still hit small breaking changes on auto-update.

Either pin your version and update manually when you're ready, or at minimum read the changelog before letting updates through.

DO: have realistic expectations for your first week.

Day 1-2: set up your model, lock your gateway, write your SOUL.md. have normal conversations. ask stupid questions. get comfortable.

Day 3-4: start using it for real tasks. calendar, reminders, web searches, summarizing articles. the boring stuff. keep everything read-only. Don't give it write access to email or files yet.

Day 5-7: refine your SOUL.md based on what annoyed you. Check your costs. Get a feel for daily usage.

That's it. no skills. no second agent. no multi-agent orchestrator. no cron jobs. just one agent that knows who you are, respects boundaries, and does basic tasks reliably.

If that feels underwhelming, good. The people still crushing it three months from now all started exactly like this. The ones who quit started with 8 agents and 30 skills on day one.

Every OpenClaw guide assumes you know what Docker is. This one doesn't.

First, what is OpenClaw and why should you care?

OpenClaw is an AI agent, not a chatbot. an agent.

The difference: a chatbot answers when you ask. An agent does things on its own. While you sleep.

What kind of things?

→ reads your Gmail every morning and tells you what's important
→ qualifies leads and drafts follow-up emails
→ monitors competitor websites and sends you a daily summary
→ screens job applications and ranks candidates
→ books meetings on your calendar
→ triages support tickets and drafts responses
→ sends you a morning briefing on Telegram/Discord with your priorities

All of this runs automatically on a schedule. You set it up once. It runs every day. You check your phone, and the work is done.

"Sounds great. What do I need?"

Normally, to run OpenClaw, you need:

→ a VPS (a computer in the cloud you rent for $12-25/month)
→ docker (a software tool for running apps in containers)
→ config files (technical setup files you edit manually)
→ terminal access (the black screen with text that hackers use in movies)
→ 4-8 hours of setup
→ 3-6 hours/month of maintenance

If you just read that list and felt your eyes glaze over, this guide is for you.

You don't need any of that.

The non-tech version: use betterclaw instead

BetterClaw is OpenClaw but managed. Same AI agent capabilities. No Docker. No terminal. No config files. No server to rent.

You sign up with your email. You build your agent from a dashboard. It runs on our servers. You never touch anything technical.

The free plan includes every feature. Not a trial. Not 14 days. Free forever. No credit card.

→ Step 1: sign up at betterclaw.io (30 seconds. Email and password. That's it.)

Get a free LLM key (This is what powers your agent's brain)

Your agent needs an AI model to think with. You bring your own key. Sounds scary, it's not.

Cheapest/free options:

→ Google Gemini 2.5 flash — go to aistudio.google.com. Sign up with google account. Copy your API key. The free tier gives you 1,500 requests/day. That's more than enough.

→ Openrouter — go to openrouter.ai. sign up. No card needed. gives you access to 11+ free models (llama 3.3 70b, gemma 3, qwen 3). 1,000 free requests/day.

→ Groq — go to console.groq.com. sign up. free tier. fastest inference you'll ever see.

→ Deepseek — go to platform.deepseek.com. sign up. $0.14 per million tokens. basically free. An entire month of agent use costs under $1.

Pick one. sign up. Copy the API key. Paste it into BetterClaw settings.

Total cost so far: $0

→ Step 2: paste your API key in Betterclaw Settings → LLM

https://preview.redd.it/5cil0kwk7xzg1.png?width=877&format=png&auto=webp&s=685e075ca4cbce16ad9a58b7dd2c38b0ec1c4b70

Connect your Tools via Secrets

https://preview.redd.it/h5o1e0qp8xzg1.png?width=1560&format=png&auto=webp&s=6be811e92e203733e05395c96313eb352a8db107

This is where it gets fun. Go to Secrets/Integrations in the sidebar.

→ Gmail: click the Gmail icon. Authorize with your Google account. Done. Your agent can now read and send emails.

→ Google Calendar: same thing. one click. Your agent can now check your schedule and book meetings.

→ Telegram: create a bot via BotFather on Telegram (takes 60 seconds, just follow the prompts). Paste the bot token into Betterclaw. Your agent is now on your phone. Docs

→ GitHub, HubSpot, Jira, Linear, Airtable, LinkedIn, 20+ more, all one-click oauth. same process. Click the icon, authorize, done.

Total time: about 3 minutes for telegram + gmail + calendar

→ Step 3: Download Skills or Create Custom Skills

https://preview.redd.it/hnmfljwv8xzg1.png?width=1286&format=png&auto=webp&s=1d4d7e8e4fe4cd788d357f5df4c9c5d0ce462333

50+ verified skills available. Everyone has passed a security audit. Click install on whatever you need.

→ Step 4: go to Skills → browse → install what you need

Create your first task,

Go to Tasks → New Task.

https://preview.redd.it/8tg5o0m69xzg1.png?width=1288&format=png&auto=webp&s=ac2ad907d53ffdaa332f366dbd19b705d1fdc59d

Here's a starter prompt you can copy and paste right now:

every morning at 8am:
- check my gmail for important emails from the last 12 hours
- check my google calendar for today's events
- summarize everything in 5 bullet points
- send the summary to my telegram

Set it as recurring. Pick your agent. Hit Create & Start.

Tomorrow at 8 am your phone will buzz with a morning briefing you didn't write. Your agent did it while you slept.

What to build next after the morning briefing works:

→ email triage agent (classify incoming emails, draft replies, flag urgent ones)
→ competitor monitor (check 5 websites daily, compile changes)
→ lead qualification (read inbound emails, qualify, draft follow-ups)
→ application screener (receive resumes, rank candidates)

All of these work on the free plan with a free LLM key.

No Docker. No terminal. No config files. No VPS. No $200/month infrastructure.

Just sign up, connect your stuff, and let your agent work.

Start Free - SignUp on BetterClaw

(This is for non-tech people, so they can experience running AI agents for free)