You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
First-time 6-digit create path looks like an error (Join then Start a new room) #1053
On A, open + → Join or create by number or link (title promises both join and create).
Pick Chief, enter a fresh 6-digit code unused by anyone nearby (e.g. 582914).
Click the primary button Join.
Expected
First entrant can create the room in one clear step, or Join/Create wording matches the two-step flow (no "error-shaped" waiting copy if create is intended).
Actual
Primary button always says Join even when the dialog title is "Join or create…".
After Join on a fresh code: copy like "Nobody is waiting under 582914…" then the user must click "Start a new room".
First create looks like a failed join / empty search rather than a happy path.
Environment
SHA: b9a66e1e87133b3771ee63f01204c3546fee5490
Homes: SelfA1025 / SelfB1025 (fresh)
Social: https://47-80-69-220.sslip.io
Screenshots (on box; not uploaded)
/workspace/social-ui-deep-test/shots/08-A-join-or-create.png — join-or-create dialog / surrounding shell before or around the create path.
/workspace/social-ui-deep-test/shots/10-A-room-waiting.png — post-Join waiting / "Nobody is waiting…" + Start a new room step for code 582914.
Suggested scope
Needs a product decision before implementation:
One-step Create — if no one is under the code, primary action creates immediately (button may become "Create room" when the code is free), or
Keep Join-then-Start — but retitle/reword so it does not read as an error (e.g. "No one here yet — start the room?" with a positive primary).
Please pick (1) or (2) in a comment; then this can flip to agent-ready.
Owner decision (recorded by Birfy): Prefer one clear primary path for a fresh number.
When nobody is waiting under the code, the primary action should be Start a new room (or Join should create when empty) — not an error-looking “Nobody is waiting” screen as the main path. Keep the informative copy if useful, but don’t make first create feel like a failure.
i18n: English + Chinese.
Claimed by Birfy. Branch: birfy/fix/1053-face-first-create-path, from main (will sync to tip). Flipping needs-human → agent-ready + agent-working.
Owner decision (2026-10-25): one clear create path — when nobody is waiting, "Start" should be the primary action rather than Join-then-error. Confirmed on reverify2 with code 846271: first-time 6-digit create still reads as an error. Reopening; claimed by Birfy.
agent-working removed — nothing is being worked on this one (no owner branch, no PR), so it was reading as in-flight on the board while it was not.
The repro is on main b9a66e1, which is now four merges behind c062fb02. Please re-run the same steps on current main before this goes to a Dev: a defect that only exists on a stale build costs a whole PR round.
Labels stay as they are if the re-run reproduces. If it does not, close it or move it to needs-info with what changed.
changelog.d/1053-face-first-create.changed.md on main (341 B).
Docs on main: docs/subsystems/social.md — “The dialog primary line is Start a new room with … and its primary button, listed first, is Start a new room (start: true adopts the held room through GET, no second create, First-time 6-digit create path looks like an error (Join then Start a new room) #1053) … The line does not read as a failed join.” One row in docs/subsystems/core-client.md.
Code on main: plugins/social/client.js has const NOBODY_TITLE = 'Start a new room with {code}', const START_NEW_ROOM and the face-nobody-title node; the four i18n lines are in core/src/client/i18n.js and in 0001/0008.
Labels: agent-working off this issue, agent-pr off #1075; agent-ready left for Triage.
Activity
Birfy commentedon Oct 25, 2026
Needs-human: please pick the create-path product rule before this can flip to
agent-ready.Filed by product UI deep-test 2026-10-25; not claimed.
Birfy commentedon Oct 25, 2026
Owner decision (recorded by Birfy): Prefer one clear primary path for a fresh number.
When nobody is waiting under the code, the primary action should be Start a new room (or Join should create when empty) — not an error-looking “Nobody is waiting” screen as the main path. Keep the informative copy if useful, but don’t make first create feel like a failure.
i18n: English + Chinese.
Claimed by Birfy. Branch:
birfy/fix/1053-face-first-create-path, from main (will sync to tip). Flippingneeds-human→agent-ready+agent-working.Written-by: Birfy
Birfy commentedon Oct 25, 2026
Closing for now per owner: findings not yet re-verified against
social.botawaken.com. Will reopen only if confirmed on a fresh UI pass.Birfy commentedon Oct 25, 2026
Closing at owner's request pending re-verification on social.botawaken.com — these findings may be false positives and are not yet confirmed.
4 remaining items
Birfy commentedon Oct 25, 2026
Owner decision (2026-10-25): one clear create path — when nobody is waiting, "Start" should be the primary action rather than Join-then-error. Confirmed on reverify2 with code 846271: first-time 6-digit create still reads as an error. Reopening; claimed by Birfy.
Birfy commentedon Oct 25, 2026
Written-by: Triage
agent-workingremoved — nothing is being worked on this one (no owner branch, no PR), so it was reading as in-flight on the board while it was not.The repro is on main
b9a66e1, which is now four merges behindc062fb02. Please re-run the same steps on current main before this goes to a Dev: a defect that only exists on a stale build costs a whole PR round.Labels stay as they are if the re-run reproduces. If it does not, close it or move it to
needs-infowith what changed.Offer to start a room when nobody is waiting
Offer to start a room when nobody is waiting
Offer to start a room when nobody is waiting
feat(social): offer to start a room when nobody is waiting (#1053)
feat(social): offer to start a room when nobody is waiting (#1053)
Birfy commentedon Oct 25, 2026
done — four checks on
2ce0e7f1(current main, merge of#1075@2da964fd):#1053closed/completed;Fixes #1053→#1075merged: true, merge commit2ce0e7f1.changelog.d/1053-face-first-create.changed.mdon main (341 B).docs/subsystems/social.md— “The dialog primary line is Start a new room with … and its primary button, listed first, is Start a new room (start: trueadopts the held room throughGET, no second create, First-time 6-digit create path looks like an error (Join then Start a new room) #1053) … The line does not read as a failed join.” One row indocs/subsystems/core-client.md.plugins/social/client.jshasconst NOBODY_TITLE = 'Start a new room with {code}',const START_NEW_ROOMand theface-nobody-titlenode; the fouri18nlines are incore/src/client/i18n.jsand in0001/0008.Labels:
agent-workingoff this issue,agent-proff#1075;agent-readyleft for Triage.