Document query syntax in search_sentry and drop the embedded search agents

Open
#1,896 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
43/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
ai, cli

Research direction

Read the linked cli-first-mcp design and tasks, then inspect the search_sentry entries for search_events, search_issues, and search_issue_events, along with their evals. The issue says the search-agent prompts and OpenAI/Anthropic provider config are removed at cutover; confirm the dependency on #1895 is complete first. Done means each command entry carries its query syntax and the evals check query quality.

Written by the indexing model from the issue text.

Description

enhancement MCP

Part of #1357. Plan: cli-first-mcp task 5.3 (design, tasks). Depends on #1895.

search_events, search_issues, and search_issue_events translate natural language with a second model call. Under this plan the calling agent writes the query itself.

Scope

  • Put the query syntax for each search command in its search_sentry entry, replacing the search agents' prompts.
  • The search agents and the OpenAI/Anthropic provider config are deleted at cutover. That also makes #1754, #1307, #1290, and #1226 moot.

Done when

  • Search-command entries carry the syntax, and the evals check query quality.

via @BYK.

--

View Session in Sentry

Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.