Cowork issues on the web app
Issues the maintainers labelled both platform:web and area:cowork.
74 issues · 54 open · 20 resolved (27%) · first seen Apr 4, 2026
Is this getting better or worse?
This class of problem is still growing. 57 new reports in the last 90 days vs 14 in the 90 before — +307%. The open backlog peaked at 54 in 2026-10 and sits at 54 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
5 of these reports name the Claude Code build they were running, spanning 3 releases. Heaviest reporters:
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 39 days across 20 closures. Of the 20 closures with a recorded reason, 5% were closed as completed and 19 as not-planned or duplicate. The most recent completed fix landed in 2026-09.
Workarounds reported by the community
12 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Claude Code Projects (Beta). The auto-mode permission check blocks approved work in cloud environments and Projects
- …and 24 September 2026). The one allowed attempt was step 7. Workaround: run the same steps in a local Claude Code session, which does not have this check. Claude Model Opus Is this a regression? I don't know Last Working…
Found in the description of #96775 · still open - [BUG] Cloud scheduled Cowork task completes and generates final message but hangs indefinitely at "Sending notification" — push/email never delivered
- …sidebar under Scheduled with the spinner still active. The workaround (and the diagnostic tell) is that simply opening the stuck session from the Scheduled sidebar unblocks it : within about a minute of opening it, the…
Found in the description of #79409 · still open - session_info MCP tools (list_sessions, read_transcript) missing from Cowork sessions since 9/22–23
- …r id. 5. Interim archive path. Until returns, the practical workaround people have used is exporting/copying from the Cowork UI history (or any official export) on a manual cadence, and keeping the nightly job’s “archive…
Found in the thread of #97896 · still open - [BUG] Claude Cowork blocked by "Usage credits required for 1M context" — usage credits enabled, /model workaround non-functional, triggers at 7% session usage during compaction
- …uring context compaction mid-session, not at the start. The workarounds suggested in the error message do not work — typing /model does nothing in the Cowork interface, and the error persists despite usage credits being…
Found in the description of #65756 · resolved - [BUG] Cowork HTTP MCP plugins: silent connection drops, Authorization header dropped on tools/call, and GitHub-disconnect "fix" wipes plugins for the whole workspace
- …P plugins unusable on multi-user workspaces without painful workarounds. Verified against over multiple sessions and confirmed by at least two members of our team. The four issues: 1. Silent connection drops within a ses…
Found in the description of #56122 · resolved
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 1–74
Ranked by community engagement (reactions weighted over comments).
- [BUG] Gmail connector OAuth hard-blocked by Google ("This app is blocked") — cannot reconnect in CoWork
- [FEATURE] Visible context-window usage indicator in Cowork (parity with Codex / Claude Code status line)
- Ultraplan remote session became unresponsive, losing extensive iterative planning work
- [BUG] GitHub push permission (403) in Claude Code Remote session - read only despite repo being added as source
- [BUG] Custom MCP connectors on scheduled tasks don't load until a human sends a message
- [BUG] Claude Code Projects (Beta). The auto-mode permission check blocks approved work in cloud environments and Projects
- [BUG] Cloud scheduled Cowork task completes and generates final message but hangs indefinitely at "Sending notification" — push/email never delivered
- Cowork scheduled tasks: permission classifier refuses owner-authorized email sends ("Real-World Transactions"); same send succeeds in an attended session; no per-task allow
- [GitHub integration] Chat-Project cloud session (linked to desktop app) cannot push or call GitHub API on repos the Claude GitHub App is installed on; no way to add session sources; Claude Code Projects not rolled out to account
- session_info MCP tools (list_sessions, read_transcript) missing from Cowork sessions since 9/22–23
- [BUG] A Stop hook's blocked reply is still shown to the user, so every retry reads as the assistant repeating itself
- [BUG] Claude Cowork blocked by "Usage credits required for 1M context" — usage credits enabled, /model workaround non-functional, triggers at 7% session usage during compaction
- [BUG/FEATURE] claude.ai Cowork (web): dismissed banners keep coming back; need one global setting to turn off non-critical notices
- [BUG] I am eligible for 2x more usage until July 5, but it doesn't apply on my usage page
- [BUG] Cowork HTTP MCP plugins: silent connection drops, Authorization header dropped on tools/call, and GitHub-disconnect "fix" wipes plugins for the whole workspace
- [Bug] Remote session stuck after plan generation without remote configuration
- Projects: keep a folder's "default local folder" approval when its Remote Control server restarts
- [Cowork/claude.ai] Cannot add anthropics/claude-plugins-community as a marketplace; community plugins (e.g. eli5) missing from the directory
- [BUG] Resource not accessible by integration" 403, GitHub
- claude.ai: merging Chat and Cowork into one surface (7-8 Oct 2026) broke working Cowork sessions
- Permission prompt not showing in Project thread
- [BUG] Conversations locked after moving personal account to Team org: "This conversation has moved to a view that isn't available here"
- Projects: coordinator + thread sessions merged PRs with red CI and ignored AGENTS.md during multi-thread implementation
- [BUG] A blocking Stop hook's refused reply is still rendered to the user, so every refusal shows them the whole answer again — and two hooks can deadlock with no way out
- [FEATURE] Cowork scheduled tasks: per-routine connector scoping to cut cold-start cost
- Claude Cowork: scheduled task gets HTTP 500 from a custom MCP (OAuth) connector, while Claude Desktop + Claude Code succeed on the same server
- [BUG] Claude Max 5x: 1M context window auto-triggered in Cowork session, deducting usage credits without user request
- [BUG] Cowork Linux sandbox fails to start — persistent for 24+ hours
- [GitHub integration] Repo shows as connected in settings, but Cowork / cloud sessions can't access it
- Cowork cloud sessions sync a plugin's hooks/hooks.json but never register it — enabledPlugins is null in launcher-settings.json, so plugin hooks silently never fire
- [BUG] Child sessions: claude-code-remote MCP "Allow once" approvals are orphaned — calls fail before the prompt renders, grants never bind (11 calls, every prompt approved, 0 executions)
- Cowork plugin refresh: no UI to pull upstream changes without remove+reinstall
- Cowork creates a broken @<plugin>-local connector for a plugin-bundled HTTP MCP server, despite the endpoint supporting DCR
- [FEATURE] Port message_compose_v1 (inline email composer) to Cowork
- "Add to project" shows "No matches" even though the project exists
- [FEATURE] claude.ai: let users disable Chat mode / make Cowork the only way to start a conversation
- Cowork cloud egress: WebSocket (wss) hosts refused while ordinary HTTPS to the same service is allowed
- [FEATURE] claude.ai Cowork on the web: let me turn off the unread dot on Recents rows, or mark all read
- [BUG] WebFetch fabricates a live job posting for a URL that is actually a 500 error page (Cowork Scheduled Tasks)
- Repo picker overlay reopens on every submit attempt, blocks sending message in Cowork new-task composer
- [BUG] Cowork/claude.ai: uninstalling "Installed by default" marketplace plugins silently reverts within ~60s — no opt-out, "Enable plugin" toggle also reverts
- [BUG] Cowork scheduled tasks fail when Slack is the first (or only) connector called
- [BUG][REGRESSION] Broken Projects upgrade wiped out classic projects with no no opt-out
- [BUG] GitHub connector create_pull_request shows a form to the user instead of creating the PR, even when the owner told Claude to act
- [Cowork / model behavior] Claude reported a message as "sent" without verifying, then shipped a truncated message
- Cowork tasks created from claude.ai web (Windows, no desktop app) are all missing claude-in-chrome and remote-devices tools
- claude.ai Cowork: create_pull_request renders an editable PR card that later shows a false "failed to create pull request" error
- Feature request: distinct visual theme for the Code tab vs claude.ai
- [BUG] Cowork (claude.ai web, cloud sessions): a message one of my own sessions posts into another of my sessions is silently held ("peer_message_hold", "no-mode-asserted") with no way for the account owner to pre-authorise it
- [Cowork web] Safeguards repeatedly halt routine tool calls mid-reply in one session (upload, issue filing, session rename)
- i see sometime there is a communication drop between the coordinator and thread…
- [GitHub integration]
- [FEATURE] Projects (beta): persistently load the attached repo (CLAUDE.md, skills, hooks) into the coordinator session
- Cowork and GitHub [GitHub integration]
- [GitHub integration]
- Sidebar threads in Projects keep getting stuck, spawning background processes a…
- We keep hitting permissions issues pushing work to hosted git repos or deployin…
- [GitHub integration] Cowork session can't access repo even though "Check repository status" shows green
- [claude.ai web / Cowork] Home greeting comments on the user's working hours ("Up late, Aviv?") with no way to turn it off
- [Cowork] Agent is steered to hand the user a propose_skills "Save" card even when the user has forbidden it and a working save route exists
- Unable to authorize GitHub repo access for Claude (Cowork) session — push blocked by git proxy
- [GitHub integration]
- [Cowork web] "Temporarily unable to authenticate. Please retry. (×3)" banner while status page shows all systems operational
- Cowork (cloud): routine sandbox Bash commands keep stopping for "Allow once" approval mid-task, despite user granting blanket permission
- [BUG] Plugin account-upload is last-write-wins with no compare-and-swap, so concurrent sessions silently destroy each other's hook fixes
- [FEATURE] Account-synced plugins have no update API: skills have upload-skill, plugins have nothing, so a hook fix cannot be shipped without a human clicking Accept
- [BUG] Cowork (web): near-identical assistant paragraphs re-rendered three times in one message block during/around auto-compaction
- Cowork cloud session: agent proxy returns 503 on WebSocket (wss) CONNECT while HTTPS to the same vendor works
- Connector tool results return unusable payloads: Browserbase navigate dumps the internal page object, Claude Code Remote list_triggers returns 180 KB on one line
- Cowork: a custom MCP connector fails to connect with 502 CLIENT_HTTP_NOT_IMPLEMENTED from the MCP proxy, and only that connector, for a whole session
- claude.ai Gmail MCP create_draft: the google.com/url wrapper is emitted CORRUPTED (raw 0x17 in place of "=1"), and the substituted signature carries no gmail_signature marker
- Cowork (claude.ai web): a single uploaded image is delivered to the model twice, causing it to assert the user sent two
- [MODEL] Stated unverified claims as fact (payment status, filing deadline rule)
- [BUG] Custom remote MCP connector - all tools show "Auto-Allow disabled by your admin" in routine, despite org-wide Always Allow