Skip to content

Tracer: Set and reset Human Channel nicknames in DM and Group headers #622

Closed

Description

@DoodleBears

Parent

Spec #619, a native child of Human Inbox #126. Design authority: ADR-0103, delivered in PR #618.

What to build

The Human can set My nickname in the header menu of a participating PersonaBot DM or Group Channel and clear it to resume the plugin default. Different conversations can show different roleplay names while using the same stable Human identity, personal Inbox and name-resolution behavior delivered by the default-name slice.

Acceptance criteria

  • Participating DM and Group Channel headers offer My nickname and restore-default, using the authorized existing Human command path.
  • Canonical Host resolution is Channel nickname → plugin default → Human; an explicit nickname is independent of later default changes, including when its text initially equals the default.
  • Clearing a nickname resumes inheritance and updates the same Channel's author, Human member/receipt, trusted mention, Inbox source context and newly queried/assembled Bot context labels.
  • The default Little Bear / DM Captain / Group Researcher scene works; renaming the Group to Professor leaves the DM unchanged and updates the Group's historical typed @ label.
  • Changing the default affects only inheriting Channels; two Channels never substitute one another's nickname in Human Inbox.
  • Every nickname retains one local Human ID and one Inbox, preserving unread positions, actions, canonical messages and Bot attention.
  • Duplicate names, ordinary text and unavailable-target fallback retain the default-name slice's identity rules.
  • Two windows and Host restart reconstruct both overrides and inheritance; readonly Bot-to-Bot inspection does not become a Human-participating Channel or allow a nickname there.
  • Focused observable Host/Bridge/Client coverage plus a genuine DSH scene show DM/Group editing, reset, independent names, Bot-visible names and source-Channel Inbox labels.
  • One implementation PR includes screenshots or video evidence and pauses for Human QA before the next issue.

Blocked by

Activity

  1. added this to the v1.1 milestone on Oct 1, 2026
  2. added
    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:channelChannel chat, timeline, composer, and navigation
    feature:inboxBot Inbox and Human Inbox attention
    scope:tracerHuman-testable implementation slice
    feature:identityPersonaBot identity, lifecycle, and deletion
    on Oct 1, 2026
  3. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

  4. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 1, 2026
  5. DoodleBears commented on Oct 1, 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
    • PR: feat: independent Human Channel nicknames (#622) #645
    • Head: 84756ab
    • Scope delivered: independent Human Channel nicknames in participating DM/Group header menus, restore-default inheritance, source-Channel current labels for historical mentions/Inbox/Bot context, stable identity and current membership authorization.
    • Verification: genuine DSH screenshots, real Bot discovery of DM Captain / Group Professor, two windows, restore button, light/dark/narrow layout, source/read/attention invariants and cold restart. Latest-main restart passed; the screenshot matched the committed evidence. Complete exact-head CI passed (1,640 tests, 1 existing skip, lint/format/typecheck/build/generated bundle consistency/docs). Spec and Standards reviews passed; the reported CodeRabbit issue was fixed and its discussion resolved.
    • Evidence: https://github.com/BotHarness/BotHarness/blob/codex/622-human-channel-nickname/docs/assets/pr/622-human-channel-nickname/README.md
    • Remaining: Human QA and merge approval. Check any subsequent automated review before merge; the next issue starts only after Human QA approval.
  6. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 1, 2026
  7. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

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 areafeature:channelChannel chat, timeline, composer, and navigationfeature:identityPersonaBot identity, lifecycle, and deletionfeature: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