Learn Claude — Part 2: Setup, Interface & Conversation Mechanics

Signing up takes two minutes. What separates casual users from effective ones isn't the interface — it's conversation mechanics: how you manage context, when you branch, when you restart, and which settings you've configured. That's what this part is really about.

The two-minute setup

Go to claude.ai, sign up with email, Google, or Apple. The free plan is permanent, no card required. Install the mobile app and, if you work at a computer all day, the desktop app — a global keyboard shortcut to summon Claude changes how often you actually use it.

Interface essentials, quickly: the message box, the sidebar (past chats, searchable), the model picker dropdown, and the attach button for files. Done. Now the part that matters.

Mechanic 1: Every message replays the whole conversation

From Part 1: Claude has no hidden memory — the conversation transcript is its memory, re-read on every turn. Three consequences:

1. Long chats degrade. Responses slow down, usage burns faster, and details from 50 messages ago get less attention.

2. Everything in the chat influences everything after. A wrong assumption Claude made early keeps echoing unless you correct it explicitly.

3. A fresh chat is a reset button — often the strongest debugging move you have.

Mechanic 2: When to continue vs. when to restart

Continue the same chat when you're iterating on the same task and the accumulated context helps ("now make section 2 more formal").

Start a new chat when:

• You're switching topics — even related ones

• The conversation went sideways and corrections aren't sticking

• You've finished a phase (research done → new chat for writing, pasting in only the summary)

That last one is a professional pattern called context distillation: end a long session with "Summarize everything we decided as a brief I can paste into a new conversation" — then start clean with just that brief. Best of both worlds: full memory of decisions, none of the clutter.

Mechanic 3: Edit, don't pile up

Most people respond to a bad answer by adding another message: "no, I meant..." — which leaves the misunderstanding in the context, still influencing everything.

The stronger move: edit your original message (hover over it) and rephrase. The conversation re-branches from that point as if the bad turn never happened. You can also retry a Claude response to get a different take. Cleaning history beats correcting it.

Mechanic 4: Choose models deliberately

The model picker isn't decoration:

• Fast models (Haiku/Sonnet) for drafts, summaries, simple questions — quicker and lighter on your usage limits

• Top models (Opus and above) for complex reasoning, tricky code, high-stakes writing

You can switch mid-conversation — the new model sees the full history. Pattern: explore cheap, finish strong.

Also try extended thinking (a toggle, on supported models) for genuinely hard problems — Claude reasons step-by-step before answering. Slower, but noticeably better on math, logic, and planning. Leave it off for casual questions.

Mechanic 5: Configure once, benefit forever

Five minutes in Settings pays off permanently:

• Preferences — standing instructions applied to every chat: "I'm a non-native English speaker, keep language natural and simple. Never use emojis. When I ask for code, always include comments."

• Styles — switch response style (concise / explanatory / formal) per task, or create your own from writing samples

• Memory — lets Claude carry useful details across conversations; review and edit what's stored in Settings

• Feature toggles — make sure web search and the analysis tool are enabled; you'll need both later in this series

A worked example

❌ Novice: one 80-message chat mixing a trip plan, a CV review, and a Python bug — by the end, Claude is confusing the contexts.

✅ Practitioner: three chats. The trip chat ends with "summarize the itinerary decisions"; that summary starts a clean booking-research chat, on a fast model, with web search on.

Same tool. Completely different results.

Exercise

1. Set up your Preferences (3 lines minimum).

2. Start a chat on any topic, then deliberately edit an earlier message and watch the conversation re-branch.

3. End a chat with the context-distillation prompt and carry the summary into a new one.

Next up

Part 3: prompting — from the basic formula to the structured, example-driven techniques professionals use.