fix(seer): Parse widget conditions into structured filters for LLM context

[Mihir-Mavalankar]

• The raw Sentry search syntax in widget conditions (e.g. span.name:Containsqueue.task.taskworker) was passed directly into the LLM context tree. The Seer Explorer agent couldn't distinguish operators from values, causing it to misinterpret filters and make broken tool calls that returned no results.

+Add getSearchFiltersForLLM() in widgetLLMContext.tsx that wraps parseSearch to convert raw conditions into structured {field, op, value} objects with human-readable operators (via OP_LABELS) and negation support. Falls back to the raw string if parsing fails.

  Before:
  "conditions": "span.description:Contains[task1,task2] span.name:Containsqueue.task.taskworker !trigger_path:Containsold_seer_automation"

  After:
  "conditions": [
    {"field": "span.description", "op": "contains", "value": "[task1,task2]"},
    {"field": "span.name", "op": "contains", "value": "queue.task.taskworker"},
    {"field": "trigger_path", "op": "NOT contains", "value": "old_seer_automation"}
  ]

• link to sample conversation: https://sentry.sentry.io/explore/conversations/?project=6178942&statsPeriod=24h&query=user.email:mihir.mavalankar@sentry.io&conversationSpan=8fff88f4e071e733&conversation=12972955&conversationStart=1775611105120&conversationEnd=1775611117059

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 602b5c0. Configure here.}

[cursor]

Filter parsing drops query logic

High Severity

getSearchFiltersForLLM keeps only Token.FILTER entries and discards non-filter tokens. Queries containing OR, parentheses, or mixed free text lose their original semantics when converted into conditions, so the LLM context can represent a different query than the widget actually runs.

 

^{Reviewed by Cursor Bugbot for commit 602b5c0. Configure here.}