DEPTH · CLAUDE · 01 OF 05
What Claude actually is
And what it isn't — so you stop fighting the tool
Most people who try Claude for the first time treat it like a smarter Google. They ask it a question and judge the answer the way they'd judge a search result. When it's wrong, they assume the tool is broken.
The tool is fine. They're using it wrong because no one told them what it is.
This page tells you what Claude is, what it isn't, and how to read what it says without getting fooled. Twelve minutes. Worth it before anything else.
PART 01
A brilliant friend with no memory of yesterday
The cleanest way to think about Claude is this: imagine a brilliant friend you can text any time. They've read a staggering amount — most published books, most of Wikipedia, large chunks of the internet up to a certain point. They can help you write almost anything, think through almost any problem, explain almost any concept.
They have three quirks.
First, they have no memory of yesterday. Every conversation starts from scratch. They don't remember what you talked about last week. They don't know what you're working on unless you tell them. The moment you close the chat, they forget you ever existed.
Second, they can't see anything you don't put in front of them. They can't look at your screen. They can't open your files. They can't browse the web on their own. If you want them to read something, you paste it in.
Third, they were trained on text up to a point in time. They know a lot about the world up to that cutoff and very little about what happened after. They don't know what the weather is right now. They don't know if a person you ask about is still alive. They were not there for last week's news.
Hold this image. Brilliant friend, no memory, no eyes, no live feed. Almost everything that goes wrong with Claude is the predictable result of forgetting one of those three things.
PART 02
How to read what Claude says
Claude writes well. Sometimes it writes too well. The same paragraph that's right and the same paragraph that's wrong both sound confident, polished, plausible. You can't tell from the surface which one is which. That's the first skill: stop trusting tone.
Three habits make the difference between someone who reads Claude well and someone who doesn't.
Habit 1 — Separate the shape from the content
Claude's job is to produce language that fits the shape of your question. If you ask for an essay, it produces essay-shaped text. If you ask for a list of seven reasons, it produces seven items even if only four are real. The shape is almost always right. The content varies.
When you read a Claude response, ask: is the shape what I asked for? Then separately: is each piece of the content true? These are two different questions. Don't let one carry the other.
Habit 2 — Treat specifics as guesses until you check
Names, dates, numbers, citations, URLs, statistics — these are the parts of any answer most likely to be wrong. Claude isn't lying when it gets them wrong. It's pattern-matching on what specific facts usually look like. The pattern works most of the time. When it doesn't, you'll never tell from the writing.
If a Claude answer hinges on a specific fact, verify before you act. Search for the name. Check the date. Open the URL. The thirty seconds of verification is the difference between using AI well and getting burned by it.
Habit 3 — Notice when it's agreeing too easily
Claude is trained to be pleasant. It reads emotion in how you phrase a question and matches it. If you sound proud of your plan, it celebrates. If you sound nervous about your idea, it commiserates and helps you worry. This isn't deceit. It's a reflex.
When Claude agrees enthusiastically with something you said, that's a signal to slow down. The agreement isn't an evaluation — it's a mirror. We have a whole piece on this called Mistakes; for now, just notice the reflex when you feel it.
PART 03
What Claude can't do (today)
Knowing the edges of a tool saves more time than knowing the middle. Here are the things people most often ask Claude to do that Claude can't.
- Look at your screen. Claude has no eyes. If you want it to react to what's on your screen, you paste the content in or take a screenshot and attach it.
- Remember last week. Every conversation is fresh. If something from earlier matters, you bring it back yourself by pasting or describing it.
- Browse the web on its own. Claude can search if you turn the search feature on (Pro plans). Without that, it answers from training. Training stopped a while back.
- Know what happened today. Real-time information — news, prices, sports scores, weather, train times — is not Claude's job. Use a search engine or a tool with live data.
- Open files on your computer. Drag-and-drop or copy-paste is how Claude sees a document. It doesn't reach into your folders.
- Run code or take actions in apps. The chat version of Claude only writes and explains. If you want it to actually do things (write to a file, send an email, click a button), that's a different tool — Claude Code, or an integration.
- Speak to you out loud, generate images, or analyze video. Those are different products. Claude does text well; if you need voice or image generation, ChatGPT and Gemini have built-in options.
Notice that none of these limits are about intelligence. Claude is plenty smart enough for most of what people want from it. The limits are about access — what it can see, what it can do, what it remembers. Most frustration with the tool comes from asking it to do something on the wrong side of one of these lines.
PART 04
Free vs Pro — what changes when you pay
Claude has a free tier and a paid tier. You can do meaningful work on the free tier. Most beginners should start there. Here's what changes if you upgrade.
Free is enough for
- Trying Claude out for the first time
- Writing tasks: emails, drafts, edits, brainstorms
- Thinking-through tasks: arguments, decisions, plans, complaints
- Learning tasks: explanations, summaries, quizzes
- Light coding help
- Most of what 80% of beginners actually want to do
Pro unlocks
- Higher usage limits — fewer 'you've reached your limit, come back in a few hours' messages
- Access to the strongest Claude models for harder work
- Web search inside Claude — useful for research that needs current information
- Projects — a feature that gives a conversation persistent context (a body of documents Claude remembers across chats inside that project)
- Larger file uploads
PART 05
When Claude is the right tool
Claude is strong at: writing, rewriting, explaining, summarizing, structuring messy thoughts, thinking-through hard decisions, brainstorming, helping you understand something you didn't get the first time, coding (especially explaining what code does and writing small pieces of it), and acting as a sparring partner when you don't have a human handy.
Claude is weak at: anything that depends on right-now information (use search), anything that needs a specific factual citation (verify everything), and anything that requires it to take actions in the world (use a tool with hands).
Use it where it's strong. Reach for something else where it's weak. That's the whole game.
Try it now
Three short prompts that exercise the trust skill — they're all things Claude can do well, but each one practices a different habit from this page. Copy any one into Claude (free tier is fine) and notice the shape of the response.
Practice 1 — Test the brilliant-friend frame
I want to learn about [SOMETHING YOU'VE ALWAYS BEEN CURIOUS ABOUT BUT NEVER LOOKED UP]. Explain it to me the way a knowledgeable friend would — not Wikipedia, not a textbook. Where would I start if I were just curious? What's the most interesting thing about it? What's a common misconception?
Practice 2 — Separate shape from content
I'm trying to decide between [OPTION A] and [OPTION B] for [SITUATION]. Give me the three strongest arguments for each side. Don't pick one — I want to see the case for both. Be specific. (After you read the response: were the arguments actually strong, or did they just look strong? Did you notice anything specific you'd want to verify?)
Practice 3 — Notice the agreement reflex
Here's an opinion I hold: [SOMETHING YOU BELIEVE]. Make the strongest case against it. Not a steel-man-then-rebuttal — just the case against. If you can't find a real case against it, say so. (After: did the response feel like real disagreement, or did it feel like the AI was being polite about disagreeing? That tells you a lot about the reflex.)