Skip to content

Tracer: Trusted Bot @Human reaches personal Inbox mentions #549

Closed

Description

@DoodleBears

Parent

What to build

A joined PersonaBot can explicitly address the local Human in a Group Channel using a trusted Human target, and Human Inbox shows that committed message as a personal mention. The Human can open the exact Channel message or answer from the Inbox through #547. Ordinary text that merely resembles an @Human name does not create personal attention.

Acceptance criteria

  • The Host verifies a stable local Human target and current Group membership when a Bot sends the mention. A pasted name, stale identity, or non-member target cannot forge a Human mention.
  • One Channel Source Event appears once in Human mention attention and once in the Human unread count even if it also addresses several Bots; each Bot's own Admission and Wake Policy are unaffected.
  • The mention view shows the exact source, concise context, recent-first ordering, and Bot/Channel filters. Source navigation and inline reply use the existing authorized Channel path.
  • The target survives restart and name changes without resolving to the wrong Human. Focused Messaging/Host/Bridge/Client tests and a running Group path cover trustworthy targeting and deduplication.

Blocked by

Activity

  1. added this to the v1.1 milestone on Sep 30, 2026
  2. added
    enhancementNew feature or request
    ready-for-agentFully specified, ready for an AFK agent
    area:ui-uxInteraction and visual experience; may accompany a code-layer area
    area:fullstackEnd-to-end Host and Client implementation
    feature:inboxBot Inbox and Human Inbox attention
    scope:tracerHuman-testable implementation slice
    on Sep 30, 2026
  3. DoodleBears commented on Sep 30, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a0f083-4337-71d2-8639-dec84699b8d9 (not a DSH Session)
    • Issue scope: trusted Bot-to-local-Human Group mentions through the existing Channel sender, personal Inbox projection, canonical unread deduplication and existing exact navigation/inline reply.
    • Branch: codex/549-trusted-human-mentions
    • Started: 2026-09-30 19:34 UTC
    • State: active
  4. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 30, 2026
  5. DoodleBears commented on Sep 30, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

    • Task: codex/local/01a0f083-4337-71d2-8639-dec84699b8d9
    • State: paused — awaiting Human QA
    • PR: feat(inbox): trusted Group mentions reach Human Inbox (#549) #605
    • Head: 639d6c3889423a8532557d6ce58a1cf16c96cdc4, integrated with main 97b312e.
    • Delivered scope: trusted current Group Human targets, durable Source Event metadata, personal mention/reply deduplication, unchanged Bot admission semantics, filters, expandable context, canonical inline replies and exact source navigation.
    • Verification: model-backed two-Bot/two-Group E2E, light/dark/narrow screenshots, second browser window and Host restart; focused Host/Tool/Bridge/Client regressions; final-head CI full tests/format/typecheck/lint/build/generated/docs gates all passed. CodeRabbit runtime validation finding fixed with malformed-input regressions; final CodeRabbit check passed with no open review threads.
    • Human QA: Bot mode → Inbox → Mentions & replies; select either QA Bot, expand nearby messages, answer inline and open the exact source. Screenshots and repeatable QA path.
    • Remaining scope: Human QA, then approved merge; no subsequent Spec: Human Inbox unread, personal attention and actions #126 issue has been started.
  6. added and removed
    ready-for-agentFully specified, ready for an AFK agent
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 30, 2026
  7. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    ContributorAuthor

    Agent work resumed

  8. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 1, 2026
  9. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

  10. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 1, 2026
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 implementationarea:ui-uxInteraction and visual experience; may accompany a code-layer areaenhancementNew feature or requestfeature:inboxBot Inbox and Human Inbox attentionready-for-humanRequires human implementationscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions