Guide

Claude Code vs Claude chat: which should you use?

Both run on the same Claude models and often the same subscription, but they work in very different places. This guide explains the difference, which jobs belong where, and how to hand work from one to the other.

Updated 30 October 2026

Quick answer: use Claude chat (claude.ai, the desktop app's Chat tab, or mobile) for thinking, writing, research and questions about documents you upload. Use Claude Code when the work lives in files on your computer or in a code repository: it reads the folder, edits files and runs commands. On Pro and Max both are included and share the same usage limits.

Details below were checked against Anthropic's help center and Claude Code documentation as of October 2026.

The core difference

Claude chat is a conversation. You type, attach files, and Claude answers in the chat. It can search the web, run Research, use connectors to apps like Google Drive or Slack, and keep background in Projects, but it doesn't change anything on your computer.

Claude Code is an agent that works inside a folder. Anthropic describes it as a tool that reads your codebase, edits files, runs commands and works with your development tools, including git. You give it a task in plain language and it plans the steps, changes the files and checks the result.

	Claude chat	Claude Code
Where it runs	claude.ai, desktop app Chat tab, iOS and Android	Terminal, VS Code, JetBrains, desktop app Code tab, claude.ai/code
What it sees	Your messages, uploads, project knowledge, connected apps	The project folder (or repository) you open, plus tools you connect with MCP
What it changes	Nothing outside the chat, unless a connector takes an action	Files in the folder; it can run commands, commit and open pull requests
Standing instructions	Project instructions and preferences	A `CLAUDE.md` file in the project, read at the start of each session
Plans	Free and paid plans	Pro, Max, Team, Enterprise or a Claude Console account

Tasks that suit Claude chat

Drafting and editing text: emails, briefs, posts, specs.
Research: web search for quick facts, or Research (paid plans) for multi-step investigation across the web and your connectors.
Working from documents: upload a PDF or add files to a Project's knowledge so every chat there can use them.
Thinking out loud: weighing options, planning, explaining a concept.

Tasks that suit Claude Code

Building and fixing software: describe a feature or paste an error, and it traces the problem across files and makes the fix.
Chores across many files: writing tests, fixing lint errors, updating dependencies, resolving merge conflicts, writing release notes.
Git work: staging changes, writing commit messages, creating branches and pull requests.
Automation: piping logs into claude -p, running it in CI, or scheduling recurring tasks.

A simple test: if the answer you want is text to read, use chat. If the answer you want is changed files, use Claude Code.

How to use both together

Plan in chat. Talk through the idea in a Claude Project, attach the background documents, and ask for a written spec or task list.
Save the decisions where Code can read them. Copy the agreed spec into a file in the project folder, or into CLAUDE.md for rules that should apply to every session. Claude Code doesn't see your chat history.
Open Claude Code in that folder. In the terminal, cd into the folder and run claude; in the desktop app, open the Code tab and choose the folder with the project folder control.
Start in Plan mode for bigger jobs. In Plan mode Claude explores and proposes a plan without editing code. Switch modes during a session when you're ready.
Bring results back to chat if needed. Paste a summary of what changed into chat to draft release notes or an update for your team.

New to the terminal side? Start with how to get started with Claude Code.

Good to know

Shared limits: on Pro and Max, the five-hour session limit and weekly limit are shared across Claude and Claude Code, so heavy use in one leaves less for the other.
API key trap: if the ANTHROPIC_API_KEY environment variable is set, Claude Code uses that key instead of your subscription, and API charges apply.
Desktop app: it includes Claude Code in the Code tab, so you don't need to install the command-line tool separately. A paid subscription is required.
Permissions: by default Claude Code asks before editing files or running commands. Other modes accept edits automatically; read what each does before switching.

If it doesn't work

Claude Code doesn't know what you decided in chat: it can't read your conversations. Put the decision in a file or CLAUDE.md in the folder.
Claude Code bills your API account instead of your plan: run /login and sign in with your Claude subscription, and check that ANTHROPIC_API_KEY isn't set.
Wrong account after signing in: run /logout, update with claude update, restart the terminal, then run claude and choose the right account.
You hit a limit in chat after a long coding session: that's the shared limit. See what to do when you reach Claude's usage limit.

Keeping chat and code in step with Workbranch

If the hard part is remembering what was decided in chat by the time you open Claude Code, the Workbranch connector and Claude Code plugin help: say "save this to Workbranch" in a Claude chat and it files the tasks, decisions and open questions into a project, and when a Claude Code session starts in a folder linked to that project, the plugin shows what's still open. There's a 3-day free trial at app.workbranch.ai.

Sources

Claude Code overview (Claude Code docs, checked 30 October 2026)
Use Claude Code Desktop (Claude Code docs, checked 30 October 2026)
Using Claude Code with your Pro or Max plan (Claude Help Center, checked 30 October 2026)
What are projects? (Claude Help Center, checked 30 October 2026)
Use Research on Claude (Claude Help Center, checked 30 October 2026)

Frequently asked questions

Do I pay separately for Claude Code?

Not on Pro or Max. Both plans include Claude on the web, desktop and mobile plus Claude Code under one subscription. You can also use Claude Code with a Claude Console account, which bills API usage instead.

Can Claude Code be used for things other than code?

It works on any files in the folder you open, so it can rename, sort or edit documents too. It is built and documented for software work, though, and it can run commands on your computer, so keep the default permission mode until you know what it will do.

Do Claude Code sessions show up in my chat history?

Treat them as separate. The desktop docs say each Code session keeps its own conversation history and project folder, independent of other sessions, so don't expect a chat to know what a Code session did.