Claude Cowork Plugins Launch: Enterprise Features & New Capabilities

When Anthropic launched Claude Cowork, plugins were already central to the platform — they're what turn a generic AI assistant into a specialist for your team's specific work. But the initial plugin framework was limited to what Anthropic shipped natively and what organisations could build internally. The Claude Cowork Plugins launch changes that substantially, opening the ecosystem to third-party developers and significantly upgrading the enterprise controls that IT and security teams need to deploy with confidence.

This is the update that makes Claude Cowork deployment at scale genuinely viable for larger enterprises. The governance gaps that CISOs were raising in early evaluations — "how do we control which plugins employees can access?" — have been directly addressed. Here's a full breakdown of what's new.

What Changed in the Plugins Launch

Before this update, Claude Cowork plugins were essentially bundles of skills, connectors, and agent configurations that Anthropic or internal developers could create. The platform supported custom plugin development, but there was no marketplace, no third-party distribution mechanism, and limited enterprise governance tooling. You could build a plugin, but deploying it to your organisation was a manual, IT-mediated process.

The Claude Cowork Plugins launch introduces three major changes: a formal plugin SDK and distribution framework that third-party developers can use to build and publish plugins; an enterprise admin portal with granular controls over which plugins are available to which users; and a set of pre-built integrations with enterprise software platforms that previously required custom connector development.

For organisations that have already deployed Claude Cowork, the update is largely additive. Your existing plugins continue to function. You gain access to new governance controls and a broader library of pre-built options. For organisations that were waiting to deploy pending these controls, the timing to reassess is now.

New Enterprise Features

Third-Party Plugin Framework

The most significant architectural change in the Claude Cowork Plugins launch is the opening of the platform to third-party developers. Anthropic has published a plugin SDK that allows any developer — whether a software vendor, a systems integrator, or an internal team — to build and publish Cowork plugins using the same framework as Anthropic's own plugins.

A Cowork plugin consists of three components bundled together: skills (pre-written, reusable Claude instructions for specific tasks), connectors (authenticated integrations to external applications via MCP servers or direct API calls), and a manifest that defines the plugin's capabilities, permissions requirements, and UI elements. The SDK handles the packaging, and the marketplace handles the distribution.

Third-party plugins go through an approval process before appearing in the public marketplace. Anthropic reviews them for security, data handling compliance, and functional accuracy. Enterprise organisations can also maintain a private plugin registry — their own internal marketplace — where they publish custom plugins built for their specific workflows without going through the public review process.

The implication for our Cowork plugins guide is significant: organisations now have three deployment options. Use pre-built marketplace plugins, build custom plugins internally using the SDK, or engage implementation partners like us to build custom plugins on your behalf. That flexibility is exactly what enterprise procurement needs.

Admin Controls and Governance

The admin portal is where the enterprise governance story for Claude Cowork plugins finally becomes complete. IT administrators now have a single dashboard to manage the entire plugin lifecycle for their organisation.

Plugin approval workflow: administrators can set a policy where all plugins from the public marketplace require explicit admin approval before any user can install them. This prevents shadow IT situations where employees install plugins that access sensitive business data without IT's knowledge.

User and group assignment: plugins can be assigned to specific Active Directory or SSO groups. A sales plugin that connects to Salesforce is automatically available to everyone in the Sales group and not visible to anyone else. This is the kind of access control that regulated industries require before they can deploy AI agents across their workforce.

Data handling classification: each plugin can be tagged with a data classification level. Plugins that handle confidential data require additional approval steps and are subject to additional audit logging. This is a direct response to the compliance requirements that legal, financial services, and healthcare organisations brought to early evaluations.

For organisations that have been waiting to deploy Claude Cowork at scale pending these governance controls, the admin portal removes the primary barrier. If you're in that position, our Cowork deployment service can now proceed with a governance architecture that meets enterprise requirements from day one.

Impact on Current Deployments

If you've already deployed Claude Cowork in your organisation, the plugins update affects you in several ways. First, your existing custom plugins continue to function exactly as before — the update is backwards compatible. You don't need to migrate or rebuild anything.

Second, you now have access to the admin portal governance controls regardless of whether you were using them before. IT administrators should take a pass through the new settings to ensure your existing plugin permissions align with your security policies. In particular, check whether the new version management controls should be applied to your existing plugins to prevent automatic updates to versions you haven't reviewed.

Third, you now have access to the marketplace plugins. Evaluate which newly available third-party plugins might serve your team better than existing custom solutions. The economics often favour using a well-maintained marketplace plugin over maintaining equivalent custom code internally.

Build vs Buy: When to Create Custom Plugins

With the marketplace now available, the build-vs-buy question for Cowork plugins has a cleaner answer than before. Use marketplace plugins when a vendor has already built a high-quality plugin for your target application — check the approval status, review the security documentation, and test it in a sandbox. Custom plugins make sense when your integration requirements are specific to your organisation's data model, terminology, or workflow logic that a generic plugin can't address.

The hybrid approach works well for most large enterprises: use marketplace plugins for commodity integrations (standard Salesforce CRM queries, generic document analysis), and build custom plugins for your most distinctive workflows — the ones that encode your organisation's specific processes and domain knowledge. Those custom plugins are where the real competitive value of Claude Cowork lives, and they're also where a specialist like us adds the most value.

Your Action Plan

For organisations currently deploying or evaluating Claude Cowork, here's the priority sequence following the plugins launch. First, if you have an existing deployment, configure the admin portal governance controls before adding any new plugins — establish the approval workflow and user group assignments. Second, audit the marketplace for plugins that cover your existing manual or custom integration needs. Third, identify the two or three highest-value custom plugin opportunities — the workflows that are unique to your organisation and would benefit most from AI agent automation.

For organisations that were evaluating Cowork but waiting on governance features, this is the right moment to restart that evaluation with fresh eyes. The platform is now materially different from what you may have assessed six months ago.

We're actively building custom plugins for clients across financial services, legal, and operations. If you want to discuss your plugin strategy — whether that's evaluating the marketplace, planning a custom build, or auditing your existing deployment — get in touch. For the full picture on how Cowork plugins work architecturally, see our detailed Claude Cowork plugins guide.