Skip to content

Improve mentions for agents + people #942

Merged
klopez4212 merged 2 commits into
mainfrom
kennylopez-mentions-tagging
Jun 10, 2026
Merged

Improve mentions for agents + people #942
klopez4212 merged 2 commits into
mainfrom
kennylopez-mentions-tagging

Conversation

@klopez4212

Copy link
Copy Markdown
Contributor

Summary

  • Add persona/agent-first mention autocomplete with agent chips and non-member labels
  • Reuse, create, start, and deploy mentioned agents before sending
  • Render agent mentions consistently in composer, messages, and system rows

Tests

  • bin/just fmt-check
  • bin/just desktop-tauri-fmt-check
  • bin/just desktop-check
  • bin/pnpm --dir desktop build
  • bin/just desktop-tauri-check
  • bin/just desktop-tauri-test
  • bin/pnpm --dir desktop exec playwright test --project=smoke tests/e2e/mentions.spec.ts
  • git diff --check

@klopez4212 klopez4212 force-pushed the kennylopez-mentions-tagging branch 3 times, most recently from c93f73b to b487051 Compare June 10, 2026 13:02
@klopez4212 klopez4212 changed the title Improve agent mentions Improve mentions for agents + people Jun 10, 2026
@klopez4212 klopez4212 force-pushed the kennylopez-mentions-tagging branch 2 times, most recently from f67cd87 to 99c7d2a Compare June 10, 2026 13:28
@klopez4212 klopez4212 marked this pull request as ready for review June 10, 2026 13:30
@klopez4212 klopez4212 requested a review from a team as a code owner June 10, 2026 13:30

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 99c7d2aec1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread desktop/src/features/messages/ui/useMentionSendFlow.ts
Comment thread desktop/src/features/home/ui/InboxDetailPane.tsx
@klopez4212 klopez4212 force-pushed the kennylopez-mentions-tagging branch from 99c7d2a to f0bc999 Compare June 10, 2026 14:10

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f0bc9996df

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread desktop/src/features/channels/useMembershipNotifications.ts Outdated
@klopez4212 klopez4212 force-pushed the kennylopez-mentions-tagging branch from f0bc999 to a5d580f Compare June 10, 2026 14:23
…flicts

# Conflicts:
#	desktop/src/testing/e2eBridge.ts
#	desktop/tests/helpers/bridge.ts

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ea203bfa29

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +390 to +395
if (
channelType === null ||
channelType === "dm" ||
!mentions.hasResolvedMembers
) {
return [];

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Wait for members before skipping non-member prompts

When a stream/forum composer sends before getChannelMembers has resolved, this returns no non-member pubkeys, so a globally searched @person bypasses the invite/send-without-inviting dialog and is sent as a normal p mention even though the channel membership is still unknown. In slow relay/member-list loads this means outside users are mentioned without being invited or converted to reference-only mention tags; the send path should wait/refetch members (or otherwise treat unresolved membership as needing confirmation) before deciding there are no non-members.

Useful? React with 👍 / 👎.

@wesbillman wesbillman enabled auto-merge (squash) June 10, 2026 16:33
@tlongwell-block tlongwell-block disabled auto-merge June 10, 2026 16:36
@klopez4212 klopez4212 merged commit e9cd1c3 into main Jun 10, 2026
14 checks passed
@klopez4212 klopez4212 deleted the kennylopez-mentions-tagging branch June 10, 2026 16:40
tellaho added a commit that referenced this pull request Jun 11, 2026
PR #942 added a directory-wide gate that hides any agent from the
mention autocomplete unless it lives in the running build's
`managed-agents.json` or advertises `respondTo === "anyone"` on the
relay. The intent — keeping the relay's zombie zoo out of autocomplete
— is right for the global directory, but the gate is also applied to
agents that are already explicit channel members. That hides:

- the user's own agents owned by a different build (prod vs.
  dev/worktree split — each build has its own `managed-agents.json`)
- channel-added bots that defaulted to `respondTo: "owner-only"`

Explicit channel membership is itself an opt-in signal, so let those
candidates through unconditionally and keep the directory gate for
non-members and `userSearchQuery` hits.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
tellaho added a commit that referenced this pull request Jun 11, 2026
PR #942 added a directory-wide gate that hides any agent from the
mention autocomplete unless it lives in the running build's
`managed-agents.json` or advertises `respondTo === "anyone"` on the
relay. The intent — keeping the relay's zombie zoo out of autocomplete
— is right for the global directory, but the gate is also applied to
agents that are already explicit channel members. That hides:

- the user's own agents owned by a different build (prod vs.
  dev/worktree split — each build has its own `managed-agents.json`)
- channel-added bots that defaulted to `respondTo: "owner-only"`

Explicit channel membership is itself an opt-in signal, so let those
candidates through unconditionally and keep the directory gate for
non-members and `userSearchQuery` hits.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

2 participants