Repository navigation
Add project lobbies for presence and channel lifecycle #17
Description
Project lobbies give presence, notifications and live channel lifecycle across a project's hosts.
Done
- feat(host): share project IDs between hosts and the app #334–feat(host): push channel lifecycle through project lobbies #337: the per-project
LobbyDurable Object inservices/directory, presence (Here and Away facepiles), and lifecycle events pushed through the lobby. The directory poll slows from 30 s to 5 min while lobbies are live. - fix(ui): keep a channel row's facepile clear of its pin #408, fix(ui): dim away people in facepiles and name everyone on hover #409, Report away even while listings keep changing #411, fix(host): report away 3 s after a blur even while listings keep publishing #412: the facepile/pin overlap, the dimmed away style with name tooltips, and away reported 3 s after a blur (fixed Show away people distinctly in facepiles #406, Keep channel row facepiles clear of the pin control #407).
- Notifications: run-finished and run-failed notifications shipped in feat: notify participants when their agent run finishes or fails #255 (Notify participants when an agent finishes #12).
- Production:
ace-directoryruns the lobby code (migrationv2, deployed October 15). The newace-dogfooding-directorywas deployed with it. - fix(app): say when an open channel is archived and who can unarchive it #438: an archived channel's open tab says it is archived and who can unarchive it.
- Verified: two-Mac study scenarios 25 and 25b.
The brief auto-name flash on a new channel (studies 25, 26) was dropped as not worth fixing.
Tracked by #5. Migrated from TODO.md — During dogfooding.
Activity
feat(host): share project IDs between hosts and the app
feat(host): share project IDs between hosts and the app
feat(directory): add a per-project Lobby cell beside the directory
feat(host): show who is here from project lobbies
feat(host): push channel lifecycle through project lobbies
feat(host): share project IDs between hosts and the app
feat(host): share project IDs between hosts and the app (#334)
feat(directory): add a per-project Lobby cell beside the directory
feat(directory): add a per-project Lobby cell beside the directory (#335
feat(host): show who is here from project lobbies
feat(host): show who is here from project lobbies (#336)
feat(host): push channel lifecycle through project lobbies
feat(host): push channel lifecycle through project lobbies (#337)
iamnbutler commentedon Oct 15, 2026
Project lobbies landed in #334, #335, #336 and #337 (merged on main at 3a5d0d1).
projectIdand related helpers moved to@ace/host/protocol.docs/terms.mddefines Person, Here, Away and Lifecycle event.LobbyDurable Object, one per project, runs in the directory's Worker at/lobbies/<project>. Presence lives only in socket attachments. Lifecycle events have a per-projectseqand are kept for 30 days, up to 2,000 per project. An alarm every 5 minutes closes sockets that have been silent for 90 s. Re-arming that alarm is the only steady write: 288 row writes a day per project while a host is connected. Pings and presence write nothing. Each lifecycle event costs about 5 rows over its life.ace serve --loopbackhosts stay out of lobbies.Nothing changes until the directory Worker is deployed, and that's your call. Until then, hosts get 404 from
/lobbies, retry quietly, and keep today's 30 s directory poll. To deploy, runwrangler deployonce fromservices/directory. That adds theLOBBYbinding and thev2migration (new_sqlite_classes: ["Lobby"]) and needs no new secrets. First confirm the live Worker's last applied migration tag is stillv1.Notifications (mentions, read state) are still not built, so this issue stays open.
iamnbutler commentedon Oct 15, 2026
Verified in the two-Mac study, scenario 25 (Canary 0.0.42, ace-directory-study running main with the Lobby DO).
talkrow.Follow-ups:
lucid-cedar) and then under the chosen name.iamnbutler commentedon Oct 15, 2026
Rewrote the body to the current state. Presence, lifecycle push and notifications (#255) are done and verified in studies 25 and 25b. What's left is the production directory deploy (the
v2Lobby migration, the user's call) and two minor UI items from the study.iamnbutler commentedon Oct 15, 2026
The production directory is already deployed.
ace-directoryis the Worker that both stable and Canary hosts use. Its migration tag isv2, and it was last deployed at 10:33 UTC today, after #335 (06:21 EDT); nothing has changed inservices/directorysince. The "study directory" was this same Worker, so no deploy is needed. Only the two small UI items are left.iamnbutler commentedon Oct 15, 2026
Done: lobbies, presence, lifecycle and notifications shipped and verified; the archived-tab notice landed in #438. The new-channel auto-name flash was dropped.