Browse Local Sentry

From the author

Connects an agent's browser to a local Sentry dev server (dev-ui on *.dev.getsentry.net or the full devserver).

— the description by Sentry

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured workflow for connecting an agent's browser session to a local Sentry development server. It distinguishes between the dev-ui (which interacts with production Sentry data using the user's authenticated session) and the full devserver (which uses a local database). The skill includes rigorous safety checks for certificate validation and browser authentication, ensuring that the agent operates within the user's existing Chrome profile without compromising security or session integrity.

What it does

Identifies and locates active local Sentry development servers.
Validates SSL certificates to ensure secure connections to local dev environments.
Integrates with the user's existing Chrome browser session for authenticated access.
Verifies authentication status via Sentry API endpoints.
Provides troubleshooting paths for common certificate and browser connectivity issues.
Ensures safe interaction by preventing unauthorized data modification in production-linked environments.

When to use it

When you need to test frontend changes against a live Sentry development server.
When the agent needs to perform browser-based QA on local Sentry builds.
When you encounter certificate errors or authentication failures while connecting to a local Sentry instance.
When you need to switch between production-linked dev-ui and local-database devserver environments.

Advantages

Maintains user session security by leveraging existing browser profiles.
Provides clear, actionable troubleshooting steps for common environment setup issues.
Prevents accidental data modification by enforcing strict operational rules.
Automates the complex process of port discovery and browser attachment.

Usage examples

“Connect to my local Sentry dev-ui.”: The agent will identify the running dev-ui port, verify the SSL certificate, attach to your active Chrome session, and confirm authentication.
“I am getting a certificate error when trying to browse my local Sentry instance.”: The agent will guide you through the troubleshooting steps, including verifying the local CA installation and checking the dev-ui certificate status.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/getsentry/browse-local-sentry/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip browse-local-sentry.zip -d .agents/skills

Documentation by Sentry

Server	URL	Data	Browser
dev-ui (`pnpm run dev-ui`)	`https://<org-slug>.dev.getsentry.net:<port>/`. Ask the user for the org if it is unknown.	Production sentry.io, as the user	The user's own Chrome, the only one with their session
Full devserver (`devservices serve`)	`http://dev.getsentry.net:8000/`	Local database	Any

Run every check in every session. Chrome updates, re-auth, and port changes undo earlier setup without warning. When a check fails, open the named section of references/troubleshooting.md.

Rules

dev-ui acts on production sentry.io as the user, including any staff or superuser session. Do not create, edit, or delete anything, and stay in the org the user named, unless the user approves the specific action. Use the full devserver for flows that change data.
Never bypass certificate warnings (thisisunsafe, --ignore-certificate-errors, --acceptInsecureCerts), log in to sentry.io yourself, or type the user's credentials.
Change the user's MCP config only with their approval.
In the user's own Chrome, open your own tabs with background: true, never isolatedContext, which has no session. Never navigate, reload, close, read, screenshot, run scripts in, or quote the user's tabs. Emulate viewports instead of resizing the window, and close your tabs when done.

Step 1: Find the Server

Use the URL the user gives. Otherwise never assume a port: dev-ui tries 10 ports upward from SENTRY_WEBPACK_PROXY_PORT (default 7999) and prints the one it took, and the devserver logs to .artifacts/dev.log. List listeners with lsof -nP -iTCP -sTCP:LISTEN and match one to its clone with lsof -a -p <pid> -d cwd.

Step 2: Check the Certificate (dev-ui Only)

Outside any shell sandbox, run curl -sS -o /dev/null https://dev.getsentry.net:<port>/ (on macOS, /usr/bin/curl, which reads the keychain). If it fails, see Certificate.

Step 3: Attach to the User's Chrome (dev-ui Only)

Call list_pages, or use another tool that already drives the user's signed-in Chrome. The browser is attached when it lists the user's own tabs. If not, see Chrome.

Step 4: Check Authentication

Open the server URL in a new tab and read /api/client-config/. Continue when isAuthenticated is true. If not, see Authentication.

After editing frontend source, wait for the rebuild, then reload with the cache bypassed. If the console shows "An SSL certificate error occurred when fetching the script.", the certificate is not trusted; return to Step 2.

When a Step Is Blocked

Stop and tell the user which step failed and the exact action they need to take. Do not substitute tests, stories, or reasoning for browser QA, and do not write "browser verification was blocked" into a PR description in place of doing it.

Files

ATTRIBUTION.mdAdded by AutoGineer862 B
LICENSELicence file added by AutoGineer10.5 KiB
SKILL.md3.0 KiB
SOURCES.md5.4 KiB
SPEC.md2.5 KiB
references/troubleshooting.md5.2 KiB

SKILL.md