Tier 1 · Foundations1.112 min

Claude vs Claude Code — two different tools with almost the same name

A leaf-strewn path curving through autumn woodlandWorking with Claude — CC BY 4.0

Anthropic makes two things that both start with the word “Claude”, and people mix them up constantly. Getting them straight now will save you a lot of head-scratching later, because they behave very differently and you interact with them in different ways.

Here is the short version:

Most small-business owners will spend nearly all their time in the first one. That is the right place to start.

Claude — the assistant you chat with

This is the one you reach at claude.ai in a web browser, or through the Claude app on a phone or desktop. You sign in, start a conversation, and type what you need — draft this email, summarise this contract, pull the figures out of this spreadsheet, explain this letter from the council.

A few key points:

The mental model: you are the one in charge. Claude proposes; you read it, judge it, and decide what to do with it. Nothing leaves the conversation unless you copy it out.

Claude Code — the tool that acts on your files

Claude Code is a different animal. Instead of handing you an answer to copy, it goes and makes the change itself — opening files on your computer, rewriting them, running commands. You describe the outcome you want; it plans the steps, does the work, and checks in with you along the way.

It runs in places most people never open: a terminal (the plain text command window on your computer), inside coding editors, and in a desktop or browser version. It was designed for software developers, and that is still its main audience.

Access is different too. Claude Code isn’t on the free tier — it comes with a paid Claude plan (Pro or Max), a Team or Enterprise seat, or an Anthropic developer account. (Plan names and inclusions change; confirm in-app / current docs before you rely on this.)

Do you need it? Probably not on day one. If you’re writing, summarising, planning and answering questions, the chat assistant covers you. Claude Code earns its place when you have real work sitting in files on your own machine that you want changed directly — and when you’re comfortable letting a tool make those changes and reviewing them afterwards. That “reviewing them afterwards” part matters: because it acts for you, the discipline of checking its work is on you, not optional.

How to tell which one you’re in

A quick gut-check when you’re not sure:

If you only remember one line: the assistant answers you; Claude Code acts for you. The more a tool can act on your behalf, the more it matters that you stay the one who directs it and signs off on the result.

Think of a task you did this week on your computer. Would you rather an assistant that hands you a draft to check — or a tool that makes the change itself?

What would have to be true before you’d trust the second one to act for you?

Where this course goes

Nearly everything in this course is about the assistant — Claude at claude.ai — because that’s what a small-business owner uses day to day, and using it well is a genuine skill. We’ll come back to Claude Code later, briefly, so you know what it is and when it might be worth a look. For now, when you see “Claude”, picture the chat window. That’s home base.


Shared freely, in good faith. If it's been of value, a koha toward development and running costs is warmly welcomed.

Leave a koha →

Useful? Share this lesson with a colleague.