Skip to content

Tracer: Human @所有 Bot mentions current Group members #542

Closed

Description

@DoodleBears

Feature ownership — 2026-09-30

Project: https://github.com/orgs/BotHarness/projects/2. Historical umbrella #30 is retired. Existing implementation acceptance and active claims are preserved; this organization change does not claim the feature is complete.

Parent

Goal

A Human in a Group Channel can choose @所有 Bot once instead of entering a mention for every joined PersonaBot. This is a composer shortcut for ordinary direct mentions, not a new broadcast event, attention kind, or Wake Policy. A PersonaBot cannot use this shortcut.

First tracer

A local Human opens one Group Channel with two active joined PersonaBots, selects @所有 Bot, sees the recipient count, and sends one message. Messaging commits one Channel Source Event with both stable Bot targets, creates one ordinary Inbox Admission per recipient, and applies each recipient's existing direct-mention attention and Wake Policy semantics. The Channel history and Human unread projection still contain one message. Each Bot can act from its own Admission. The same result survives restart.

Rules

  • The Host derives recipients from active Bot members of the current Channel at send time. The Client cannot authorize a different set with pasted text or a supplied ID list.
  • If membership changed since the count preview, reject the stale send and return the new count so the Human can send with that visible set. Zero eligible recipients cannot send this mention.
  • Do not include other Channels, inactive or non-member Bots, or Human members. Do not create a second Source Event or a special wake path.
  • Existing per-Bot loop guards, deduplication, permissions, and attention handling continue to apply.

Acceptance

  • One Human gesture targets exactly the active joined Bots in one Group and shows the recipient count before send.
  • Each target's Admission and wake behavior matches an individual direct @Bot in the same Channel; a silent ordinary-message preference does not suppress an explicit mention.
  • One Source Event and one human-facing unread message appear regardless of recipient count.
  • Stale preview, no eligible Bot, Bot-authored attempt, and restart behavior are covered in focused Host/Client tests and a Human-testable runtime path.

Activity

  1. added this to the v1.1 milestone on Sep 30, 2026
  2. added
    enhancementNew feature or request
    needs-triageMaintainer needs to evaluate this issue
    area:fullstackEnd-to-end Host and Client implementation
    feature:messagingMessaging module and external providers
    scope:tracerHuman-testable implementation slice
    on Sep 30, 2026
  3. DoodleBears commented on Oct 2, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a0f083-4337-71d2-8639-dec84699b8d9 (not a DSH Session)
    • Issue scope: Tracer: Human @所有 Bot mentions current Group members #542 — Human Group composer all-Bot shortcut, Host-authoritative recipient preview/stale rejection, ordinary mention Admissions and real DSH evidence.
    • Branch: codex/542-all-bot-mention
    • State: active
    • Delivery: one PR; pause after runtime evidence and checks for Human QA.
  4. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 2, 2026
  5. DoodleBears commented on Oct 2, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

    • Agent: Codex
    • Task: codex/local/01a0f083-4337-71d2-8639-dec84699b8d9 (not a DSH Session)
    • State: paused — awaiting Human QA
    • Delivery: feat: Human all-Bot Group mention shortcut (#542) #730, commit 896bdb5a2d4b27b61cbf99b79b509a79070cbb81
    • Verified: actual DSH counted selection; two real model replies with silent ordinary Group policy; paused/outside exclusion; stale draft recovery; zero-recipient blocked Send; DM scope; restart persistence. Light/dark, narrow, stale and restart screenshots are in the PR.
    • Checks: complete Linux CI passed, plus Standards/Spec review. CodeRabbit was rate limited and did not perform a fresh review.
    • Remaining scope: Human QA and merge after acceptance. No next issue starts before that review.
  6. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 2, 2026
  7. DoodleBears commented on Oct 2, 2026

    @DoodleBears
    ContributorAuthor

    Human QA refinement: clean @bot picker

    Individual Bot menu rows now show only avatar, display name and existing role labels. Untagged Bots show avatar/name only; neither row falls back to a technical ID. Stable IDs remain the internal mention targets.

    Actual DSH verified tagged and untagged rows and asserted no Bot ID in menu text. Updated light/dark and narrow screenshots are embedded in the PR. Types, existing Composer/Profile tests and complete Linux CI passed. Standards/Spec incremental reviews passed; CodeRabbit is still rate limited.

    Task: codex/local/01a0f083-4337-71d2-8639-dec84699b8d9.
    State: paused, awaiting Human QA. Commit: 497b7e7eb8cad6766947d124b6e2495fdecd802c.

  8. DoodleBears commented on Oct 3, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome — merged

    • Task: codex/local/01a0f083-4337-71d2-8639-dec84699b8d9.
    • State: completed.
    • Human QA accepted; merge explicitly authorized.
    • PR feat: Human all-Bot Group mention shortcut (#542) #730 merged as a559ab293627125cadb553cd56ce06c5fe001938.
    • Delivered: counted Human Group all-Bot shortcut, Host-authoritative recipients/stale rejection, ordinary per-Bot Admissions and wake behavior, clean avatar/name/role-label picker.
    • Evidence: actual DSH screenshots, real-model replies, stale/zero/DM scope and restart; full exact-head CI passed. Standards/Spec reviews passed; CodeRabbit's last incremental attempt was rate limited with no actionable comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:fullstackEnd-to-end Host and Client implementationenhancementNew feature or requestfeature:messagingMessaging module and external providersneeds-triageMaintainer needs to evaluate this issuescope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions