Skip to content

Group @ menu: handle/.home and (Friend) inserts do not call room members #1141

Description

@Birfy

Owner decision (2026-10-25 Asia/Shanghai)

拉了群就应该都能发消息,而不是还要加好友 — co-members in a live shared group must be able to message each other (group @ and sidebar 1:1) without a separate friendship / Sharing grant.

Repro A — @ insert / no answer (研发组)

  1. Ordinary group with friend's Chief + local Architect/Backend/…
  2. @ picker: Architect as architect.…home, others as (Friend).
  3. Lines that call nobody: @@architect.flybot….home …, Backend (Friend) 你好啊 (no @).

Repro B — sidebar DM not friends

  1. From the shared-group context, open sidebar chat Architect (flybot682b8a43) (projected / cross-home seat).
  2. Send 「你是谁」.
  3. Actual: Not sent: you are not friends with this Bot. Add them from + Add friend.
  4. Expected: send succeeds because both sides share a live group (same spirit as Name the room on a platform-room send: pass room_id on the claimed-room path only #881 face-room / Friend Bot in shared local group cannot message peer @…home — blocked as not shared #1126 ticket @; Deliver shared-room mentions without a Sharing grant #1130 merged for ticket mentions — this is the DM/sidebar path).

Acceptance

  1. Group @ insert uses seat/Bot name the host routes on; no @@; no .home as the call token; no (Friend)-only insert.
  2. Live co-members: sidebar/DM send and in-group @ work without friendship.
  3. After leaving the room (or never sharing one): stranger refuse may remain.
  4. Tests for insert routing + room-scoped reach without friendship.

Claim and fix.

Activity

  1. added
    bugSomething isn't working
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    area:uiWeb/desktop UI and copy
    on Oct 25, 2026
  2. self-assigned this
    on Oct 25, 2026
  3. Birfy commented on Oct 25, 2026

    @Birfy
    CollaboratorAuthor

    Claimed by bot-im. CloudAgent bc-7b72d208 fixing. Owner asked to fix after 研发组 repro: @@architect.…home and Backend (Friend) call nobody.

    @ picker: Architect as .home handle vs Friend rows

    Chat: @@handle and Backend (Friend) unanswered

  4. Birfy commented on Oct 25, 2026

    @Birfy
    CollaboratorAuthor

    Owner: 拉了群就应该都能发消息,而不是还要加好友. Sidebar DM to Architect (flybot682b8a43) hits Not sent: you are not friends — expand fix beyond @ insert (#1130 already merged for ticket @).

    DM Not sent: you are not friends despite shared group

  5. Birfy commented on Oct 25, 2026

    @Birfy
    CollaboratorAuthor

    Same rule, another path (FlyBot 交付组): after @chief, reply fails with
    Chief is not friends with @flybot98b8ecba.home: that friendship is with @architect.flybot682b8a43.home only.
    Owner: friendship via Architect must not block other co-members in a shared group from messaging that friend home.

    Chief not friends with flybot98 — only Architect has the link

  6. Birfy commented on Oct 25, 2026

    @Birfy
    CollaboratorAuthor

    Owner: flybot98b8ecba already deleted, but sends still show rejected / not-friends. Stale remote seat + friendship-via-Architect-only must clear when the friend home is gone; shared-group co-members must not depend on that friendship edge.

  7. removed
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    on Oct 25, 2026
  8. added 3 commits that reference this issue on Oct 25, 2026
    c0a3369
    5152f73
    0972daa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:uiWeb/desktop UI and copybugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions