The Context Window: Claude's Working Memory

You are going to hear the phrase "context window" a lot in this community. It is one of those technical terms that sounds complicated but is actually very simple.

Understanding it will save you from a specific type of frustration that catches almost every beginner off guard.

What the context window is

Think of Claude's context window as a whiteboard.

At the start of every session, the whiteboard is blank. As you have a conversation with Claude, asking questions, giving instructions, and getting responses, everything gets written on that whiteboard. Claude can see everything on it and uses it to understand your project and give you accurate responses.

The whiteboard has a size limit. You cannot write an infinite amount on it.

When it fills up, Claude starts losing access to things written earlier. The most recent conversation stays visible but older parts of the session fade out.

What happens when the context window fills up

You will notice Claude forgetting something you told it earlier in the session. It may get confused about your project structure, make mistakes it would not have made an hour ago, or ask you to repeat information you already gave it.

This is not Claude getting worse. It is Claude working with a smaller and smaller portion of the whiteboard as the session grows longer.

How to work with it, not against it

One task per session. Do not cram everything into one long session. Build your homepage in one session, then start a new session to add the contact form. Fresh session, fresh whiteboard.

Start new sessions for new tasks. When you finish one thing, type /clear or click New Chat. This resets the context window completely and gives you a clean start.

CLAUDE.md solves the remembering problem. You might be thinking: "But then Claude forgets everything about me and my project every time I start a new session?"

Yes, and this is exactly why the next course exists.

In Track 1: The Memory System, you will learn to create a set of files that tell Claude everything it needs to know about you, your brand, and your project before a single word of conversation. Every new session starts with Claude already knowing your name, your design style, your audience, and your goals.

The context window is not a problem once you have your memory files set up. We cover this in full in the next course.

How to tell when you are getting close to the limit

If Claude starts giving you answers that feel slightly off, producing code that does not match the style of your project, forgetting a change you made an hour ago, or ignoring something you specifically asked it to keep, that is your signal.

Start a new chat. Give Claude a quick brief on where you are. Continue from there.

It takes 30 seconds to restart. The alternative is getting increasingly frustrated with a Claude that is doing its best with a completely full whiteboard.

The one-sentence version

The context window is Claude's short-term memory for one session. Keep sessions focused and start fresh for new tasks.

Your action right now

Finish your current session naturally. Do not start a new chat just to practice this. But now that you know what the context window is, you know exactly what to do when Claude starts acting confused mid-session.

Move to the next lesson. We are going to cover what to do when Claude makes a mistake.