Skip to content

Face room still Bot-first: two tiles per person, Members counts Bots, '(you)' on Bots, mention re-binds after leave, bloated bubble headers #457

Closed

Description

@Birfy

Found by the product self-test on 2026-10-20 ~01:00 Asia/Shanghai (focus: Face-to-face room). Setup: ThinkFlowLab/FlyBot main 84a95a6, dsh 0.2.0-rc.2, two fresh homes A SelfA0056 (:3090, Bots Chief + Researcher) and B SelfB0056 (:3091, Bot Chief), not friends (two strangers meeting in person), Bot Social server https://47-80-69-220.sslip.io, Bots on ark/deepseek-v4-flash. Room 482915.

Problem

The room is still Bot-first where the design says person-first:

  1. Waiting tiles: A sees two tiles both labelled "SelfA0056" (one for Chief, one for Researcher) instead of one person tile for SelfA0056 with "Chief, Researcher" as secondary.
  2. Members panel: header "Members · 3" over Chief (SelfA0056), Researcher (SelfA0056), Chief (you), while the subtitle says "2 people · 3 Bots". The Auto-send toggle only offers "Auto-send Chief → room" (no Researcher).
  3. "(you)" on Bots: the @ picker lists "Chief (you)", "Researcher (you)", "Chief (SelfB0056)", "Everyone — Every Bot in this room" (no count). Members uses the same "Chief (you)".
  4. Mention re-renders after leave: A's bubble "@chief (SelfB0056) what noodle dish…" became "@chief (you) (SelfB0056)…" with A's whale icon after B left, so it now looks like A mentioned its own Chief.
  5. Own bubbles: no avatar/name, and their colour flips black → grey after the next message → black again.
  6. Bubble headers bloated: "Researcher · SelfA0056 (selfa0056) @researcher.selfa0056.home", "Chief · SelfB0056 (selfb0056) @chief.selfb0056.home"; join lines "Chief (SelfA0056) joined; available to this room only"; other places plain "Chief".

Expected

  • One tile and one Members entry per person: "SelfA0056 · Chief, Researcher", "SelfB0056 (you) · Chief". Count = people. "(you)" only on the person, never on a Bot.
  • Auto-send lists each of my Bots in the room (or one toggle for all my Bots, clearly worded).
  • @ picker: each Bot once as "Chief (SelfB0056)" / "My Researcher"-style, Everyone with a correct count.
  • A sent mention stays bound to the Bot that was mentioned (store the handle, render from it), even after that person leaves.
  • One name format everywhere in the room: "Bot (Person)" for Bots, person name + avatar for humans; no handles or lowercase ids in bubble headers (handle on hover/details at most). Own bubbles stable colour, with my avatar like the others.

Scope

Face room UI (waiting dialog, Members, @ picker, bubble header, mention rendering). Avatars mismatch is tracked on #182.

Activity

  1. added
    bugSomething isn't working
    area:socialFriends, invites, grants, Bot Social
    area:uiWeb/desktop UI and copy
    self-testFiled by the product self-test routine (issues only)
    on Oct 19, 2026
  2. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Maintenance triage (2026-10-20 01:58 Asia/Shanghai, main 84a95a6): bug against the person-first room design. Proposed: one waiting tile and one Members entry per person ("SelfA0056 · Chief, Researcher", "SelfB0056 (you) · Chief"), count = people, "(you)" only on the person; @ picker lists each Bot once as "Chief (SelfB0056)" plus "Everyone (N Bots)"; mentions stored by handle and rendered from it so they survive a leave; one name format "Bot (Person)" in bubble headers, no handles/lowercase ids (hover/details only); own bubbles keep a stable colour and show my avatar. Open question for the owner: Auto-send as one toggle per Bot of mine in the room (recommended, matches per-Bot grants) or a single "Auto-send my Bots' replies" toggle. Marking needs-human.

  3. added
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    and removed
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    on Oct 19, 2026
  4. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Owner decision (2026-10-20): Confirmed: the room is person-first (one tile per person, '(you)' only on people). Auto-send is one switch per Bot (option a).

  5. added
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 19, 2026
  6. self-assigned this
    on Oct 19, 2026
  7. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Claimed by maintenance (2026-10-20 07:58 Asia/Shanghai). Working on branch fix/457-face-room-person-first in Birfy/FlyBot, developed in parallel with the other face-room issues (#462, #458, #457, #455, #304, #182); they will merge one after another.

  8. Birfy commented on Oct 20, 2026

    @Birfy
    CollaboratorAuthor

    Minor details decided while implementing (PR #468). Recorded 2026-10-20 08:26 Asia/Shanghai:

    • Every Bot in a face room is named Bot (person), my own Bots too (Chief (SelfB0056)). (you) appears only on a person (SelfB0056 (you), Me (you) on the waiting tiles).
    • A person tile uses that person's first Bot's avatar as its mark, with the person's name on the first line and their Bots on the second. Members rows in group settings and the details drawer use a person mark instead.
    • Members · N counts people. The room subtitle stays N people · M Bots. In the @ menu, Everyone shows the Bot count (3 Bots).
    • A sent mention stays bound to the Bot it named because mention matching also looks at seats that have left (they keep leftSeq). No new stored field.
    • My own typed face-room line is never drawn as held. It carries my person mark and name.
    • Face-room bubble headers show the name only, with the handle on hover. No globe, handle line or lowercase id.
    • Per-Bot Auto-send:
      • It is stored host-side per Bot (settings.faceAutoSend) and off by default. No Bot Social server change.
      • With a Bot's switch on, the host approves that Bot's held line only when Bot Social's hold has no DLP reason or risk flag. Flagged lines still wait for the owner's click.
      • The old account-wide auto_approve_face_rooms reads as "every switch on". The first per-Bot change keeps the other Bots on locally and turns the account-wide flag off.
      • Auto-send from now on on a face-room card turns on only the writing Bot's switch.
  9. removed
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a templatearea:socialFriends, invites, grants, Bot Socialarea:uiWeb/desktop UI and copybugSomething isn't workingself-testFiled by the product self-test routine (issues only)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions