Repository navigation
Move a cloud workspace channel back, or fork it #545
Description
A channel moved to a cloud workspace can't move back to its host or to a hosted channel. Its confirmation says "can't move back yet". It also can't be forked, because its lanes live in the container (architecture.md, Forks).
That makes Move to cloud workspace a one-way door. Trying it on a real channel means giving up the local placement for good.
Activity
iamnbutler commentedon Oct 22, 2026
From the 2026-10-22 map study (cloud rig, Canary 0.0.51.85):
ace-canary move <channel> --localon a cloud workspace channel prints "A cloud compute channel's workspace is its container, so it cannot move", but the CLI help saysmovebrings "an idle hosted channel back", and the app's details label these same channels "Hosted: ace-butler-home-compute…". The cloud channel's menu also drops Move and Fork with no explanation. Testers read it as a hosted channel and expected--localto work (^862, ^425).