Claude Dreams: Your AI Assistant Now Learns While You Sleep

What if your AI got smarter every night — without you doing anything? What if you could correct it once, and the lesson just… stuck?

That’s the promise behind Claude Dreams, a new research preview Anthropic just announced. It’s a feature that lets Claude inspect its own past conversations, find patterns in how you corrected it, and create new “memories” while you sleep. You run a task before bed. Claude audits itself. By morning, it’s better at your specific workflow.

This isn’t about fine-tuning a model or writing better prompts. It’s about the AI learning passively, like a junior team member who pays attention. For designers, agency owners, and anyone who feels like they’re repeating the same instructions to their AI every day, this is a quiet but massive shift.

---

What actually shipped

Anthropic announced Claude Dreams at their recent Code w/ Claude event. It’s currently a research preview, which means it’s rolling out to Claude Pro users gradually. The core idea is simple: your AI should learn from your feedback without you having to explicitly tell it to “remember this.”

Here’s how it works. You work with Claude in a chat thread during the day. You ask it to draft copy, write code, or summarize notes. When it gets something wrong, you correct it. “No, use this hex code,” or “Rephrase that to be more direct.” At the end of the day, you close the laptop.

Overnight, the “dreaming” process kicks in. Claude analyzes the transcript of your session. It looks for moments where you provided corrective feedback. It identifies the pattern — what it did wrong, and what you provided as the right answer. It then creates an internal memory from that correction. The next morning, when you use that same chat thread for the same task, it applies what it learned.

DAY (you work)         NIGHT (Claude dreams)        MORNING (return)
──────────────────     ──────────────────────       ──────────────────
You chat with Claude   Reviews transcript           New task, same prompt
You correct mistakes   Spots correction patterns    Claude applies what
You close the laptop   Creates internal memories    it learned overnight

        ↓                       ↓                            ↓
   One session             Passive learning           Compounding speed

This is different from custom instructions or pasting a style guide into every prompt. Those are static rules you provide up front. This is dynamic learning based on the natural flow of work. It’s the closest any model has come to mimicking how a human apprentice learns on the job.

Before Claude Dreams, you had to re-teach your AI every day. Now, you teach it once, and it remembers the next morning.

---

Why this matters for design and agency work

For designers and creative directors, this changes the texture of working with AI. The friction of repeating yourself starts to fade away. Think about the small, repetitive corrections you make every day.

A client has a specific tone of voice they prefer — slightly formal, no emojis. You correct Claude’s first draft. With Dreams, that correction sinks in. The next day’s drafts are closer to the target from the start.

You have a preferred way of structuring CSS files or naming components in a React project. You paste in a code block and tell Claude, “No, do it like this.” The next time you ask it to scaffold a component in that same thread, it remembers your preferred structure.

This turns a generic AI assistant into a specialist. You can have one Claude thread that becomes an expert on Client A’s brand, and another that becomes an expert on your agency’s internal reporting format. The AI starts to feel less like a calculator and more like a collaborator who’s been on the team for a few weeks.

---

Here’s how I’d actually use this

This feature only works if you change your habits slightly. You can’t just keep opening new chats for everything. Here’s the 4-step process I’d use to make this stick:

1. Dedicate one chat thread to one recurring task. Don’t mix everything in one giant conversation. Create a thread called “Client X – Social Media Copy” or “My Agency – Weekly Report Drafts.” This gives Claude a clean, focused transcript to learn from.
2. Correct it explicitly for a full week. For the first few days, be a patient teacher. When it makes a mistake, don’t just fix it and move on. Tell it *why*. Use clear, simple language: “Incorrect. The call to action should always be ‘Book a call,’ not ‘Learn more.’”
3. Let it dream. The learning happens overnight. Resist the urge to start a new chat for the same task the next day. Go back to the dedicated thread you created in step one. This is the most important part. Re-using the thread is what allows the memories to compound.
4. Test it with less context. After a few days of corrections, try giving it a simpler prompt. Instead of pasting the full brand guide again, just say, “Draft three tweets for Client X about their new launch.” See if the tone, formatting, and call to action are correct. That’s how you know it’s working.

The goal isn’t to get perfect results on day two. The goal is to see a noticeable improvement over a week. The AI should feel like it requires less hand-holding each day you work with it.

---

What this changes for agency work

When the tool changes, the business of using the tool changes, too. For agency owners, Claude Dreams opens up new ways to structure work, price services, and deliver value.

You can now sell a “trained agent” as a deliverable. Instead of just handing over a website, you can hand over a website *plus* a dedicated, pre-trained Claude thread that knows how to write blog posts in the client’s voice, update their product descriptions, or draft their newsletters. The client doesn’t need to learn prompting; they just use the agent you already taught.

Onboarding new team members gets simpler. When a new designer or project manager joins your team, you can give them access to the client-specific Claude threads. They can see the history of corrections and get up to speed on a client’s quirks in hours, not weeks. The AI becomes part of the institutional memory.

This creates a new, valuable retainer service. Managing and refining these learning agents is real work. A client’s brand voice might evolve, or they might launch a new product line. You can offer a retainer line item for “AI Agent Curation” where you continue to train and update their specialist agent each month. This is a sticky service that provides real, compounding value.

The shift is from selling one-off AI tasks to providing a continuously learning AI partner for your clients. That’s a much more valuable position to be in.

---

My $0.02 — How I’d roll this out for a design business

If I were starting with Claude Dreams this week, I wouldn’t try to boil the ocean. I’d run a simple, three-day experiment to prove the value to myself first. Here’s the playbook:

Day 1 — Pick one chore and dedicate a thread. I’d choose the single most annoying, repetitive writing task I do every week. For me, it’s drafting the initial summary for my YouTube videos. I’d create a new Claude chat named “YouTube Summary Agent” and use it for nothing else. I’d start with a seed prompt that has my basic style rules.

Day 2 — Work and correct, then walk away. I’d process two or three video summaries in that single thread. I would be ruthless with my corrections, treating Claude like a brand new intern. “This is too long.” “Rephrase this to be a question.” “Start with the hook.” At the end of the day, I’d close the tab and let it “dream” on those corrections.

Day 3 — Test the learning with a lazy prompt. I’d open the exact same thread. This time, I’d just paste in a transcript and say, “Draft a summary.” I wouldn’t re-paste my style guide or remind it of my previous corrections. I’d look for evidence that the lessons from Day 2 stuck. Is the length right? Is the tone closer? Even a 20% improvement is a huge win, because that improvement is now the new baseline, for free.

This is exactly how I’m training the agent that helps with content for mikekwal.com. It starts with a real pain point, involves deliberate training, and proves its worth with a simple test. *If you can talk it, you can build it.*

---

FAQ

Is Claude Dreams available to everyone right now?
It’s a research preview, so it’s rolling out gradually to Claude Pro subscribers on the web. It’s not in the API yet. Check your Claude.ai account for a notification.

Does this cost extra?
During the research preview, there is no additional cost. It’s part of the standard Claude Pro subscription.

Is this the same as fine-tuning?
No. Fine-tuning is a much heavier, more technical process where you train a model on a large dataset. Claude Dreams is lightweight, automatic, and happens based on your natural conversation. It’s more like providing on-the-job feedback than sending someone to a formal training course.

How is this different from Custom Instructions in ChatGPT?
Custom Instructions are a static set of rules you provide up front. They don’t change unless you manually edit them. Claude Dreams is dynamic; it learns passively from your corrections during a conversation, meaning it can pick up on nuances you might not think to write down in a formal instruction set.

What if it learns the wrong thing?
Since the learning is tied to a specific chat thread, the easiest fix is to start a new chat. This gives you a blank slate. Anthropic is also working on tools to view and manage memories, but for now, a new thread is the reset button.

Will my corrections in one chat affect my other chats?
No, the memories are scoped to the conversation they were learned in. The agent you train to write social media copy for Client A won’t apply those learnings when you ask it to write code in a different chat.

Is my data used to train Anthropic’s main models?
No. Anthropic’s business policy is that they do not train their foundation models on user inputs or outputs. The “memories” created by Claude Dreams are private to your account and specific to your conversations.

How many corrections does it take for a lesson to stick?
There’s no magic number, but in early tests, it seems that clear, direct corrections on the same type of error two or three times are often enough for Claude to pick up the pattern.

---

Want help applying this?

Four ways to go deeper:

• Build with Builders. Join the Talk-to-Build community to learn how to Earn money with AI, Download our AI Skills, Advance your business, and learn to build real assets — AI-native websites, cinematic AI video, agent-driven workflows — that you can sell to SMBs who want the outcomes but don’t have time to learn the skills.
• 1-on-1 working session. Skip the friction. Book a screen-share with me — bring a real problem, leave with a working piece of it.
• Done-for-you. MK-Way builds AEO-ready websites, apps, and AI agent workflows for design agencies and founders who want it shipped fast.
• Quick question. DM me on Instagram or connect on LinkedIn. I read every message.

---

This post is part of the AI Pulse atomic series. If you commented “AUTOMATE” on one of my videos — this is the breakdown. Sources: Simon Willison’s Notes on Code w/ Claude, Bloomberg.

Last updated: 2026-05-26.