Repository navigation
feat(tools): add search_issue_events tool with AI agent - #688
Merged
Merged
Conversation
Implement new search_issue_events tool that filters events within a specific issue using natural language queries. This fills the gap between search_events (searches across all issues) and get_issue_details (returns one event). Key features: - Natural language query translation via embedded GPT-4o agent - Filters by time, environment, release, user, trace ID, and custom tags - Automatically constrains results to specified issue - Support for both issueId + organizationSlug and issueUrl parameters Additional changes: - Add pointer to search_issue_events in get_issue_details output - Remove CLAUDE.md files from all tool directories (not needed in source) - Simplified tool description from 28 to 10 lines for clarity Closes #685 - filter historical events within specific issues Partially addresses #534 - better event browsing for investigation Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Update tool count expectations in use_sentry handler tests after adding search_issue_events tool (20 tools exposed to agent, 21 total including use_sentry). - Base case: 20 tools (21 total - use_sentry itself) - With org constraint: 19 tools (20 - find_organizations) - With both constraints: 18 tools (20 - find_organizations - find_projects) Also updated snapshots for related tests. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
The sort parameter was extracted from the agent response and validated, but never passed to the listEventsForIssue API call. This meant events were always returned in the API's default order regardless of the agent's sorting decision. Changes: - Add sort parameter to listEventsForIssue API method signature - Pass sort to URL params in API call - Update handler to pass sortParam to API call This matches the pattern used in search_events handler (line 187). Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
This branch was previously deployed
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.
Implement new search_issue_events tool that filters events within a specific issue using natural language queries. This fills the gap between search_events (searches across all issues) and get_issue_details (returns one event).
Key features:
Additional changes:
Closes #685 - filter historical events within specific issues Partially addresses #534 - better event browsing for investigation