Claude Cowork Desktop Unusable in Corporate Environments Without Proxy
The Claude Cowork desktop app runs in an isolated VM with no awareness of host-system proxy configuration, causing all API calls to fail silently in corporate networks behind HTTP/HTTPS proxies. Unlike Claude Code CLI which supports standard proxy environment variables, Cowork provides no mechanism to configure or inherit proxy settings, completely blocking enterprise adoption.
Signal
Visibility
Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.
Sign up freeAlready have an account? Sign in
Deep Analysis
Root causes, cross-domain patterns, and opportunity mapping
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Solution Blueprint
Tech stack, MVP scope, go-to-market strategy, and competitive landscape
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Similar Problems
surfaced semanticallyStale ANTHROPIC_BASE_URL Produces Misleading Connection-Refused Error
When a stale ANTHROPIC_BASE_URL environment variable points to a dead local endpoint, Claude Code fails instantly with a generic connection-refused error, while standard diagnostics like curl and raw fetch succeed because they don't read that variable, leaving users no clear diagnostic path to the true root cause.
AI Coding Tools Have Inconsistent Plugin and Connection Behavior
Developer tool ecosystems have inconsistent plugin and connection behavior across desktop, mobile, and web versions of the same product. Workflows that work on one platform break on another due to missing integrations.
No clear path to bridge OpenAI Secure MCP Tunnel with Claude tooling
A developer asks how to connect OpenAI's newly released Secure MCP Tunnel to Claude Desktop or Claude Code, noting it is built for the OpenAI ecosystem only. Highlights an emerging cross-vendor interoperability gap in the MCP tooling space as multiple providers ship incompatible tunnel/transport implementations.
Claude Code Desktop Lacks GUI for Project Folder Selection and Session Switching
Launching Claude Code from the Windows desktop always opens the home directory with no way to select a project folder or switch between previous sessions via a graphical interface. Developers must use command-line navigation to reach project contexts. This friction affects Windows users who prefer GUI workflows.
Claude Desktop Unexpectedly Triggers Actions on a Separate, Unlinked Machine
A developer running Claude Desktop sessions independently on a Mac and a Windows machine found that finishing a task on the Mac caused a web app to launch on the unrelated Windows machine. The user was unaware of any cross-device or remote-session feature that would explain this behavior, raising concerns about undocumented cross-machine session linking.
Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.