search_issues agent strips punctuation from quoted phrases

Aberta
  • Algo errado?
#2,212 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
ai, search

Direção de pesquisa

Start with the search_issues path in search-issues.ts (around lines 195-244, where the query goes to Seer or the embedded agent) and the agent prompt in support/search-issues/config.ts (lines 11 and 25). Check whether a quoted phrase containing parentheses survives the agent's rewrite, and how rewriteSearchQuery treats it. Done means a quoted phrase like "organization step(s) failed" is passed through unchanged, or any rewrite is reported in the result notes.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Through the embedded repair agent, search_issues can rewrite a quoted literal phrase. In MCP-SERVER-GPC (opencode, server 0.42.0), "organization step(s) failed" was reported to run as organization step failed. It returned nothing, though a matching issue existed (a search for organization found it).

  • Not verified from telemetry: the failing call isn't in the sampled spans, and the feedback trace is unsampled. The call path below comes from code and from the same caller's other calls.
  • The deterministic rewrite keeps the phrase: rewriteSearchQuery('"organization step(s) failed"', { issueSearch: true }) returns it unchanged with no notes. A quoted phrase alone isn't structured syntax (looksLikeSentrySearchSyntax → false), so it goes to Seer or the agent (search-issues.ts:195-244).
  • This org uses the agent path: the same user and org's earlier quoted search_issues call (trace e90e6dd4…, 2026-11-10, "timeout of 20000ms exceeded") shows the org feature-flag GET and then callEmbeddedAgent, with no Seer translate call. That run kept the quotes, so the rewrite seems tied to the punctuation.
  • Likely trigger (inference): the agent prompt counts only field:value forms as explicit tokens (support/search-issues/config.ts:11), so a quoted free-text phrase is natural language that the agent may rewrite. It also says parentheses are "invalid in issue search even when written explicitly" (config.ts:25), which doesn't separate grouping parens from literal characters inside a quoted phrase.
  • The rewrite is silent: the result's notes only include rewrites from rewriteIssueQuery (search-issues.ts:282-289). An agent rewrite shows up only as the changed executedSearch.query, and the explanation only appears with includeExplanation.

Related: the same feedback's search_logs part (unknown attribute with no suggestions) is in #2211.

via Sentry.

--

View Session [Sentry]

Linguagem predominante
TypeScript
Estrelas
961
Forks
179
Merge médio
15h 33min
PRs com merge (30d)
476

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de getsentry/toolkit

Todas as issues de getsentry/toolkit

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.