anthropic has officially rolled out a Third-Party Inference feature within Claude Desktop, fundamentally transforming the APPlication into a versatile shell capable of routing requests to external providers. This update allows the Cowork and Code interfaces to forward reasoning tasks to enterprise-grade endpoints such as Amazon Bedrock, Google Vertex AI, Microsoft Foundry, or custom gateways.
Enterprise-First compliance and Security
Officially, this feature is positioned as a robust solution for enterprise deployment, specifically targeting organizations with strict data governance needs. It caters to:
Regulated enterprises prohibited from sending data to external vendors.
International organizations with specific Data Residency requirements.
Public sector entities operating under FedRAMP or ITAR Frameworks.
Configuration is streamlined via MDM (Mobile Device Management) tools. In this mode, conversation data is routed exclusively to the user-specified inference endpoint and processed locally, ensuring that no data traverses Anthropic’s servers.
The Community Hack: running GPT and Grok on claude
Beyond the official enterprise use case, the developer community has quickly identified a powerful workaround. By enabling Developer Mode (via Help > Troubleshooting > Enable Developer Mode), users can manually configure the Gateway Base URL.
This has allowed users to point Claude Desktop at third-party aggregators like OpenRouter, effectively turning the interface into a universal CLIent. Users have successfully run non-Claude models, including GPT-5.4 and Grok 4.20, directly within the Cowork environment. It is important to note that this "Universal Agent" capability is an extension of the Gateway API by the community, rather than an officially supported feature for non-Claude models.
While the flexibility is a major win, the Third-Party (3P) mode currently has specific functional constraints:
Available Tabs: Only Cowork and Code tabs are functional.
Disabled Features: The Chat tab, as well as the Skills and Plugins stores, are unavailable in 3P mode.
Network: Users must manually configure allowlists for network egress to ensure connectivity.
Comments & Questions (0)
No comments yet
Be the first to comment!