Repository navigation
After friend accepts invite, inviter home shows no friend row / no joined feedback #1054
Description
Reproduce
Two fresh FlyBot homes on main b9a66e1 (SelfA1025 :3090 / SelfB1025 :3091 → https://47-80-69-220.sslip.io):
- On A: + → Add friend → Copy invite for Chief (SelfA1025).
- On B: paste invite → Accept.
- Observe B sidebar and A's sidebar / chat after accept.
Expected
Inviter (A) sees that the invite was accepted, and a clear path to share their Bot back / start mutual chat — or explicit UI copy that only the joiner can talk to the inviter's Bot (one-way by design). Silent zero feedback is not enough either way.
Actual
- B sees "Chief (SelfA1025) · Friend's Bot" and can message A's Chief.
- A's sidebar never shows a friend row for B / SelfB1025; A gets no "joined" / accept toast or row.
- A cannot open a chat to message B. Messaging looks one-way with no explanation on the inviter side.
- Design may intentionally be one-way grant (ST-F19: inviter direction has a grant; peer side stays 0 by design), but the UI gives zero feedback that accept happened and no way for the inviter to share back or understand the asymmetry.
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/04-A-invite-link.png— A Add-friend panel with invite link / "Invite link for Chief copied."/workspace/social-ui-deep-test/shots/05-B-after-accept.png— B after accept: selected Chief (SelfA1025) Friend's Bot, empty chat./workspace/social-ui-deep-test/shots/07-A-received-failed.png— A after B accepted and messaged: inbound line from SelfB1025 on Chief, but no friend row for B in the sidebar.
Suggested scope
Needs-human — clarify the product rule in UI:
- If mutual friendship is the goal: after accept, inviter gets a friend/person row + prompt to share their Bot / open chat both ways.
- If one-way grant is the rule (ST-F19): inviter still needs accept confirmation + explicit copy ("SelfB can message Chief; share your Bot so you can message theirs") and a one-click share-back.
Not a duplicate of #970 (re-share after revoke never reaches friend).
Source
product UI deep-test 2026-10-25
Activity
Birfy commentedon Oct 25, 2026
Needs-human: clarify mutual vs one-way grant in the inviter UI (related to ST-F19 one-way-by-design).
Not a duplicate of #970. Filed by product UI deep-test 2026-10-25; not claimed.
Birfy commentedon Oct 25, 2026
Owner decision (recorded by Birfy): Keep one-way grant by default (inviter shares Bot; joiner sees Friend’s Bot).
BUT the inviter MUST get visible feedback when someone accepts (toast and/or sidebar notice / friend activity), and a clear one-click path to share their Bot back / add mutual access. Do not leave the inviter with a silent empty sidebar.
Not mutual-by-default; not silent asymmetry.
Claimed by Birfy. Branch:
birfy/fix/1054-inviter-accept-feedback, 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.
3 remaining items
Birfy commentedon Oct 25, 2026
Owner decision (2026-10-25): keep the one-way grant, but the inviter must see accept feedback plus a path to share back. Confirmed on reverify2: after B accepted, A still shows "Nobody has this Bot" and no friend row. 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.This one is held at
needs-inforather thanagent-ready: the symptom is the inviter-side outcome of accepting an invite, and two merges after your base changed exactly that — #1024 (1d5b5a5f) made the re-accept grant name the peer bot instead of the home and removed thefriend_homefallback, and #1037 (699d03d9) fixed theYour …copy on the same line. If it still shows no friend row onc062fb02, say so here with the two sidebars and I will putagent-readyback the same 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.Birfy commentedon Oct 25, 2026
Continue deep-test confirm (2026-10-25)
Reconfirmed on https://social.botawaken.com: accepter sees "You already have Chief (SelfA1025). Your Chief is shared back…", but inviter sidebar still has no friend row for B. Owner asked to fix this track (already claimed). Not filing a duplicate for the "one-directional friendship UI" candidate.
Birfy commentedon Oct 25, 2026
Ark retest 2026-10-25
Reconfirmed on social.botawaken.com with live Ark models: Accept still gives no toast; inviter A has no friend row for B. Already claimed/fixing — no new duplicate.
Tell the inviter when someone accepts their invite