[BUG] Cowork + Chat tabs disappear after auto-update 1.18286.2 → 1.19367.0 (VM healthy, zero process spawns, sessions-bridge poll aborts) — macOS

Status Fixed / completed
Reported on v2.1.202
Maintainer reply None cached
Activity 4 comments · opened Jul 22, 2026 · closed Jul 25, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Summary

After the desktop app auto-updated from 1.18286.2 → 1.19367.0 (applied on relaunch
Jul 7, 2026 3:55 PM local), the Chat and Cowork tabs vanished from the app —
only Code remains — and no Cowork work runs. The Cowork backend on my machine is fully
healthy; the client simply never dispatches work to it. This matches the "Cowork tab missing
after auto-update" regression class (see related issues below).

Environment

  • Claude Desktop 1.19367.0 (regressed from 1.18286.2)
  • macOS Tahoe 26.5.2, MacBook Pro (Apple Silicon)
  • Claude Pro subscription
  • Full uninstall + clean reinstall performed — did not resolve it

Timeline (from ~/Library/Logs/Claude/)

  • Jul 7, 12:02 PM — last successful Cowork activity. cowork_vm_swift.log shows its final

Process spawned entry (session magical-exciting-franklin). 686 spawns before this point,
zero after.

  • Jul 7, 3:55 PM — update applied at relaunch. main.log:

[updater] Version changed since last launch: 1.18286.2 → 1.19367.0

  • Jul 7 evening → Jul 8 — every launch shows the same broken pattern below.

Key evidence — VM is healthy, but no work ever starts

Across ≥4 VM boots after the update (Jul 7 7:55 PM; Jul 8 6:44 AM, 7:25 AM, 11:25 AM) the VM
boots cleanly and recovers sessions, yet zero processes ever spawn, while main.log's
sessions bridge repeatedly aborts its poll loop.

<details>
<summary>VM boots clean (cowork_vm_swift.log / coworkd.log)</summary>

What Should Happen?

After a desktop-app auto-update, the Chat, Cowork, and Code tabs should all remain
present and functional. On a Pro plan with a healthy Cowork VM, starting a Cowork
session should spawn worker processes and run work as it did on 1.18286.2.

Error Messages/Logs

Source: ~/Library/Logs/Claude/

Update applied (main.log):
[updater] Version changed since last launch: 1.18286.2 → 1.19367.0

VM boots clean but never does work (cowork_vm_swift.log / coworkd.log):
[VM] 2026-07-08 07:25:13 [info] Installed 2 host CA certificates in guest
[VM] 2026-07-08 07:25:13 [info] API reachability: REACHABLE
[VM] 2026-07-08 07:25:13 [info] SDK installed successfully: version=2.1.202
[KERNEL] 2026/07/08 10:44:10 [coworkd] user recovery complete: recovered=91 skipped=1 failed=0

cowork_vm_swift.log: last "Process spawned" entry was Jul 7 12:02 PM (session
magical-exciting-franklin); 686 spawns before that point, ZERO after the update.

Meanwhile sessions-bridge poll loop repeatedly aborts (main.log):
2026-07-08 11:13:34 [error] [sessions-bridge] Poll error, backing off: This operation was aborted
2026-07-08 11:31:02 [error] [sessions-bridge] Poll error, backing off: This operation was aborted
2026-07-08 11:48:14 [error] [sessions-bridge] Poll error, backing off: This operation was aborted
2026-07-08 15:10:01 [error] [sessions-bridge] Poll error, backing off: This operation was aborted

Full logs available on request: main.log, coworkd.log, cowork_vm_swift.log, cowork_vm_node.log

Steps to Reproduce

  1. Run Claude Desktop 1.18286.2 on macOS with Cowork working normally (tabs present,

sessions spawning processes).

  1. Allow the app to auto-update to 1.19367.0 and relaunch.
  2. Observe the app window: only the Code tab is present — Chat and Cowork tabs are gone.
  3. Start (or attempt to resume) a Cowork session.

Result: The Cowork VM boots cleanly and recovers sessions, but zero processes spawn and
no work runs. A full uninstall + clean reinstall does NOT restore the missing tabs.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.18286.2

Claude Code Version

You're running Claude Code v2.1.160. But, this problem started manifesting in Claude Desktop 1.19367.0 (regressed from 1.18286.2) and is still present.

Platform

Claude Desktop

Operating System

macOS

Terminal/Shell

Other

Additional Information

Signature: healthy VM + zero spawned processes + sessions-bridge poll aborts → points to
the client entitlement / feature-flag / UI-preload layer, not the VM, network, or account.
Given the exact version pair and timestamps, this should be reproducible as a diff between
1.18286.2 and 1.19367.0.

Related issues (same "Cowork tab missing after auto-update" class):

  • #48407 (open) — Cowork tab missing, Windows 11
  • #75321 (open) — Cowork tab missing, Windows 11 Home 25H2 (status=unsupported)
  • #48310, #49748, #51871 (closed) — same class

