Skip to content

feat(templates): direct-pubkey members in channel templates - #8253

Closed
jaxxon33 wants to merge 1 commit into
block:mainfrom
jaxxon33:feat/template-direct-members
Closed

jaxxon33 wants to merge 1 commit into
block:mainfrom
jaxxon33:feat/template-direct-members

Conversation

@jaxxon33

@jaxxon33 jaxxon33 commented Oct 11, 2026 •

Copy link
Copy Markdown

Opened by mistake from a private setup; closing.

Channel-template rosters only accepted personas and teams, both of
which resolve through persona instances — so standing agents already
on the relay (no persona entry) could never join a templated channel,
and a persona-shaped template would spin up clone instances instead.

Add an optional `members: [{pubkey, label?}]` roster to the template
wire shape in both duplicates (buzz-cli reader + desktop tauri types):

- CLI `channels create --template` validates every member pubkey before
  any channel-creation side effect (a typo aborts with zero channels),
  normalizes lowercase, dedups case-insensitively, and adds each member
  with role `bot` after persona-resolved agents. The channel creator is
  skipped — create already made them an owner, and a self-targeted
  kind:9000 is relay-rejected.
- Desktop template create/update rejects malformed member pubkeys at
  write time; apply-path adds members via addChannelMembers without
  creating any agents, treats "already a member" as acceptable, and
  invalidates the members cache.
- The settings editor preserves existing members across edits even
  though it doesn't yet expose member management.

Co-Authored-By: Fizz <noreply@buzz.local>
Signed-off-by: Fizz <b41ea9dccb4b6ad92951955cd373138a16184a3cba9184850053f581640e9ffc@buzz.tail0a48eb.ts.net>
@jaxxon33
jaxxon33 requested a review from a team as a code owner October 11, 2026 00:48
@github-actions

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 845fc16ebf5ec84f87a94ceaf69bb79c004b3a76...7f8ac172a371f286a6232f33065017fba82f3a57.
A new review must complete for this exact range. When manual authorization
is required, a user with write access must comment exactly
@buzz-security-review 7f8ac172a371f286a6232f33065017fba82f3a57 to authorize a new review.
Any previous review applies only to its recorded range.

@jaxxon33 jaxxon33 closed this Oct 11, 2026
@jaxxon33
jaxxon33 deleted the feat/template-direct-members branch October 11, 2026 01:24
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