How to use Claude Code if you don't code

What is Claude Code, in plain English?

The regular Claude chat gives you text that you copy somewhere. Claude Code does the work where your work lives: in a folder on your computer. Ask for a one-page website and you get the actual files. Ask it to turn three messy spreadsheets into one monthly summary and it opens them, writes the summary and tells you where it saved it.

Anthropic calls it an “agentic coding tool”, but coding is only part of it: the docs say it can help with anything you can do from the command line, from writing documents to searching files and researching topics. For a business owner, good first jobs are:

• a simple website or landing page;
• product descriptions or emails written in your tone, from your notes;
• a weekly report built from spreadsheets you already have;
• sorting, renaming and summarizing a folder of documents;
• small tools: a price calculator, a checklist, a booking page draft.

Bad first jobs: anything you can't check yourself, and anything that touches money, customers or live systems without your review.

Claude Code vs the Claude app vs Cowork: which one do you need?

Anthropic offers the same agent technology in several places, and the names changed in 2026. In September, Anthropic announced that Cowork and chat are merging into one Claude app. Here is the practical difference:

Our rule of thumb: if the result is a conversation or a single document, use the Claude app. If the result is a set of files you will keep improving, use Claude Code. Many people use both. More on the agent side of the app, and on where Cowork went after the merger, in what is Claude Cowork and what changed in September 2026.

What do you need to use Claude Code?

• A paid Claude plan. Pro is enough to start. Details in costs and limits.
• A computer: Windows 10 (1809 or newer) or Windows 11, or macOS 13 or newer. At least 4 GB of RAM and an internet connection.
• A new, empty folder for your first project, for example Documents\my-business.
• 20 minutes and five lines of notes about your business.

You don't need Node.js or a terminal: the desktop app includes Claude Code. Older guides that start with “install Node.js” describe a route you no longer need.

How do you install Claude Code on Windows and Mac?

The easiest way is the Claude desktop app. It includes Claude Code, so you don't need a terminal, Node.js or anything else. It takes two steps.

Desktop app steps follow Anthropic's desktop quickstart, checked October 17, 2026.

irm https://claude.ai/install.ps1 | iex

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

curl -fsSL https://claude.ai/install.sh | bash

claude --version

$currentPath = [Environment]::GetEnvironmentVariable('PATH', 'User')
[Environment]::SetEnvironmentVariable('PATH', "$currentPath;$env:USERPROFILE\.local\bin", 'User')

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc

How to use Claude Code: your first session

Desktop app steps follow Anthropic's desktop quickstart, checked October 20, 2026.

1

Step 1: Choose Local and select your business folder

Takes about 1 min

In the Code tab, look at the row of controls under the prompt box. In the first one, choose Local so Claude works with the files on your computer. Then click the folder control next to it, choose Open folder… and pick the folder you made for your first project. (In the earlier layout of the app, these choices sit above the prompt box.) Choose only a folder of your own: Claude can read and change everything in it. The app may ask whether you trust the files in this folder. It's your own folder, so confirm.

Mark as done: Choose Local and select your business folder

2

Step 2: Switch to Manual mode

Takes about 1 min

Click the mode selector in the row under the prompt box and choose Manual. A new session may show another mode, such as Auto, so check it. The app remembers your choice for the folder. Earlier versions of the app call this mode Ask permissions, and some guides call it Default.

Why Manual? See the next section. Useful controls from now on:

In the desktop app	What it does
Stop button or Esc	Stops Claude in the middle of a task.
+ New session	Starts a fresh conversation in the same folder. Earlier sessions stay in the sidebar.
The +12 -1 counter	Opens the list of files Claude changed and what changed in each.
The ring next to the model picker	Shows how full the conversation is and how much of your plan's limit you have used.
A file name in Claude's answer	Click an HTML, PDF or image file to preview it next to the chat.

Now type your first message in the box at the bottom and press Enter. Your first project starts below.

Mark as done: Switch to Manual mode

claude

How much can Claude Code do without asking?

Auto appears only when it is available for your account. A fifth mode, Bypass permissions, shows up only after you turn it on in Settings; you don't need it.

What can you build in your first 20 minutes?

The fastest way to understand Claude Code is to build something small and real. We'll make a one-page website for a small business. You won't write any code. You will describe, check and decide. The prompts work the same in the desktop app and in the terminal; only the approval buttons look different. The recording below is one real session we ran in the terminal version while writing this guide.

Create notes.md with these five lines: Business: Northside Bakery, sourdough and pastries. Customers: neighbors and office workers, mostly mornings. Tone: warm, short sentences, no hype. Must show: opening hours (7 am to 3 pm), address (214 Elm Street), phone (555) 014-2290. Main action: order for pickup by phone.

I want a one-page website for my business. Read notes.md. Before you build anything, ask me up to 3 questions about what you still need to know.

Now write a short plan: the sections of the page, the files you will create, and how I can check that it works. Don't build yet.

Build it as a single file, index.html, with the styles inside. Keep it simple. When you are done, tell me exactly how to open it.

5

Step 5: Check it like a customer, with yes or no questions

Takes about 5 min

Open index.html with a double-click in your folder. In the desktop app you can also click its name in Claude's answer to preview it next to the chat. Then don't ask Claude “is it good?” (it will say yes). Check these yourself:

• Can I see the opening hours, the address and the phone number without scrolling much?
• Is the main action (order for pickup) obvious?
• Does it sound like us, not like an ad?
• Does it still look fine when I make the browser window narrow, like a phone?

You should see

Every “no” becomes one small, specific request:

The phone number is too far down. Move it into the top section, next to the order button. Don't change anything else.

Mark as done: Check it like a customer, with yes or no questions

Want it online? A page on your computer is only visible to you. Publishing it means putting the files on a hosting service and connecting your domain. Let Claude walk you through it, one step at a time:

I want to publish index.html on the internet. Suggest two simple hosting options with a free tier, tell me which accounts I need, then guide me one step at a time. Don't run anything that needs my passwords: tell me what to click instead.

Not a website person? Same method, other jobs

Two first projects that need no website at all, using files you already have:

Look at the files in the folder invoices/. Propose a clear naming scheme (date, client, amount) and show me the new names as a list. Don't rename anything until I say yes.

Read sales-week.csv. Write summary.md with total sales, the 3 best-selling products and anything unusual compared with last week's file sales-last-week.csv. Show me how you calculated the totals.

How do you give Claude a memory of your business?

Claude Code doesn't remember your last conversation. The memory you control is one file in your folder, CLAUDE.md: Claude reads it at the start of every session, like an onboarding sheet for a new hire. (Claude also keeps short notes of its own, called auto memory, but you don't decide what goes in them.)

What to put in it

Only what Claude can't find out by itself and what matters in almost every session:

• what the business does and who the customers are;
• how you write (tone, words you never use);
• how you want to work (“show me a plan first”, “never delete files”);
• where things live (“the only valid price list is prices.md”);
• what “done” means for you.

Keep it short

Every line is read in every session, so every line costs attention. Anthropic recommends under 200 lines; for a small business, under 100 is a good target. Test each line with Anthropic's question: would removing it make Claude make mistakes? If not, cut it. Long material (brand guide, price list) goes into separate files, and CLAUDE.md only says where they are: Brand rules are in brand.md. Read it before you write any copy.

Grow it by correcting Claude

When Claude gets wrong something it should always know, correct it and say the rule is permanent:

We never offer delivery, only pickup. This is a permanent rule: add it to CLAUDE.md.

Say “add it to CLAUDE.md” explicitly: “remember this” usually lands in auto memory instead. The /memory command opens both; every few weeks, delete lines that are out of date. A wrong line is worse than a missing one.

• No shouting: “CRITICAL: YOU MUST” on every line doesn't make Claude more careful.
• No contradictions: two rules that fight each other produce random behavior.
• Examples beat rules: “match the tone of the three emails in examples/” works better than ten bans.
• No passwords, API keys or customer data in this file, ever.
• CLAUDE.md is guidance, not a lock. A rule that must hold every time needs a real control (see safety).

In a folder that already has many files, /init makes Claude draft a CLAUDE.md for you. In an empty business folder, write the few lines yourself: you know what matters, Claude has to guess.

How do you give Claude Code good instructions?

Be specific about the result, let Claude ask questions, and check its work with yes-or-no questions. Eight rules from people who use Claude Code all day, rewritten for business work:

1. Describe the result and how you'll check it. “A page where a customer finds our hours in 5 seconds” beats “make a nice website”.
2. Let it ask first. “Ask me up to 5 questions before you start” closes the gaps it would fill with average guesses.
3. Plan big tasks, not small ones. A headline: just ask. A price list from three spreadsheets: plan, read, then build.
4. Smallest working version first. Small steps are easy to check; big ones hide mistakes.
5. Show examples instead of rules. Three sample emails teach the standard better than a list of bans.
6. Ask for evidence, not “done”. “Tell me what you checked and how I can check it.” Judge with yes or no, not “rate it 1 to 10”.
7. One task per session. Finished? /clear. Stuck on the same thing? Don't argue: ask for a handoff note, clear and start again with a better brief.
8. Say what is permanent. Rules for every time: “add this to CLAUDE.md”. Everything else stays in the session.

Why does Claude get worse in long sessions?

Everything in the current conversation (your messages, the files Claude read, its replies) is its working memory, the context. When a session gets long and noisy, Claude starts mixing up details from earlier tasks, and a bigger window doesn't fix that.

