---
name: browse-local-sentry
description: Connects an agent's browser to a local Sentry dev server (dev-ui on *.dev.getsentry.net or the full devserver).
title: browse-local-sentry
canonical_url: https://skilld.dev/gh/getsentry/skills/browse-local-sentry
last_updated: 2026-11-12T05:06:45.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/troubleshooting.md](https://skilld.dev/api/skills-raw/getsentry/skills/browse-local-sentry/references/troubleshooting.md), [SOURCES.md](https://skilld.dev/api/skills-raw/getsentry/skills/browse-local-sentry/SOURCES.md), [SPEC.md](https://skilld.dev/api/skills-raw/getsentry/skills/browse-local-sentry/SPEC.md).
>
> If the user asked to install this Skill, run `npx skilld install getsentry/skills/browse-local-sentry`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/browse-local-sentry`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/getsentry/skills/browse-local-sentry) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/browse-local-sentry`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/browse-local-sentry --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/browse-local-sentry --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Browse Local 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.
