[teamleaderleo]

What

When a machine's older cmux-tui refuses the folder copy (machine_outdated), a Cloud chat start updates the machine and copies again. The update restarts the machine's daemon, so its link comes back on a new socket. The second copy still used the socket it read before the update, so it failed.

Evidence

A DEV capture of build ff3f8c9 (cloud-proof integration, 2026-11-01) sent to a fresh machine, cloud-chats-2. The machine's daemon was upgraded at 15:26:27–33. Then the card failed with:

Couldn't copy the folder to cloud-chats-2: cannot connect to /var/folders/_2/…/T/cmux-link-1c5fe16010a3.sock: No such file or directory (os error 2)

CloudStartChat read machine.daemon.connection?.endpoint?.socketPath once, before CloudOutdatedMachine.copy. CloudMachineUpdates.updateNow → reconnectAfterUpdate → connect(dropTicket: true) creates a new link socket.

Fix

• CloudOutdatedMachine.copy (CmuxNextCloud) reads the socket for each copy.
• After an update, it waits up to 90 s (CloudWait.holds) for the connection's handshake key (CloudMachineUpdates.handshake) to change from its value before the update. Then it reads the socket again.
• If either read finds no connection, the start fails with "not connected" as before. That failure now comes inside the copy's catch, so it shows as a copy failure with Retry.
• CmuxNextApp shrinks by 1 line (arch-ratchet: app_lines -1).

Overlap

#30655 (open, same lane family) changes the same CloudOutdatedMachine.copy call in CloudStartChat.swift. Whichever lands second needs a small rebase there.

Tests

• CloudStartChatMachineTests.onlyTheMachinesOutdatedRefusalUpdatesItBeforeCopyingAgain now also checks that the second copy uses the new socket.
• New: theCopyAfterAnUpdateWaitsForTheMachinesNewLink. The link drops during the update and comes back after it returns; the copy waits for it. It also checks that nothing copies while the machine is not connected.
• Fleet compile check: cmux-ci compile-check --app at the head.

Agent session: agent session

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Fixes a chat start that copies a folder to a just-updated machine failing because it reused the machine's old link socket, which the daemon restart had removed.

The copy now reads the machine's socket for each attempt, and after an update waits up to 90 seconds for the connection's handshake key to change before copying again. A missing connection surfaces as a copy failure with Retry instead of silently succeeding.

^{Written for commit 87bfa16. Summary will update on new commits.}

[github-actions]

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review 87bfa16: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr31087 -f ref=cloud-recopy-fresh-socket -f platform=macos -f backend_mode=local

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4132418488301 (5f712a27cc)
• cmux NEXT nightly 1.0.0-nightly.4132492786501 (3c0c02a5ae)
• cmux NEXT nightly 1.0.0-nightly.4132569907101 (641e45405d)
• cmux NEXT nightly 1.0.0-nightly.4132675672201 (1d9d0c83e6)
• cmux NEXT nightly 1.0.0-nightly.4132727143001 (fe90490c5d)

[teamleaderleo]

Owned by an agent session · session

[teamleaderleo]

Review (subagent claude-opus-5-5 medium): SHIP at 87bfa16

No blocking findings. Three follow-ups are filed as one issue.