Account: Claude Pro. Full uninstall + clean reinstall performed; did not resolve.

View original on GitHub ↗

4 Comments

cjmcgin · 2 months ago

Update — regression persists across 10 subsequent auto-updates.

Since filing this on 1.19367.0, the app has auto-updated ten more times and the Chat/Cowork
tabs remain missing on every one. Version progression from main.log ([updater] Version
changed since last launch
):

1.19367.0 (Jul 7, regression starts)
→ 1.20186.0 (Jul 9) → 1.20186.1 (Jul 11) → 1.20186.9 (Jul 14)
→ 1.21459.0 (Jul 15) → 1.21459.1 (Jul 16) → 1.21459.3 (Jul 16)
→ 1.22209.0 (Jul 17) → 1.22209.3 (Jul 19)
→ 1.24012.0 (Jul 21) → 1.24012.1 (Jul 22, current)

I am now on 1.24012.1 and the Code tab is still the only tab present. Scoped to the
Cowork VM specifically, [VM] ... Process spawned entries in cowork_vm_swift.log number
686 before the Jul 7 update and 0 after — across this entire 15-day, 10-version range.
The VM continues to boot clean while the client never dispatches work to it. None of these
10 updates addressed the issue.

cjmcgin · 2 months ago

Correction / clarification on which tabs are affected.

My original report said "Chat and Cowork tabs vanished — only Code remains." That
under-described what I'm actually seeing. To be precise, in the top-left of Claude Desktop
I currently have two tabs:

  • Home — present and working; clicking it lets me interact with Claude Chat.
  • Code — present and working; clicking it lets me interact with Claude Code.

The Cowork tab is the one that is missing. So Chat is still reachable (via Home) — the
regression specifically dropped the Cowork tab, while the Cowork backend VM continues to
boot cleanly (see the "686 before / 0 after" [VM] Process spawned evidence above). Everything
else in this report stands; only the tab inventory is corrected here.

Still on 1.24012.1 as of Jul 25, 2026; Cowork tab still absent.

cjmcgin · 2 months ago

Resolved as a discoverability failure — but I want to be precise about what "resolved" means here.

The Cowork functionality was never broken on my machine. Following a tip in #48407, I found
that the 1.19367.0 redesign removed the named "Cowork" tab and relocated its function into
an unlabeled mode toggle inside the Home input box
: "Chat" ↔ "Allow Claude to Act
Autonomously." The second mode is Cowork. Confirmed: with it selected, "List the files on my
Desktop" produced a permission prompt reading "Claude would like to Cowork in:
/Users/cjmcgin/Desktop"
and then correctly listed my files.

Log evidence, now complete. [VM] ... Process spawned in cowork_vm_swift.log:

  • 686 entries through the last tab-based session (Jul 7, 12:02 PM)
  • zero for the next 18 days — no discoverable entry point, so no dispatch
  • one at Jul 25, 11:01:51, the instant I used the toggle (session brave-magical-cray)

So the backend was healthy the entire time. This was a user-experience regression, not a
code regression — and I'd ask the team not to file it under "working as designed."

Why this is a defect the UX owners should act on, not close out:

  1. A navigation element was deleted with no in-product signposting. Users who had learned a

three-surface model — Chat, Cowork, Code — opened the app to find Cowork simply gone. No
migration notice, no tooltip, no release-note callout. The published docs still describe a
three-tab layout, so the product contradicts its own documentation.

  1. The replacement control abandons the term users were trained on. "Allow Claude to Act

Autonomously" does not read as "this is where Cowork went." Renaming a feature while removing
every trace of its prior name breaks the conceptual bridge between Chat, Cowork, and Code
that users relied on to navigate. If "Cowork" no longer adequately distinguishes the mode
from Claude Code, that is an argument for clarifying the label — not for erasing it.

  1. The cost landed on users, and it was not trivial. Believing Cowork was broken, I performed

a full uninstall/reinstall, pulled and analyzed four log files, tracked the regression across
11 app versions, and filed a detailed bug report — substantial time spent diagnosing
something that was functioning as intended but rendered invisible. #48407 shows dozens of
others doing the same. That volume is the signal: the change, not the users, is the defect.

Requested actions:

  • Restore the word "Cowork" to the toggle (e.g. "Chat / Cowork"), or otherwise make the mode

self-identify as Cowork in-product.

  • Add a one-time in-app notice for users migrating across the tab→toggle change.
  • Reconcile the documentation, which still describes the removed three-tab layout.

Marking my specific issue resolved, since Cowork works. The underlying UX regression above is
what I'd ask the team to own.

Environment: macOS Tahoe 26.5.2, Apple Silicon, Claude Pro, 1.24012.1.

github-actions[bot] · 25 days ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.