How Claude Cowork and Claude Code Plugins Differ: Architecture and Usage

Claude Cowork and Claude Code plugins share the same marketplace manifest but operate in completely different runtime environments—Cowork runs plugins in Anthropic's cloud via web UI, while Code executes them locally through CLI commands.

The anthropics/claude-plugins-community repository hosts a unified plugin ecosystem that serves both products through a single manifest file. While the underlying .claude-plugin/marketplace.json catalog is identical, the installation methods, execution contexts, and security models create fundamentally different integration patterns for end-users versus developers.

Shared Marketplace Infrastructure

Both products consume plugins from the same central registry. The repository maintains a single source of truth at .claude-plugin/marketplace.json, which lists all community-contributed extensions available to either platform.

This unified approach means plugin developers maintain one manifest entry that automatically becomes available to both Claude Cowork users browsing the web interface and Claude Code users working in their local development environments. According to the repository's README.md, this shared infrastructure simplifies distribution while supporting distinct consumption patterns【README#L1-L22】.

Installation and Access Methods

The primary distinction between Claude Cowork and Claude Code plugins emerges in how users discover and install them.

Claude Cowork: Browser-Based Marketplace

Claude Cowork plugins are installed through the web UI at claude.com/plugins. End-users browse the marketplace in their browser, click installation buttons, and instantly activate plugins within their chat sessions.

The README.md explicitly directs Cowork users to "Install plugins from [claude.com/plugins]"【README#L13-L16】, emphasizing the zero-installation, cloud-native workflow designed for non-technical users who need immediate access to augmented capabilities without local setup.

Claude Code: Command-Line Interface

Claude Code plugins require CLI commands using the claude tool. Developers must first register the community marketplace, then install specific plugins through terminal commands.

The repository documentation shows the exact syntax: claude plugin marketplace add … to register the source, followed by claude plugin install … to add individual plugins【README#L17-L22】. This approach integrates directly into developer workflows within IDEs like VS Code, where the Claude Code extension manages plugin lifecycle.

Runtime Environments and Security Models

Where and how plugin code executes represents the most significant architectural divergence between the two products.

Cloud Execution in Claude Cowork

Plugins for Claude Cowork run inside Anthropic's hosted cloud environment. The code executes on Anthropic's servers, with results communicated back through the web UI chat interface.

This server-side execution model creates a sandboxed security boundary where plugins cannot access the user's local file system. The security model relies entirely on Anthropic's server-side isolation, making it suitable for general data retrieval and API-driven tasks without exposing local machine resources.

Local Execution in Claude Code

Claude Code plugins execute locally within the developer's IDE or terminal, operating as extensions to the Claude Code CLI tool. This architecture grants direct file-system access and integration with local project files.

Because plugins run under the user's local OS security policies, they can read, write, and manipulate files within the development environment. This local execution model supports complex development workflows where AI assistance requires deep integration with version control systems, build tools, and project-specific configurations.

Practical Installation Workflows

The following examples demonstrate the distinct workflows for each product using the shared anthropics/claude-plugins-community repository.

Installing for Claude Cowork (Web UI)

1. Navigate to https://claude.com/plugins
2. Locate the desired plugin (e.g., "GitHub Repository Analyzer")
3. Click the "Install" button
4. Return to your Cowork chat and invoke with: /github analyze org/repo

This workflow requires no local installation or command-line knowledge. The plugin immediately appears in the chat sidebar and processes commands through Anthropic's cloud infrastructure.

Installing for Claude Code (CLI)

# Register the community marketplace once per environment

claude plugin marketplace add anthropics/claude-plugins-community

# Install a specific plugin (e.g., GitHub tools)

claude plugin install github-tools@claude-community

# Use within your IDE or terminal

claude github-tools repo-summary --repo "anthropics/claude-plugins-community"

The CLI workflow creates a local installation managed by the Claude Code tool, allowing the plugin to access your local Git repositories and development environment variables.

Summary

• Claude Cowork and Claude Code plugins share the same marketplace manifest at .claude-plugin/marketplace.json but serve different user personas.
• Cowork plugins install via browser at claude.com/plugins and execute in Anthropic's cloud sandbox, isolating them from local systems.
• Code plugins install via claude plugin install commands and run locally, enabling direct file-system access and IDE integration.
• Both products reference identical plugin metadata from the anthropics/claude-plugins-community repository, ensuring consistency across deployment targets.

Frequently Asked Questions

Can I use the same plugin in both Claude Cowork and Claude Code?

Yes. The anthropics/claude-plugins-community repository maintains a single marketplace registry that both products consume. When you publish a plugin to this registry, it becomes available to Cowork users through the web interface and Code users through the CLI, though the execution context (cloud vs. local) will differ based on the product.

Do Claude Code plugins have access to my local files?

Yes. Unlike Claude Cowork plugins that run on Anthropic's servers, Claude Code plugins execute in your local environment with permissions governed by your operating system. This allows them to interact with your project files, read configuration data, and execute development tools, but also requires trusting the plugin source code.

How do I add the community marketplace to Claude Code?

Run the command claude plugin marketplace add anthropics/claude-plugins-community in your terminal. This registers the community repository as a plugin source, allowing you to install any listed plugin using claude plugin install <plugin-name>@claude-community. You only need to add the marketplace once per development environment.

Why do Claude Cowork plugins use a web UI instead of CLI?

Claude Cowork targets end-users who augment their AI chat experience without requiring local development tools. The browser-based installation at claude.com/plugins eliminates the need for terminal access, package managers, or local configuration, making AI extensions accessible to non-technical users who rely entirely on cloud-based interactions.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}