Repository navigation
[Meta] Onboarding: start a team, join it, and go remote #550
Description
Getting a team onto Ace: the first person who sets up the team's services, teammates who join them, how hosts discover services, and the optional remote channel paths.
Mapped on 2026-10-21 by tracing the code and taking screenshots of the real app; the gaps came from that walk-through. Sub-issues are ordered by priority. The first-run fork comes first, because it reshapes most of the others.
Related but tracked elsewhere: #511 (one shared ACE_SECRET opens every service; under #506) and #182 (browsers reaching hosted channels).
Also part of onboarding, with parents elsewhere: #215 (first-run teaching) and #177 (hosted channels from the new-channel picker).
Activity
iamnbutler commentedon Oct 22, 2026
Status 2026-10-21. Shipped: first-run team setup with an in-app Cloudflare deploy (#552, #553); a join link and asking to join over the tailnet (#561, #563); a phone QR in Settings (#562); service URLs kept across restarts (#556); team services and the 401 explained (#558, #559); a Tailscale restart prompt (#555). Closed #538, #541, #543, #546 and #549. Open: #539 (pick up Tailscale live), #540 (check gh sign-in), #542 (peers on other ports), #545 (move a cloud workspace back or fork it), plus #215, #177 and #511.