[MathurAditya724]

Connect Local to a daemon's plain http://127.0.0.1:<port>/stream address to discover capturing and saved sessions. The searchable picker keeps feeds isolated, refreshes as runs start or expire, and restores the selected capture after reload. Human-readable Local commands print a hosted viewer link using the actual bound port; JSON output stays unchanged.

The workspace explains capture state and the scope of each action:

• Capture context shows the selected session/project, Capturing or Saved capture, receiver connectivity, last received time, and the receiver's original save deadline when supplied. Expired captures keep already displayed events readable.
• Clear view affects this tab only and keeps ingestion running. Delete captured events requires confirmation and deletes receiver history when the existing loopback permissions allow it. Reload stays disabled while receiver deletion is pending. Stop capture rejects later ingestion with HTTP 410 and saves a finite archive. Disconnect viewer leaves capture and receiver history intact.
• Switch receiver probes the replacement before changing the feed. Failed or cancelled attempts preserve existing events. Reload restores the tab’s successful receiver choice; choosing a local receiver supersedes that tab’s earlier remote choice. Past connections keep five successful receivers per tab, omitting displayed credentials and local session capabilities.
• Capture-first onboarding offers a copyable sentry local run --session web --open -- <your dev command> example, with connecting to an existing receiver as a secondary flow.
• Event inspection shows log messages/attributes, exception causes and stack frames, compact request summaries, and related telemetry. Diagnostic types open directly in original JSON.
• Span investigation opens a selected waterfall span's timing, attributes, original payload, and related errors/logs in the inspector. Back to trace restores focus to that span, drill-down preserves the active Traces filter, and event/trace/span selection works with URL history.
• Resizable panes support pointer and keyboard adjustment, preserve inspector space, and stack on narrow screens. Descriptions wrap and code, IDs, and timing use monospace.
• Navigation and search emphasize Events, Traces, Errors, Logs, and AI, with secondary views under Diagnostics. SDK reports distinguishes SDK reports from named Local captures. Search this session (Cmd/Ctrl+K) stays independent of the labelled view filter; filtering is explicit and has a Clear filter action. Existing /live and /sdks routes remain compatible.
• Settings separates app-wide appearance from History capacity for the selected capture. Capacity is measured in SDK envelope batches and is independent of the saved-capture deadline. Both client and receiver reject limits outside 1–50,000 or decreases that would discard retained envelopes.

Discovery uses a separate capability restricted to loopback and trusted hosted Local origins. Scoped retention updates require the session stream capability; discovery grants neither ingestion nor CLI control. Hosted viewers can update validated retention and clear their own view, but cannot delete receiver data or stop captures. Remote HTTPS streams stay read-only. Older receivers can connect without discovery; upgrading older daemons requires a restart, which clears their in-memory telemetry. This PR has not been deployed to production.

The span-v2 handling from Spotlight #1372 is adapted to Toolkit's viewer model, including supported-container validation, typed HTTP attributes, and late segment naming. Raw payloads remain available.

Validation: 278 viewer tests and all 27 real Local CLI process E2E tests pass. Root typecheck and lint pass. Known unrelated local failures are musl installer detection, the DerivedData scan timeout, and an existing issue-link response-cache race under coverage (11,399 CLI unit tests pass). The cache failure also reproduces on the pre-UI commit; its 63-test file passes without coverage. These local gate exceptions were explicitly approved; the cache implementation is unchanged. Regressions cover permission boundaries, confirmed deletion/cancellation, finite replay, frozen expiry, receiver switching, independent filters, span navigation/focus, resizing, and repeated parent refreshes. The Local workflow also runs npm/native process E2E on Linux, macOS, and Windows.

Location	Screenshot
Local › Capture onboarding
Local › Session picker, capturing and saved
Local › Events, request inspector
Local › Logs, structured details
Local › Traces, selected span
Local › Traces, narrow viewport
Local › Saved capture, empty traces
Local › Search this session, explicit view filter
Local › Switch receiver
Local › Capture actions, delete confirmation
Local › Settings, narrow viewport

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-local	Ready	Preview	Oct 26, 2026 1:39pm UTC