Claude vs Claude Code: which plugins work where
The Claude app is where you chat and, with Cowork, hand Claude multi-step work. Cowork and chat are merging into one app, while Claude Code stays a separate coding tool for the terminal, IDE, desktop and web. Plugins install in both, but each loads a different set of parts.
Last checked against Anthropic's documentation on .
Side by side
What it is
- Claude app (chat and Cowork)
- Anthropic's assistant app. Cowork brings Claude Code's agent to knowledge work and is merging with chat into one app
- Claude Code
- An agentic coding tool that reads your codebase, edits files and runs commands
Where you use it
- Claude app (chat and Cowork)
- Web, Claude Desktop (macOS, Windows, Linux in beta) and mobile
- Claude Code
- Terminal, IDE extensions, desktop app, and web
Plugins
- Claude app (chat and Cowork)
- Chat loads skills, commands and remote connectors. Cowork also runs sub-agents and hooks, and local MCP servers when the session runs on your computer
- Claude Code
- Loads all of those, plus executables in a top-level bin/ directory, LSP servers, output styles, themes and settings
Add plugins
- Claude app (chat and Cowork)
- Customize, then Plugins, in the left sidebar: Discover and Add, or add a marketplace
- Claude Code
- /plugin in a session, or claude plugin install
Marketplace hosts you add
- Claude app (chat and Cowork)
- GitHub and GitHub Enterprise, public GitLab and Bitbucket
- Claude Code
- Any Git repository, GitHub shorthand, URL or local path
Which should you use?
Anthropic's Dispatch guide routes coding work (fix a bug, open a pull request, run tests) to Code and knowledge work (research, write a document, organize files) to Cowork. The same plugin folder installs in both, but each loads a different subset, so a plugin can look complete in one and partial in the other. Check a plugin's README, then see our marketplace guide, Cowork guide and best plugins by category.
The same plugin can load different parts
A plugin folder is portable: the same directory installs in Cowork and in Code. But each surface loads its own subset of components, so a plugin that feels complete in Code - with hooks reacting to events and sub-agents running in the background - can look like only skills and commands in Cowork or chat. That is a platform difference, not a broken install.
Claude Code (v2.1.273 and later) also picks up the plugins saved to your Claude account each time it starts. The sync is one-way, from your account to Code: plugins you install from the Claude Code command line stay on that machine and are not added to your account. It only happens in sessions signed in with your claude.ai account, and Anthropic's Help Center says it does not happen when Claude Code uses an API key or runs on a cloud provider such as Amazon Bedrock. If a plugin shows up in one tool and not the other, check the version and how you sign in before reinstalling. The component model itself is explained in plugins vs skills vs connectors, and the plan and device prerequisites in plugin requirements.
Questions
Do plugins work in both Claude and Claude Code?
Yes. A plugin saved to your Claude account works in chat, Cowork and Claude Code, and syncs to Claude Code version 2.1.273 and later. Each loads a different set of its parts: chat loads skills, commands and remote connectors, Cowork also runs sub-agents and hooks, and Claude Code loads all of those and more.
Should I use the Claude app or Claude Code?
Use Claude Code for coding work, such as fixing a bug, opening a pull request or running tests. Use the Claude app, with Cowork, for knowledge work such as research, writing a document or organising files.
Is Cowork part of Claude Code?
No. Cowork brings the same agent to knowledge work in the Claude app and is merging with chat into one app. Claude Code stays a separate product for developers.
Sources: Cowork overview, Claude Code overview, Plugin feature support across platforms, Run tasks in the background with Dispatch.