fix(app): filter screen-share artifacts from participant names#6
Merged
Conversation
What: Add heuristic filters to ParticipantReader.filterParticipantNames to reject strings that are clearly not human names. Reasoning: - Problem: When someone screen-shares (e.g. a settings page), Teams' AX tree includes shared content elements. Strategy 2 picks up AXList/AXTable text from the shared screen as "participants", resulting in UI navigation text appearing as speaker labels in the transcript. - New filters: max 60 chars, no → or › arrows, no trailing colons, no URL patterns (.com/.ai/.io/://), no multi-slash paths. - These are conservative — real participant names won't trigger them.
pasrom
force-pushed
the
fix/participant-filter-screen-share
branch
from
45f5bd0 to
3e13a75
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.
Summary
Geh in Claude.ai → Settings → Connectors/Integrations → Atlassian-Verbindung:to appear in transcriptsParticipantReader.filterParticipantNames: max length (60 chars), no navigation arrows (→/›), no trailing colons, no URL patterns, no multi-slash pathsTest plan
ParticipantReaderTestspass