feat(agents): gate activity-feed ingress by relay ownership#1060
Open
tellaho wants to merge 3 commits into
Open
feat(agents): gate activity-feed ingress by relay ownership#1060tellaho wants to merge 3 commits into
tellaho wants to merge 3 commits into
Conversation
This was referenced Jun 15, 2026
- Add a relay ownership endpoint backed by agent_owner_pubkey and is_agent_owner so desktop activity visibility uses the same source of truth as observer telemetry authorization. - Add a Tauri ownership command, frontend API wrapper, and useCanViewAgentActivity hook with local managed-agent optimism only while relay ownership is loading. - Replace profile popover, profile panel, and members sidebar activity gates so owned agents can open activity across different builds and worktrees without relying on local managed-agent lists. - Refactor channel agent session candidate resolution so owned agents can keep an activity panel open when channel metadata is stale, while preserving local-only lifecycle controls. - Add focused desktop unit coverage for the ownership predicate and stale-metadata session resolution path, plus E2E bridge support for ownership mocks.
- Extend canViewAgentActivity coverage for relay-backed agent sessions - Harden Tauri ownership resolution and observer relay scoping - Wire updated visibility rules through profile panel and popover surfaces
- Update channel activity candidate resolution to treat ChannelMember.isAgent the same as bot role membership. - Keep agent typing classification and Activity panel scoping aligned so agent typing does not fall through to the generic human typing row. - Add regression coverage for isAgent channel members being created as activity candidates and retained in channel scope.
tellaho
force-pushed
the
tho/activity-ingress-ownership
branch
from
23fde5c to
0851322
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Category: improvement
User Impact: Agent activity in the desktop Activity panel now consistently shows up and respects relay ownership, so people only see activity they are entitled to.
Problem: Activity ingress was not reliably gated by ownership, and agent members were not classified for ingress — activity could surface inconsistently or to the wrong viewers.
Solution: The ingress + ownership foundation: relay-side ownership gating, refined visibility ownership checks, and agent-member classification for activity ingress (relay
.rs+ Tauri ownership commands + client viewer hooks), backed by ownership-resolution and agent-session-candidate tests.Commits
feat(agents): gate activity by relay ownershipfeat(agents): refine activity visibility ownership checksfix(agents): classify agent members for activity ingressReproduction steps
🤖 Branch split + PR by Ned (sequencer) / Bart (builder).