Desktop: Selected people chips show truncated pubkeys instead of display names

Open Beginner friendly
#5,678 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
react, typescript
Domain
authorization, frontend

Research direction

Start in desktop/src/features/agents/ui/RespondToField.tsx and compare its AllowlistPicker with PersonaShareRecipients and SelectedRecipientChip. Trace how useUsersBatchQuery can resolve the persisted pubkeys after reopening the editor. Done means selected-user chips show displayName, then nip05Handle, then the truncated pubkey fallback, with an avatar when available, while respond_to_allowlist remains hex pubkeys.

Written by the indexing model from the issue text.

Description

Summary

In Edit agent → Who can send instructions → Selected people, the selected-user chips render truncated hex pubkeys (e.g. 3fa38fb8…a2ef) instead of display names / NIP-05 handles. Search results already show names, but chips discard that metadata after add.

This makes it hard to tell who was granted agent access (computer/files/tools) when revisiting the allowlist.

Repro

  1. Open Edit agent on a managed agent.
  2. Set Who can send instructions to Selected people.
  3. Search for a community member by name and Add them.
  4. Observe the chip shows truncated pubkey, not the name from search.
  5. Close and reopen Edit agent — same truncated pubkey chips (no profile re-lookup).

Expected

Chips show displayName → nip05Handle → truncated pubkey fallback, with avatar when available — same pattern as PersonaShareRecipients / SelectedRecipientChip.

Actual

Chips always use truncatePubkey + <PubKey> with avatarUrl={null} in AllowlistPicker (desktop/src/features/agents/ui/RespondToField.tsx). Allowlist state is correctly persisted as hex pubkey strings; only the chip label needs profile resolution (e.g. useUsersBatchQuery).

Notes

  • Persistence should remain hex pubkeys (respond_to_allowlist).
  • Related but distinct from allowlist persistence bugs (#2501, #3030, #4487) and people-search matching (#3353).
Dominant language
Rust
Stars
33.7k
Forks
4.4k
Avg merge
1d 21h
Merged PRs (30d)
239

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from block/buzz

All issues in block/buzz

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.