What Claude Code is (and how to start)

The name is the first hurdle, so let’s clear it: the “Code” describes where the tool came from, not who it is for. What Claude Code actually does is open the files on your computer, do work inside them, and show you what it changed. Spreadsheets, research folders, documents, drafts — all of that counts. Developers got it first; nothing about it is only for them.

The way you meet it is a normal app. You download Claude Code Desktop, sign in, and drag a folder onto it. On one side is a chat; on the other is the file pane, showing what Claude is reading and editing as it goes. There is nothing to type at a black screen, which is the single biggest reason people who tried this a year ago and gave up should try again.

The guides below run roughly in the order you’d want them. Start with what the thing is, then the step-by-step first session, then a five-day plan for making it a habit rather than a novelty — and once it is a habit, the workflows piece is where most of the compounding happens. Two of them are comparisons, because “how is this different from ChatGPT?” and “how is this different from Cursor or Copilot?” are the two questions that most often block a decision.

The commands listed further down split into two kinds. A handful you type straight into the chat to manage your account and your setup — /login, /status, /config, and /doctor when something is misbehaving. The other two, claude and claude update, are terminal commands: the Power-Track way in and out, useful to recognise but not something you need on day one. If you’re wondering whether you’ll be pushed toward that terminal eventually, the app vs the command line answers it directly.

It builds you tools, not just edits

The part that surprises people who don’t write software is that Claude doesn’t only change the files in a folder — it can write a small program to work on them, and build you something to look at the result in.

You never see the program. You describe the outcome in the chat, Claude proposes the work, you approve it, and what lands in the folder is the thing you actually wanted:

• 300 photos named DSC_0001.jpg, DSC_0002.jpg… → “rename these by the date each was taken.”
• A sales.csv you can’t make sense of → “turn this into a bar chart I can open in my browser.”
• A folder of 40 PDF invoices → “pull the total from each one into a single table.”

None of those are coding tasks. They’re your own files plus a sentence — and each one is the kind of job that was previously either an afternoon of manual work or a request to someone technical who had better things to do. The output is a real file sitting in a real folder: if the chart is sorted wrong you say so in the chat and it gets redone, the same as any other edit.

Two habits are worth picking up in the first hour, and both have their own pages: reviewing what it changed before you accept anything, and understanding the permission prompts rather than clicking through them. Everything else you can learn as you go.