Skip to content

feat(desktop): register existing agents by pubkey - #7237

Open
DamirAGI wants to merge 2 commits into
block:mainfrom
DamirAGI:argus/register-existing-agent
Open

feat(desktop): register existing agents by pubkey#7237
DamirAGI wants to merge 2 commits into
block:mainfrom
DamirAGI:argus/register-existing-agent

Conversation

@DamirAGI

@DamirAGI DamirAGI commented Sep 2, 2026

Copy link
Copy Markdown

Summary

  • Add an owner-only Desktop flow to register an independently operated Nostr agent by its existing pubkey.
  • Verify the live kind:0 NIP-OA owner attestation, reject locally managed identities, and publish only an owner-signed kind:30177 directory record.
  • Make Desktop discovery policy explicit with respond_to plus an exact normalized allowlist; registration does not take key custody or create/start a local runtime.

Related issue

N/A. Closest existing work: #6571 implements a related owner-reviewed registration path but currently hard-codes owner-only discovery; #6321 covers display-only external agent references.

Testing

  • just desktop-ci (passed on 3a582a1b89af59634c86022642ac241c083c2ba2; frontend 5882/5882, Tauri workspace tests passed)
  • cd desktop && pnpm build:e2e && pnpm exec playwright test --project=integration tests/e2e/agents.spec.ts --grep "registers an existing agent without creating a local persona" (1/1 passed)
  • Repo-wide just ci was also attempted. It reached the Rust test lane but was not green because of pre-existing crates/buzz-acp timing-test instability outside this diff; the affected Desktop package gate above completed successfully.

UI behavior is covered by the Playwright owner-review scenario; no production or installed Desktop state was modified.

Signed-off-by: Damir Mujic <damir@agirails.io>
Signed-off-by: Damir Mujic <damir@agirails.io>
@DamirAGI
DamirAGI requested a review from a team as a code owner September 2, 2026 15:31
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 1c8321cd08feb597f8bcff5195c21148fb3e98ed...3a582a1b89af59634c86022642ac241c083c2ba2.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review 3a582a1b89af59634c86022642ac241c083c2ba2 to authorize a new review.
Any previous review applies only to its recorded range.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant