Claude Code vs Claude: what's the difference?
Claude Code vs Claude explained: Claude is Anthropic's assistant for chat, documents, and research; Claude Code is its agent for working in a codebase.
Someone on the team says they "use Claude for coding." Someone else says they "use Claude Code." They're describing very different workflows: one copies snippets between a chat window and an editor; the other has an agent editing the repository and running the tests.
This guide sets out the difference from Anthropic's Claude Code overview, its desktop app docs, and the announcement that Cowork is now part of Claude, checked on 16 November 2026.
The short answer
| Claude | Claude Code | |
|---|---|---|
| What it is | Anthropic's AI assistant | Anthropic's agentic coding tool |
| Where | Claude app: web, desktop, mobile | Terminal, VS Code and JetBrains, desktop Code tab, web, mobile |
| Works with | Conversations, files, connected tools | Your codebase, shell, git, and dev tools |
| Typical use | Questions, writing, research, documents, decks | Building features, fixing bugs, refactoring, reviews |
| Project context | Projects, uploaded files, connectors | CLAUDE.md, skills, hooks, settings in the repository |
Claude
Claude is the assistant in the Claude app. You ask, it answers, writes, analyzes, and builds documents. Since September 2026, Anthropic has merged Cowork's capabilities into the main app: when a task needs it, Claude works across your files and connected tools, runs longer tasks while you're away, and produces documents, slides, and spreadsheets. See Claude Code vs Cowork.
For code, Claude in chat can explain, review a snippet you paste, or draft a function. It doesn't work inside your repository.
Claude Code
Anthropic describes Claude Code as an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools. It understands the whole project and works across many files.
It runs in several places:
- Terminal: the full-featured CLI
- IDEs: VS Code and JetBrains extensions
- Desktop app: the Code tab, next to chat and Cowork
- Web and mobile: cloud sessions that keep running when you close the laptop
Most surfaces need a Claude subscription or an Anthropic Console account. See Claude Code desktop vs CLI vs VS Code.
Which to use
| Task | Use |
|---|---|
| Explain a concept or an error message | Claude |
| Draft a PRD, spec, or design doc | Claude |
| Write a quick script you'll paste somewhere | Either |
| Fix a bug in your project | Claude Code |
| Add a feature across several files | Claude Code |
| Refactor, migrate, or review a pull request | Claude Code |
| Run a long coding task while away | Claude Code cloud session |
The rule of thumb: if the work lives in a repository, use Claude Code.
How they connect
- Same models. Both run Claude models.
- Skills can carry over. Skills you enable on your claude.ai account load in Cowork, cloud sessions, and terminal sessions signed in with that account, per Claude Code's docs.
- One desktop app. Chat, Cowork, and Claude Code's Code tab live in the same app.
- Separate project memory. Claude Code reads
CLAUDE.mdand settings from the repository; the Claude app uses its own projects and files.
The gap between them
Teams often plan in Claude and build in Claude Code. A decision reached in a Claude chat, such as "we're cutting bulk export from v1," doesn't reach the Claude Code session building the feature unless someone carries it over.
Where Lockstep fits
Lockstep carries it over. It captures decisions from PRDs, Slack, and pull requests, routes each to its owner for approval, and briefs Claude Code sessions on the ones that apply to the work. Session briefings are a Claude Code feature; any MCP client can query decisions through Lockstep's tools.
See how it works.
Sources checked 16 November 2026
- https://code.claude.com/docs/en/overview
- https://code.claude.com/docs/en/desktop
- https://code.claude.com/docs/en/skills
- https://claude.com/resources/articles/cowork-is-now-claude
Related reading
For getting started well, see Claude Code best practices. For how Claude Code remembers your project, see how Claude Code memory works.
Frequently asked questions
- What is the difference between Claude and Claude Code?
- Claude is Anthropic's general assistant in the Claude app, for conversation, writing, research, and file-based tasks. Claude Code is an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with development tools, from the terminal, IDE, desktop app, or browser.
- Can I code with regular Claude instead of Claude Code?
- For questions, snippets, and explanations, yes. For changes to a real project, Claude Code fits better: it works directly in your repository, runs tests, and edits many files, instead of you copying code between a chat and your editor.
- Is Claude Code included with a Claude subscription?
- Anthropic's docs say most Claude Code surfaces need a Claude subscription or an Anthropic Console account. Check Anthropic's pricing page for which plans include it, since plans change.
- Is Claude Code in the Claude desktop app?
- Yes. In the Claude desktop app, Claude Code is the Code tab, alongside chat and Cowork. It runs the same engine as the Claude Code CLI and reads the same configuration.
- Do Claude and Claude Code share memory and skills?
- Partly. Skills you enable on your claude.ai account load in Cowork, cloud sessions, and terminal sessions signed in with that account. Claude Code's project memory, such as CLAUDE.md, lives in the repository and isn't part of the Claude app's chats.
Keep reading