Getting Started with Claude

This guide explains what Claude is, how it helps you do more of what you're good at, and how it can automate complex work.

Set up Claude Code

See what's possible, then make it yours.

The video below showcases concepts we'll cover later (AI agents, different Claude models, context windows, and skills). What you see is a starting point. Never accept AI's first tryAI SlopContent made with artificial intelligence that is perceived as lacking in effort, quality, or meaning, and produced in high volume.Source: Wikipedia as the final version. Your job is to refine it, poke at it with prompts, and make something you'd put your name on.

"Claude" is both a model and a product.

You can think of modelsLarge Language Model (LLM)Large Language Models are AI systems trained on broad data to understand and generate human language. Claude's models (Opus, Sonnet, Haiku) differ in capability, speed, and cost.Source: Anthropic docs as the brains and productsProductA user-facing application built on top of one or more models. Each product (Claude Chat, Claude Code, Cowork) provides a different interface and toolset for interacting with the underlying AI.Source: Anthropic as the hands and feet. Models are the Artificial Intelligence itself, each with different tradeoffs between capability and speed. Products are the user interfaces that give those models different tools to work with.

Models
Opus
Opus
Most capable – best multi-step reasoning and least likely to miss nuance or cut corners
Sonnet
Sonnet
Faster responses – strong at coding, structured output, and research
Haiku
Haiku
Near-instant responses – good for summaries, short tasks, and quick questions
Products
Claude Code
Claude Code
Runs on your computer – works directly in your files, the most you can do with Claude
Claude Cowork
Claude Cowork
Runs in desktop app – works on your files with no setup needed, but less control than Code
Claude Chat
Claude Chat
Chat in your browser (or desktop app) – upload files, download outputs to your computer
How can I help you today?
+
Opus 4.6
Opus 4.6
Sonnet 4.6
Haiku 4.5
Each product lets you pick a model

The model sees things differently.

Large language models were trainedTrainingTraining happens in two stages. In pre-training, the model reads enormous amounts of text from the internet (books, articles, websites, code) and learns patterns in language, facts, and reasoning. Then, in post-training it learns to follow instructions, answer questions helpfully, and have conversations. on text from the internet, then taught to help with tasks. They each have a knowledge cutoff Knowledge cutoffThe date when the model's training data ends. Unless you tell it or it searches the web, the model has no awareness of events, discoveries, or changes that happened after this date. date, meaning they have no awareness of events after training data ends. They do not learn from your conversations, or improve the more you use them. But training also shapes how they "see" the world. The example here shows this in action: the model fails simple counting when left to its own devices, but succeeds when using code to find the answer. This comes down to how it sees your inputs.

A model does not process text, audio, video, and images like we do. It breaks all this data into tokensTokenA small chunk of text, roughly one word or word-fragment. The model reads and generates text one token at a time. Everything (text, code, images) gets converted to tokens. – small chunks, each corresponding to a unique ID in its own vocabulary. Your question, any documents you attach, and every word the model writes back are all seen as tokens. This is why some things that seem trivial to us, like counting dots in a message, can trip it up – it can only see these tokens. Together these tokens make up the model's context window.

(This visual uses a simplified tokenizer. To see how real models tokenize text, try Tiktokenizer)

Without code
how many dots? .................................
There are 50 dots. ✗ Wrong – there are 33
With code
how many dots? .................................
use code
I'll count the dots for you using code.
Count the dots programmatically
There are 33 dots. ✓ Correct
What the model sees after tokenization
how many dots? .................................
Type here...
tokens
User Input
unique IDs

Every conversation, the model starts with a fresh context window.

The model's context windowContext WindowA fixed-size container (measured in tokens) that holds everything the model can see in one conversation. When it fills up, older messages are summarized to make room (a process known as 'compaction'). holds tokens from your prompts, its own thinking, file uploads, and more. As the context window fills up, costs rise and performance degrades (sometimes called "context rot"). There are several ways to get information in, from simple copy-paste to connectorsMCP (Model Context Protocol)An open standard that lets Claude reach into external systems like SharePoint, Slack, Google Drive, Jira, and databases. Called "connectors" in the Claude Chat interface; in Claude Code, you configure them as MCP servers. that let the model interact with external apps and data sources. Each product will also preload a system promptSystem PromptHidden instructions sent to the model by the product or platform before your conversation begins. They shape Claude's tone, rules, and behavior without being visible to you. Every Claude product has one and they vary widely. and any instructions you've saved. Claude can also load skillsSkillA pre-written set of instructions and resources (e.g., templates) that load into the context window on demand, giving Claude expertise for a specific task (creating slides, working with PDFs, writing docs, etc.). – pre-packaged instructions with expertise for tasks like creating documents, building websites, and writing in a specific tone or style. Skills load only when needed, so Claude gets the right know-how without always taking up valuable context window space.

What fills the context window
New chat Window nearly full 200K tokens
context window
0 / 7

The tools below bring outside information into the context window

