Linux desktop app: cloud (session_) chats never spawn a process → "send but no reply"; cowork VM "not supported (linux/x64)"

Bug: Linux desktop app — cloud (session_) chats never spawn a process → "send but no reply"

Environment

• Claude desktop app: 1.22209.3 (Linux)
• Bundled Claude Code: 2.1.215
• OS: Ubuntu 24.04.4 LTS, x86_64
• Hardware: Intel Core Ultra 7 256V (Lunar Lake), 16 GB RAM

Summary

In the Linux desktop app, opening a cloud/synced chat (a session_… id) and sending a
message produces no reply. The message is accepted but the app never launches a Claude
Code process for cloud sessions. Local sessions (local_…, backed by a
~/.claude/projects/<uuid>.jsonl transcript) work correctly and reply normally.

The same conversations resume and reply fine from the terminal CLI
(claude -r <id>), so the transcripts, account, and model are all healthy — the failure is
specific to how the Linux desktop app runs cloud sessions.

Evidence (from ~/.config/Claude/logs/)

cowork_vm_node.log:

[Bundle:status] rootfs.img missing
[startVM] VM not supported (linux/x64), skipping
[cleanupVMBundleIfUnsupported] yukonSilver not supported (status=unsupported)

main.log:

• Cloud session_… ids get setFocusedSession but never produce a

Mapping internal session local_… to CLI session <uuid> line or a process spawn.

• Only local_… sessions map to a CLI transcript and run.
• LocalAgentModeSessions.getDefaultWorkspaceFolders: 0 folders
• Minor: Failed to spawn git: spawn git ENOENT and

[Coder] coder CLI not found on augmented PATH — the app's child-process PATH is missing
common tools even though they're installed and on the user's login PATH.

Steps to reproduce

1. Ubuntu 24.04 (x86_64), Claude desktop app 1.22209.3.
2. Open a cloud/synced chat from history (a session_… id).
3. Type any message and send.
4. Expected: a reply. Actual: no reply; logs show no Claude Code process is spawned

for the cloud session.

Impact

Cloud/synced chats are effectively unusable in the Linux desktop app; only locally-created
chats work. This is especially painful right after migrating a machine, where most history is
cloud-synced.

Workaround

Resume from the terminal CLI: cd <project> && claude, then /resume. All local transcripts
(including very large ones) resume and reply correctly.

Requests

1. Support the cowork/remote-session runtime on linux/x64, or fall back to **local

execution** for cloud sessions when the VM is unsupported (rather than silently doing
nothing).

1. Surface a visible error to the user when a session can't be run, instead of accepting the

message with no reply.

1. Fix the desktop app's child-process PATH so git / coder are found.