Skip to content

fix(host): wait for a moved channel's cloud workspace before opening its chat - #496

Merged
iamnbutler merged 3 commits into
mainfrom
move-starting
Oct 19, 2026
Merged

iamnbutler merged 3 commits into
mainfrom
move-starting

Conversation

@iamnbutler

Copy link
Copy Markdown
Contributor

Found in the move study (M3b): after Move to cloud workspace, the move finished (move.done after 19 s, workspace connected), but the chat showed "Cannot reach https://ace-github-next-compute…" and never reopened. The app opened the channel right after activation, while the service was still starting the workspace and refusing connections.

Run in cloud avoids this by reporting computing: "starting" for the start, and the app opens the chat only after that transition ends. The gateway now does the same for the whole compute move.

Built in Ace

No. Written in Claude Code while it led the move study, since the Mac's Ace Canary was the build under test. Dogfooding gap tracked in #5.

…rt before opening its chat

Why: apps/host/src/gateway.ts#function handle | a move to a cloud workspace ends by starting it, so the listing must report computing for the whole move or the app opens the chat while the service refuses it and never retries
@iamnbutler
iamnbutler merged commit e402e8f into main Oct 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant