Skip to content

Tracer: Reply to a Channel message from Human Inbox #547

Closed

Description

@DoodleBears

Parent

What to build

From an unread Channel message in Human Inbox, the local Human can inspect a short expandable source context and send a direct reply without leaving the Inbox. The reply uses the same authorized Channel send and reply reference as the source conversation; the Human can still open that exact Channel position instead.

Acceptance criteria

  • An unread Group or Bot DM message exposes the exact source message and a concise expandable context before reply; source navigation remains available.
  • Submitting a reply creates one canonical Channel Source Event with the correct reply reference and author. It appears in the source Channel and can be seen by the intended participants through the existing delivery path.
  • A stale, deleted, inaccessible, or failed source cannot produce a misleading successful reply; the Human retains their draft and sees a usable error.
  • The Inbox does not create a second message or action store. Viewing concrete content and read-position changes follow Tracer: Human Inbox Group unread summary and deliberate read #546's rules.
  • Focused Host/Bridge and Client tests plus a runnable Group or DM path prove inline reply and exact source navigation.

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: inline Human Inbox reply to a Group or Bot DM source, concise context, canonical reply reference, draft retention on invalid sources, and real DSH visual E2E evidence.
    • Branch: codex/547-human-inbox-reply
    • 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

  6. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 30, 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-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions