Skip to content

Friend Bot in shared local group cannot message peer @…home — blocked as not shared #1126

Closed

Description

@Birfy

Repro (prod social.botawaken.com, 2026-10-25 Asia/Shanghai)

  1. Owner home u-682b8a… and friend home u-98b8ecba… are both in local group 研发组.
  2. From the friend side, Chief tries to send / reply toward @chief.flybot682b8a43.home.
  3. UI shows the intended line, then:

Chief: not sent — @chief.flybot682b8a43.home is not a Bot a friend shared with you, so your Bots cannot message it. Its owner can share it with you in that Bot's settings -> Sharing.

Screenshot attached in the filing chat (owner message).

Expected

Once both homes share a local group seat, a Bot on one home should be able to address the peer Bot that is already in that group (by the mention / home address the product surfaces), without a separate pre-existing Sharing grant. Or, if Sharing is still required for 1:1 .home DMs, the group path must not route to that refusal — e.g. send as a room-share / in-group line instead of a stranger 1:1.

Actual

Reach check treats the peer as a stranger for 1:1 messaging even though both are active members of the same local room. Group collaboration breaks: friend Bots cannot talk back to the owner's Bot they were invited to work with.

Hypothesis (non-binding — investigate)

Outbound may be resolving the mention to a .home 1:1 send that requires a Bot Social share/grant, instead of the room-share / seat path used for in-group lines. Related history: local-room invite seats (#852/#853/#864), room_id / claimed-room reach (#866), Group-update / @ approval (#1113/#1118).

Acceptance

  1. In a shared local group (both seats live), a Bot on home A can successfully send a line that addresses home B's Bot already in that group (same mention shape the UI offers), and home B receives it as a normal in-group / peer line — no "not a Bot a friend shared" refusal.
  2. Without a share grant, a pure 1:1 DM to a stranger Bot outside any shared room is still refused with a clear sentence.
  3. Leaving the group / seat revoked restores the refusal for that peer.
  4. Automated test covers the green path (same local room) and the stranger negative control.

Labels / claim

Owner deep-test; claim and fix immediately.

Activity

  1. self-assigned this
    on Oct 25, 2026
  2. added
    bugSomething isn't working
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    area:socialFriends, invites, grants, Bot Social
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    and removed
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    on Oct 25, 2026
  3. added a commit that references this issue on Oct 25, 2026
    dca05d4
  4. removed
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 25, 2026
  5. added 2 commits that reference this issue on Oct 25, 2026
    44f3e97
    c0a3369
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:socialFriends, invites, grants, Bot SocialbugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions