feat(args): parse Sentry web URLs as CLI arguments#252
Merged
Conversation
Contributor
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Build
Other
Bug Fixes 🐛Telemetry
Other
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
Contributor
Codecov Results 📊✅ Patch coverage is 89.52%. Project has 4103 uncovered lines. Files with missing lines (71)
Coverage diff@@ Coverage Diff @@
## main #PR +/-##
==========================================
+ Coverage 68.53% 68.74% +0.21%
==========================================
Files 109 110 +1
Lines 13010 13124 +114
Branches 0 0 —
==========================================
+ Hits 8916 9021 +105
- Misses 4094 4103 +9
- Partials 0 0 —Generated by Codecov Action |
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
BYK
commented
Feb 16, 2026
src/lib/sentry-url-parser.ts
Outdated
Comment on lines
137
to
139
| if (process.env.SENTRY_URL) { | ||
| return; | ||
| } |
Member
Author
There was a problem hiding this comment.
I'd say the parsed URL should take precedence over any previously set env variable.
Users can now paste Sentry web URLs directly as CLI arguments instead
of manually extracting org/project/issue IDs. Supports both SaaS
(sentry.io) and self-hosted instances.
URL patterns supported:
- /organizations/{org}/issues/{id}/ (issue view/explain/plan)
- /organizations/{org}/issues/{id}/events/{eventId}/ (event view)
- /settings/{org}/projects/{project}/ (project commands)
- /organizations/{org}/traces/{traceId}/ (trace commands)
- /organizations/{org}/ (org-scoped commands)
For self-hosted URLs, automatically sets SENTRY_URL so that API calls,
OAuth device flow, and token refresh target the correct instance.
Also fixes frozen module-level constants in oauth.ts and sentry-client.ts
that captured SENTRY_URL at import time, preventing dynamic URL detection
from working.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
- Event URLs no longer trigger OrgAll → ContextError; instead they auto-detect org/project after SENTRY_URL is set (HIGH) - SaaS URLs now clear stale SENTRY_URL so API calls use default routing instead of a leftover self-hosted value (MEDIUM) - Non-issue URLs (traces, project settings) in parseIssueArg now throw ValidationError instead of falling through to garbage slash-based parsing (LOW)
process.env.SENTRY_URL = undefined sets the string "undefined" in Node.js (Bun handles it correctly). Use delete with a biome-ignore to truly unset the env var when a SaaS URL is detected.
There was a problem hiding this comment.
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.
Instead of discarding the org extracted from event URLs, pass it as OrgAll target and handle OrgAll in viewCommand by falling through to auto-detect. This keeps the org context available while resolving the project via DSN detection or config defaults.
BYK
commented
Feb 16, 2026
Comment on lines
+215
to
220
| // Org-only (e.g., from event URL that has no project slug). | ||
| // Fall through to auto-detect — SENTRY_URL is already set for | ||
| // self-hosted, and auto-detect will resolve the project from | ||
| // DSN, config defaults, or directory name inference. | ||
| // falls through | ||
| case ProjectSpecificationType.AutoDetect: |
There was a problem hiding this comment.
Bug: The event view command discards the organization parsed from an event URL, causing it to potentially fetch the event from the wrong organization based on auto-detection.
Severity: MEDIUM
Suggested Fix
In the ProjectSpecificationType.OrgAll case within src/commands/event/view.ts, pass the parsed organization to the resolveOrgAndProject function. The call should be updated to await resolveOrgAndProject({ org: parsed.org, cwd, usageHint: USAGE_HINT }) to ensure the project lookup is constrained to the correct organization.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: src/commands/event/view.ts#L215-L220
Potential issue: When the `event view` command is used with a full event URL, the
organization is correctly parsed from the URL but is subsequently discarded. The
`resolveOrgAndProject` function is then called without the `org` parameter. This
triggers an auto-detection mechanism that may resolve to a different organization based
on local configuration or environment variables. As a result, the command may attempt to
fetch the event from the wrong organization, leading to a failure to find the specified
event.
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.
Summary
sentry issue view https://sentry.example.com/organizations/my-org/issues/32886/?project=2) instead of manually extracting org/project/issue IDsSENTRY_URLfor the sessionoauth.tsandsentry-client.tsthat prevented dynamic URL detection from workingURL Patterns Supported
/organizations/{org}/issues/{id}/issue view,issue explain,issue plan/organizations/{org}/issues/{id}/events/{eventId}/event view/settings/{org}/projects/{project}/project view,project list/organizations/{org}/traces/{traceId}/trace view/organizations/{org}/Changes
New Files
src/lib/sentry-url-parser.ts— Pure URL parser (parseSentryUrl) + self-hosted env config (applySentryUrlContext)test/lib/sentry-url-parser.test.ts— 30 unit tests covering all URL patterns, edge cases, and env var behaviortest/lib/sentry-url-parser.property.test.ts— Round-trip property tests verifying URLs built bysentry-urls.tscan be parsed backModified Files
src/lib/arg-parsing.ts— URL pre-parsing inparseIssueArg()andparseOrgProjectArg()src/commands/event/view.ts— URL handling inparsePositionalArgs()for event URLssrc/lib/oauth.ts— Replaced frozenconst SENTRY_URLwith lazygetSentryUrl()functionsrc/lib/sentry-client.ts— Removed frozenconst CONTROL_SILO_URL, madegetControlSiloUrl()read env var lazilyTest Updates
test/lib/arg-parsing.test.ts— Added URL integration tests for both parserstest/commands/event/view.test.ts— Added event URL handling testsFixes
Resolves CLI-66 (self-hosted users get confusing errors when pasting URLs)