Why Claude Cowork breaks under most corporate VPNs and how to fix it. Immediate workaround for operators, longer fix for IT, captive-portal edge cases.
TL;DR. Cowork's number-one reported issue: it does not work properly with most corporate VPNs. The immediate fix for operators is to disconnect the VPN and try again. The longer fix is for IT — split-tunnel exception and an Anthropic endpoint allowlist. The VPN conversation has to happen in week one of any deployment, not week four.
Cowork stops responding, can't reach the web, or behaves erratically while a corporate VPN is connected. The root cause is a routing conflict between Cowork's local components and the VPN's network policy.
This works in the vast majority of cases. It is also a workaround, not a fix.
For operators who must stay on VPN for compliance reasons:
There is no Option D where Cowork works through the VPN unmodified. Pick A, B, or C and commit.
claude.ai resolves correctly.The VPN issue is the single biggest headwind to Cowork adoption in enterprise IT. We bring an explicit "ask IT to whitelist X, Y, Z" template to every deployment so the VPN conversation happens in week one, not week four. Catch it late and you waste two weeks of the pilot owner's time on a problem that is fixable in a single IT ticket if it is named clearly.
Tinkso runs the deeper engagement behind the playbook on this page. Book a 30-minute call.