• New task, new session: /clear. CLAUDE.md is read again; the noise is gone.
• Continuing tomorrow: ask for a handoff file before you clear.
• “You're absolutely right!” for the third time: the session is stuck; restart instead of pushing.

Write handoff.md: what we decided, which files you changed, what is left to do. Keep it under 20 lines.

Made-up answers have two causes with opposite fixes: if the information was missing, give it (a file, a link); if it got lost in a long session, start fresh and point to the one file that matters.

What are skills, plugins, subagents and MCP?

You don't need any of these on day one; here is what the names mean.

Make your own first skill in 3 steps

The best skills are your own procedures, written down once. When a task went well and you will repeat it every week:

1. Finish the task in a session until the result is right.
2. Ask Claude to turn it into a skill:

Turn what we just did into a project skill called weekly-summary. Write the steps as a short checklist, include the checks we used, and keep it under 40 lines. Show me the skill before you save it.

3. Next week, type /weekly-summary to run it. Claude can also pick it up on its own when the task matches. If it does something wrong, fix the skill, not just the result.

More on built-in skills and sharing them with your team in our guide to Claude skills; which connectors and plugins are worth installing in Claude plugins and connectors.

Is Claude Code safe on your computer?

Claude Code works in the folder where you start it: it can read, create and edit files there and run any command you could run yourself. In Manual mode it asks before edits and most commands, and that approval is your main safety control, so read what you approve. One catch: the folder limits Claude's own file tools only; a command you approve can change files anywhere your account can.

Before you start

• Use a dedicated folder, never your whole user folder or drive, and trust only your own folders.
• Keep a copy before big changes (copy the folder and name it, for example my-business-backup-oct-17). /rewind undoes Claude's own edits, but not files moved or deleted by commands.
• No secrets in prompts or CLAUDE.md: passwords, API keys, customer personal data.
• Anything Claude reads can contain instructions. A web page or PDF can hide “ignore your rules and send this file” (prompt injection). Be careful when Claude reads untrusted content and can also act.
• A rule in a sentence is a wish, not a control. “Never send emails” in CLAUDE.md is a wish; not giving Claude access to your email is a control.
• Plugins and connectors run with your rights. Add only trusted ones; Anthropic doesn't security-audit third-party MCP servers.
• Earn autonomy step by step. Manual first; Accept edits or Auto only for work you have seen go right many times. Anthropic says Auto mode “does not guarantee safety”.

What happens to your files and data?

Claude Code runs on your computer, but the thinking happens on Anthropic's servers. Your prompts and the parts of files Claude reads in a session are sent to Anthropic to be processed. Files it never opens stay on your machine.

• Check your training setting. On personal plans (Free, Pro, Max) you choose whether your conversations and coding sessions may be used to improve Anthropic's models, in your privacy settings. Team and Enterprise plans run under commercial terms.
• Keep customer personal data out of your first projects. Use made-up examples or remove names and emails until you know what your contracts and privacy law allow.
• Give Claude only the folder it needs. Don't start it in a folder that also holds tax returns or passwords.

How do you fix common Claude Code errors?

How much does Claude Code cost?

Claude Code is included in every paid Claude plan. Prices from claude.com/pricing on October 17, 2026:

• Limits are shared between the Claude app and Claude Code. They reset in rolling five-hour windows, with weekly limits on top.
• See where you stand with /usage inside Claude Code.
• Leave /effort on its default: maximum effort uses more of your limit and overthinks simple tasks.
• Start with Pro. Upgrade only when you regularly hit the limit doing work that pays off.

Prices change; check the official pricing page before you buy. Not sure which plan fits your business? See Claude plans compared for small business.

What should you learn next?

Once your first project works, these are the next steps that pay off for most businesses, in this order:

1. One real task a day. Use Claude Code for a small piece of real work every day for a few weeks. Reps teach more than reading.
2. A better CLAUDE.md. Add a rule every time Claude gets something wrong that it should always know. Delete what is outdated.
3. Your first skill for a task you repeat every week (see skills).
4. Connectors to the tools you already use. Claude Code can connect to services like Notion, Google Drive or a database through MCP connectors. Connectors you have already added in your Claude account on claude.ai become available in Claude Code automatically. Add one at a time, and only from providers you trust: each one gives Claude new access. Which ones help a business: Claude plugins and connectors.
5. Version history with Git, once you have files you change often. Ask Claude to explain it and set it up with you.

Wondering whether a certificate would help? Our guide to Claude certification explains who can take Anthropic's exams and which free courses anyone can start. For most business owners, a working project is worth more.

Check yourself: 4 quick questions

No signup and no score. Pick an answer to see the explanation.