Web search & browsing Search the web or interact with live pages like a human would
File upload Drag PDFs, spreadsheets, images, or code into Claude Chat
Direct file access Claude Code and Cowork read and write to your local files
Connectors (MCP Servers) Interact with external sources and apps like M365, Notion, Figma

With the right building blocks, AI agents can automate work.

In the demo video, Opus reads templates and orchestrates the team, Haiku handles high-volume file scanning, and Sonnet summarizes only the relevant files. Each agentAI AgentA system that autonomously performs tasks by designing workflows with available tools. AI agents can encompass a wide range of functions beyond natural language processing including decision-making, problem-solving, interacting with external environments and performing actions.Source: IBM docs gets its own context window, so each one stays focused on its task without being distracted by what the others are doing. Skills play a role here too: when a task requires specialized knowledge (like how to orchestrate an AI team), each agent can load the relevant skill, giving it expert-level instructions without cluttering the other agents' windows. AI excels at using these building blocks. As a user, this means you need to build really good blocks – clear instructions, good templates, and well-organized files.

How Claude Code can orchestrate work

YOU Here are files from our partner. Get our AI team to build them a solution. Opus Opus SKILL.md Opus reads skill to orchestrate AI team templates Haiku Opus spawns subagents while reading templates many files index.md Haiku scans all files and identifies relevant ones Sonnet summary Sonnet reads relevant files and summarizes key findings briefing.html Opus uses context from SKILL.md, templates, and the Sonnet agent summary to make a client briefing
1 / 6

Each product gives you different capabilities.

Most of what you create – whether it's a presentation, a website, or a document – is code that gets written. When you learn to manipulate that, you can do anything. This guide starts with Claude Code because it gives you the most influence for bringing your ideas to reality. The other products are always available if you need them.

Capability CodeCode CoworkCowork ChatChat
Fully orchestrate a team of agents
Manage context window usage
Build, test, and deploy software end-to-end
Read and write local files
Work in the background
Write and run code
Connect to external tools
Search the web
Save instructions across conversations

Set up Claude Code and build something.

To set up Claude Code, copy the prompt below and paste in Claude.ai. The chat will guide you, one step at a time.

I need your help installing and setting up Claude Code on my Windows machine and explaining concepts as we progress. Walk me through this, step by step: 1. Install Git for Windows – Explain what Git is and why Claude Code needs it. Walk me through the installer screen by screen if I share screenshots. Make sure I understand what PATH means and why it matters. After installation, have me verify it worked by running a command. 2. Handle the Git Bash path proactively – A common issue on Windows is that Git sometimes installs to a non-default location (like AppData\Local\Programs\Git instead of C:\Program Files\Git), which causes Claude Code's installer to silently fail. BEFORE I install Claude Code, have me run a command to find where Git Bash actually installed, and then have me set the CLAUDE_CODE_GIT_BASH_PATH environment variable as a permanent User variable pointing to the correct bash.exe location. Do not skip this step – it prevents a confusing problem later. 3. Install Claude Code – Walk me through running the official Windows installer (irm https://claude.ai/install.ps1 | iex) in PowerShell. Help me verify the installation worked and that the "claude" command is recognized. If I need to add anything to my PATH, walk me through that with exact steps (System Properties > Environment Variables). 4. Install VS Code and the Claude Code extension – Explain what VS Code is and why I'd want to use it. Walk me through installing VS Code, then installing the Claude Code extension from the Extensions marketplace. Explain that VS Code with the Claude Code extension is recommended because it provides a user-friendly interface: see files in the side bar, edit them in the middle, and chat with Claude Code in a panel. Users can branch out to using Claude Code directly in a terminal, but this is the easiest way to get most of the Claude Code experience. 5. Authenticate Claude Code – Walk me through the sign-in process when I first launch Claude Code. 6. Explain CLAUDE.md – Once everything is running, explain what a CLAUDE.md file is: a markdown file I put in a project folder that gives Claude Code background context about my work (like a briefing document it reads automatically every session). Explain what Markdown is in simple terms. Then ask me if I'd like help creating my first one. Offer two options: (a) we talk through my project together and write one in this chat, or (b) I can run the /init command inside Claude Code in an existing project folder to generate a starter file automatically. Important guidelines for this conversation: - Explain every concept as you introduce it (terminal, PATH, environment variable, extension, Markdown, etc.). - Go one step at a time. Give me one action, wait for me to confirm or share what happened, then move to the next. - Encourage me to copy and paste whatever I see on my screen with text or snips/screenshots (error messages, command output, etc.). - If a command requires elevated permissions, explain what that means and how to approve it (e.g., "Run as Administrator"). - Don't install extra tools (Python, Node.js, etc.) unless I specifically need them for something. Keep the setup minimal. - Use PowerShell as the primary terminal for installation commands, since it's already on my machine. Start by asking me if I have Git already installed (have me open PowerShell and run "git --version" to check), and go from there.