Add keyword_tagger link for automatic tagging#132
Conversation
Co-Authored-By: Claude Opus 4.5 <[email protected]>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Free Tier Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
|
|
||
| # Other Content | ||
| "other": { | ||
| "profanity": ["fuck", "shit", "damn", "ass"], |
There was a problem hiding this comment.
Substring matching "ass" causes pervasive false profanity tags
High Severity
The profanity keyword list includes "ass", but find_keywords uses plain substring matching (if search_keyword in text). This means any transcription containing common words like "class", "pass", "assistant", "assessment", "assume", "mass", or "classic" will be falsely tagged as containing profanity. Nearly every non-trivial conversation is likely to trigger this false positive.
Additional Locations (1)
| "categories": None, # None means all categories | ||
| "custom_keywords": {}, # Additional tag -> keywords mappings | ||
| "case_sensitive": False, | ||
| "min_confidence": 0.0, # Minimum transcription confidence to process |
There was a problem hiding this comment.
min_confidence option defined but never checked
Low Severity
The min_confidence option is declared in default_options with a documented comment about minimum transcription confidence, but it is never read or evaluated anywhere in the run function. Users configuring this option would get no effect, and low-confidence transcriptions would still be processed and tagged.


Note
Medium Risk
Moderate risk because it introduces new automated tagging that mutates stored vCons and may create false positives due to simple substring matching and broad keyword lists.
Overview
Introduces a new
server/links/keyword_taggerlink that extracts transcription text from vConanalysisentries (supports bothtranscriptionandwtf_transcription) and applies tags when predefined or user-supplied keywords are found.Supports optional config for enabled categories, custom tag-to-keyword mappings, and case sensitivity; when matches occur it persists the updated vCon back to Redis with the added tags.
Written by Cursor Bugbot for commit 59bff4c. Configure here.