Skip to content

feat(profiles): show verified agent owner and archive state #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wesbillman merged 5 commits into from
Sep 24, 2026
Merged

feat(profiles): show verified agent owner and archive state #232

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c8c5c88
feat(profiles): show verified agent owner and archive state
Sep 24, 2026
f9880b6
fix(profiles): seed agent owner from directory head and use formatPub…
Sep 24, 2026
470b757
fix(profiles): seed agent owner from directory head only with a live …
Sep 24, 2026
d0c833c
fix(profiles): notify profile directory subscribers on winning-event …
Sep 24, 2026
89bbe76
fix(profiles): match buzz "managed by" owner row and drop archive row
Sep 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions docs/profiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,36 @@ add the agent again from the managed-agent profile. Older unguarded invitation
records can be promoted to guarded intent when reused through that profile flow.
Remove from outbox does not revoke an invitation already dispatched to the relay.

## Agent identity

For an identity with an agent hint (below), the Info tab adds a **Managed by**
row, matching Buzz desktop. It shows only a verified owner and is otherwise
absent:

- The owner comes from the NIP-OA `auth` tag on the identity's own winning
signature-verified kind 0 (newest `created_at`, lower id on ties). A
session-owned `session.observe` view supplies that event: it merges live
events, refreshes on reconnect and resets on purge. While that view is live,
the profile directory's retained signed head also seeds that choice, so
reopening the pane after cache eviction never accepts an older response than
the profile the session already shows. The directory notifies subscribers
when that head changes even if display fields do not, so a head restored
from disk also updates the pane. Verification is bound to that exact event
id, so an auth-only change or a lagging older read never keeps or restores a
previous owner. It requires exactly one tag, owner ≠ agent, conditions
evaluated against the event, and a valid BIP-340 signature over
`nostr:agent-auth:<agent>:<conditions>`.
- The row shows the owner's name (`formatPublicKey` without a profile name),
with "(you)" when the viewer is the owner. It opens the owner's profile in
the same slot when the host can open it.
- A missing or invalid tag, a failed read, or no available view shows no row.

@wesbillman wesbillman Sep 24, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking: qualify “a failed read” as “a failed read with no retained signed profile.” session.observe().refresh() preserves its remote evidence on error, and ProfileAgentIdentity selects from that evidence plus the retained directory head without checking read status. An already-verified owner therefore remains visible after a failed refresh, consistent with the retained name/avatar; this is not an ownership-verification bypass. Please align this sentence and the PR description with that behavior, and add error-with-retained-head / error-without-head cases to make the intended policy explicit.

Without a view nothing can signal an auth-only change, so the retained head is
not trusted; reopening the profile retries. The existing `isAgent` shape
check, avatar shape and local library never supply an owner.

Agent type and capabilities are not shown: buzz-app has no reader or contract
for their source (old Buzz kind 10100). This row has no controls.

## Boundaries

- Shared message UI recognizes author-avatar targets and identity-bound mentions.
Expand Down
Loading
Loading