Face-to-face: avatars and room title differ per home (regressions of #137/#172); Leave is abrupt and not seen by the peer

Environment

ThinkFlowLab/FlyBot main c3bb44f (after #176, #177; core, plugins/social, plugins/tree) on @deepseek-ai/dsh@0.2.0-rc.2, Node 24. Two fresh installs on one Linux box: A :3080 (owner SelfA1933, @selfa1933.home, Bots Chief + Helper), B :3081 (SelfB1933, @selfb1933.home, Chief). Bot Social https://47-80-69-220.sslip.io. Scheduled product self-test, 2026-10-17 19:38–19:44 Asia/Shanghai. No model key on the box (model errors are not the bug).

Repro

A and B join face room 482913 with Chief each, Enter chat, chat a little, then B clicks Leave.

Actual

Avatars differ per side (A friend's Bot ignores the owner's chosen avatar: the same Bot looks different in each home (follow-up to #84) #137). Both Chiefs use the default blue whale. B shows A's Chief correctly. A shows B's Chief as an orange blob, although A's room record stores color #4d6bfe, avatar whale for that member.
Title differs per side (Face-to-face: the same room has different titles in each home (A omits the other member) #172, fixed by fix(social): Past rooms Open works on every home; one face-room title for all members (#171, #172) #175).
- A's sidebar row: Face-to-face · SelfA1933 · Oct 17 19:52 with a grey placeholder avatar. A's stored room name is Face-to-face · SelfA1933 · Oct 17 19:42.
- B's row lists both names: Face-to-face · SelfA1933, SelfB1933 · Oct 17 19:42.
- The time is also inconsistent: the row shows 19:52 (when joining expires) while the title shows 19:42 (start).
Room details: Open, the Auto-send checkbox and Leave are crowded onto one row. The checkbox says just Auto-send and does not say which pair it covers.
Leave on B:
- No confirmation.
- The main pane goes blank (Choose a workspace to start) while details still show the room with 2 members.
- About 6 s later B returns to Chief with ▾ Past rooms 1.
- A sees "SelfB1933's Chief left" only after a reload. A's local room stays status: open.
Once during the session B's whole tab went blank and needed a reload. It did not happen again and may be related to fix(client): UI blank after #176 — declare roster before the tab-title effect #177.

Expected

Every member sees each Bot's own avatar and the same room title and time on every home.
Room details have one clear row of actions. The Auto-send label names the pair (e.g. "Auto-send Chief → room").
Leave asks for confirmation (or offers undo) and goes straight to a sensible view without a blank pane. The other side sees the leave within the normal poll time, without a reload.

Merged on main (c56384a): #186 covers part of this issue.

Covered (#186)

Leave on a live room asks once (Leave / Stay), then opens the main Bot (no blank pane).
Peer leave sticks: a room left/closed is no longer flipped back to open by a later poll; the other side sees the leave within one poll.
Same room title and start time on every home (title built from every member the room has had, uses start time, not the joining deadline).
Auto-send checkbox names the Bot (Auto-send Chief → room).

Skipped (leaving this open)

Orange peer-avatar blob: not diagnosed, could not reproduce from code, needs a live repro.
Waiting state for other members: needs a Bot Social server signal.
Footer turn/step counter: native to DSH, not changed here.
Room-details row layout beyond the label.

Self-test on 38c00b4:

Fixed: Leave asks inline and the peer sees "left the room" without a reload.
Still present: tile/member avatars differ per side. A's Chief is an orange cat on A and a blue whale on B.
People-vs-Bot labelling and avatar-less received lines are in Face room: people vs Bots — received human lines have no avatar and look like my own; members list shows only Bots, named inconsistently (partial regression of #180) #229.

Status against main 7a3ccb3 (2026-10-18 ~10:30 Asia/Shanghai):

Done

Same room title and start time on every home, Leave asks once (Leave / Stay), no blank pane, the peer sees the leave without a reload, and the Auto-send label names the pair: fix(social): face room Leave confirm, peer leave sticks, one title everywhere (#182) #186 (c56384a), confirmed in the self-test on 38c00b4.
People vs Bots in rooms (person lines with avatar, person-first members and tiles): fix(ui): face rooms put people first: person lines with avatar, person-first members and tiles (#229) #238 (Face room: people vs Bots — received human lines have no avatar and look like my own; members list shows only Bots, named inconsistently (partial regression of #180) #229).
Room-details row layout: fix(ui): settings say each thing once; inline friend Bot remove; clearer Sharing (part of #230) #232 changed the CSS for the face-room Auto-send row. It is covered by tests but has not been checked in a browser yet.

Still open (why this issue stays open)

A Bot looks different on each home. In the 38c00b4 self-test, A's Chief was an orange cat on A and a blue whale on B. The owner's local look (colour and avatar) never reaches the other home, so B falls back to the published or handle-seeded look. This is the same root cause as the shared-Bot colour note in Social UI polish round 3: truncation, duplicate Add friend/Accept invite, Manage access depth, wording (#166 follow-up) #173 (2026-10-17 13:06) and A friend's Bot ignores the owner's chosen avatar: the same Bot looks different in each home (follow-up to #84) #137 / A friend's Bot renders a random per-record look: unstable on re-add, inconsistent with the no-record path, different in each home #84. Expected: every home draws a Bot with its owner's look, in tiles, members, the sidebar and bubbles.
Waiting state for other members: needs a Bot Social server signal, so it can't be done in FlyBot alone.

Out of scope here: the footer turn/step counter, which comes from DSH.

Self-test on a003044 (2026-10-18 16:27–16:33 Asia/Shanghai, fresh A :3090 / B :3091, focus: Face-to-face room):

Avatars are still inconsistent, now on the same home. In B's waiting dialog B's Chief is the blue whale, but in B's right details panel it is a purple blob. Cross-home look sync is still the open item here.
Title: both homes now show the same title, but it is Face-to-face · SelfA1622, SelfB1622 · Oct 18 16:27 (date) although both joined by 482913. Core upsertFaceRoom rebuilds the title without the join code. Past rooms use yet another time. Details and code pointers are in Face room titles/Past rooms: number dropped from title, Past rows show start or future deadline time, staying home marked 'Left' and never leaves on Bot Social, closed tab title (#250 regression) #304.
Leave: full-room Leave asks once and A saw "SelfB1622 left the room. This room is closed." OK. The staying home is then labelled Left and never leaves on Bot Social (Face room titles/Past rooms: number dropped from title, Past rows show start or future deadline time, staying home marked 'Left' and never leaves on Bot Social, closed tab title (#250 regression) #304). Waiting-room Leave has no confirm (Face-to-face join/waiting/leave polish: silent disabled Join, frozen countdown, waiting card twice, Leave next to Auto-send and unconfirmed in waiting, held lines shown twice #306).

Face rooms: the title keeps its number, honest Left/Closed, and the h…

Test: pin the update_bot_profile answer to Bot Social's shape (ThinkF…

Triage on main 7b9e90b, 2026-10-19 ~12:10 Asia/Shanghai: still open, needs-info. The cross-home look part was worked on in #377 (a Bot's new Bot Social identity gets its look again). Whether a Bot now looks the same on both homes (tiles, members, sidebar, bubbles) and inside one home (waiting dialog vs details) has not been re-checked since. Blocking question: does the avatar/colour mismatch still reproduce on current main? Next self-test of face-to-face rooms should check and note what is still different. The "waiting state for other members" part needs a Bot Social server signal (separate issue in Birfy/bot-social if still wanted).

Triage on main 0852b3f, 2026-10-19 16:59 Asia/Shanghai: still needs-info. No face-to-face self-test has run since #377, which re-sends a Bot's look to each new room-only identity.

Owner-delegated decision: "waiting state for other members" leaves this issue. It needs a Bot Social server signal. If it is still wanted, it goes in its own Birfy/bot-social issue. The footer counter is DSH's and also out of scope. What remains here is only the Bot look.

Repro for the next face-to-face self-test (fresh A/B): give A's Chief a non-default look (e.g. cat, green) before joining. A and B join one room with Chief each. On both homes, compare each Chief's avatar and colour in:

the waiting dialog,
the room tiles,
the details member list,
the sidebar row,
the reply bubbles.
Then leave, start a second room (new room-only identity) and compare again. Close this issue if every place matches the owner's look. Otherwise note which place differs, on which home.

Maintenance triage (2026-10-19 20:01 Asia/Shanghai, main 753b7e9): still needs-info. No new live self-test since the 16:59 check. Leaving open; next face/friend self-test should run the repro notes on the previous comment. Not pushing design questions while this waits on live confirmation.

Self-test 2026-10-20 ~01:00 Asia/Shanghai still sees this at main 84a95a6 (homes SelfA0056 / SelfB0056, room 482915):

In A's waiting dialog A's Chief is a purple acorn, but on A's sidebar and on B it is a blue whale.
In A's room chat B's Chief is a teal blob, but in A's Members panel it is a blue whale.
On B, A's Chief and B's own Chief are identical blue whales (can't tell them apart).
People get a generic grey silhouette everywhere (own bubbles have no avatar at all).
Expected: one avatar per Bot, taken from its owner's profile and identical in waiting tiles, chat, Members and sidebar on both homes; two different Bots never render identically; people show their own avatar/initial.

Maintenance triage (2026-10-20 01:58 Asia/Shanghai, main 84a95a6): reproduced live by the 01:00 self-test, moving from needs-info to needs-human. Proposed: one avatar per Bot, taken from its owner's Bot Social profile (the owner home's own choice) and used identically in waiting tiles, chat, Members and sidebar on both homes; a deterministic per-handle fallback so two different Bots never render identically; people get their profile avatar (or an initials avatar) everywhere, including own bubbles. If the server profile lacks an avatar field, a small Bot Social issue would be filed (needs the owner's yes before any prod deploy). Waiting on the owner's yes to apply agent-ready.

Owner decision (2026-10-20): Confirmed as proposed: avatars come consistently from the owner's Bot Social profile everywhere, with non-colliding fallbacks. If the server needs an avatar field, file a separate Bot Social issue; production deploy still needs the owner's explicit yes.

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

Minor decisions for PR #464 (2026-10-20 08:10 Asia/Shanghai), following the Owner decision:

Source of a Bot's look: the look its owner's home draws. When a Bot has no stored shape or color, that is the generated (id-picked) look, and it is sent to Bot Social as the profile avatar and color. Bot Social already has those fields, so no server issue is needed.
Collisions: a look the owner has (stored or generated) is shown the same on both homes, even if it matches one of mine. Example: two homes' Main Bots both keep the default whale. The owner name tells them apart (Face room: people vs Bots — received human lines have no avatar and look like my own; members list shows only Bots, named inconsistently (partial regression of #180) #229/Face room still Bot-first: two tiles per person, Members counts Bots, '(you)' on Bots, mention re-binds after leave, bloated bubble headers #457). Only fallbacks (a peer with no look at all, e.g. an older server) still avoid my own Bots' looks (Friend's Bot rows: two name formats ('Helper · SelfB0023's Bot' vs 'SelfA0023's Chief'), two-line wrap, no preview, inset highlight, faint marker, same avatar as own Chief #384).
People: the person's initial on a color picked from their name, with no server field, so the same person looks the same on both homes. Own-bubble avatars are left to Face room still Bot-first: two tiles per person, Members counts Bots, '(you)' on Bots, mention re-binds after leave, bloated bubble headers #457, which already lists them.
Title: cross-home title consistency already shipped in fix(social): face room Leave confirm, peer leave sticks, one title everywhere (#182) #186. The number in the title and the Past rows stay with Face room titles/Past rooms: number dropped from title, Past rows show start or future deadline time, staying home marked 'Left' and never leaves on Bot Social, closed tab title (#250 regression) #304, so the title is unchanged here.
Out of scope (as decided earlier): the waiting state for other members (needs a Bot Social signal) and the footer counter (DSH).

Past rooms: list everyone, show each row's time, open from the row, r…

Show one look per Bot on every home in face-to-face rooms (ThinkFlowL…

Navigation Menu

Repository navigation

Face-to-face: avatars and room title differ per home (regressions of #137/#172); Leave is abrupt and not seen by the peer #182

Environment

Repro

Actual

Expected

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Face-to-face: avatars and room title differ per home (regressions of #137/#172); Leave is abrupt and not seen by the peer #182

Description

Environment

Repro

Actual

Expected

Activity

Birfy commented on Oct 17, 2026

Birfy commented on Oct 17, 2026

Birfy commented on Oct 18, 2026

Birfy commented on Oct 18, 2026

Birfy commented on Oct 19, 2026

Birfy commented on Oct 19, 2026

Birfy commented on Oct 19, 2026

Birfy commented on Oct 19, 2026

Birfy commented on Oct 19, 2026

Birfy commented on Oct 19, 2026

Birfy commented on Oct 19, 2026

Birfy commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions