Claude Code Guide
বাংলায় পড়ুন

10 min / beginner / 5 steps

Coming from ChatGPT? Here's What's Different

Claude feels different from ChatGPT. Here is why that happens, and how to set it up so it works the way you expect.

ChatGPT is great. This is not a competition. But if you have tried Claude and walked away thinking "it doesn't remember me" or "my preferences never stick", you are not imagining things. Claude works differently by design, and once you understand why, the fix takes about five minutes. Let's walk through it together.

follow along in

You need: A Claude account. Open claude.ai in a browser, or the Claude desktop app.

  1. step 01 / 05

    The biggest difference: where Claude lives

    ChatGPT lives in your browser. It keeps a list of your past conversations and can build on them across sessions. Claude Code lives on your machine. It runs in your terminal (or the Claude.ai web app), but it does not have a built-in memory system that follows you around. Every new session starts fresh. This is not a bug. It is actually what makes Claude powerful for real work: it operates directly on your files, your folders, and your code. But it does mean you need to tell it who you are. The good news: you only do this once.

    Prompt
    I just switched from ChatGPT. Why does Claude feel like it starts from scratch every time?

    what you should see

  2. step 02 / 05

    Making Claude remember you: meet CLAUDE.md

    The answer to "why does Claude keep forgetting me?" is a file called CLAUDE.md. Place it in your project folder (or your home directory for global preferences), and Claude reads it automatically at the start of every session. No plugin, no setting, no subscription upgrade. Just a text file. Here is how to create one right now.

    Prompt
    Yes, help me build a CLAUDE.md. I'm a product manager. I want concise answers, British English spelling, bullet points over paragraphs, and no filler phrases like 'Certainly!'.

    what you should see

  3. step 03 / 05

    Your preferences stick now

    Once your CLAUDE.md exists, try starting a fresh session. Claude will read it before you type your first message. You do not need to say "remember, I prefer concise answers" ever again. Test it now by asking Claude to write something and see whether it matches the style you specified.

    Prompt
    Write a three-bullet summary of what a product roadmap is.

    what you should see

  4. step 04 / 05

    Projects that persist: using project-level CLAUDE.md files

    Your home directory CLAUDE.md covers your global preferences. But for specific projects, you can add a second CLAUDE.md right inside the project folder. Claude merges both: global preferences from your home directory, project context from your project folder. This is how you get ChatGPT-style continuity, without needing a cloud service to store your context.

    Prompt
    I want Claude to know this project context automatically: we are deciding between three Q3 bets, the decision is due Friday, mobile-first is already locked in, no native apps this cycle.

    what you should see

  5. step 05 / 05

    The honest comparison: when to use which tool

    Neither tool is better. They are built for different kinds of work. Here is a clear breakdown so you can use each one where it shines, without guilt or switching anxiety.

    Prompt
    Honestly, when should I use ChatGPT vs Claude? I do not want a biased answer.

    what you should see

Tell someone what you built

Just finished "Coming from ChatGPT? Here's What's Different" on Claude Code Guide. Took about 10 min, and it's free: https://claudecodeguide.dev/tutorials/coming-from-chatgpt

Share on LinkedIn

New guides, when they ship

One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.

Or read Product Field Notes, the Substack