Browse Local Sentry Sources
| Source | Contribution | Confidence |
|---|---|---|
getsentry/sentry rsbuild.config.ts |
dev-ui loads config/localhost.pem when present, else a self-signed basic-ssl certificate, both at config load; proxies /api/ to production sentry.io; does not proxy /identity/ or /auth/ |
High, read from source |
getsentry/sentry package.json mkcert-localhost script |
Cert command and SANs (dev.getsentry.net, *.dev.getsentry.net); writes the files before mkcert -install, so a file can exist without a trusted CA |
High, read from source |
FiloSottile/mkcert cert.go |
Leaf certificates expire 2 years and 3 months after issue | High, read from source |
getsentry/sentry .gitignore |
/config/*.pem is ignored, so certs are per clone |
High, read from source |
getsentry/sentry scripts/dev-ui-server.ts |
Port starts at SENTRY_WEBPACK_PROXY_PORT or 7999 and searches 10 ports upward |
High, read from source |
getsentry/sentry AGENTS.md, devserver.py, runner/commands/createuser.py |
Devserver is plain HTTP on 8000 with local accounts; .artifacts/dev.log; createuser flags for non-interactive use |
High, read from source |
chrome-devtools-mcp 1.12.0 browser-options.js, ServerConfig.js, BrowserManager.js |
--autoConnect needs Chrome 144+ and chrome://inspect/#remote-debugging; channel choices; without it the server launches a dedicated profile under its cache directory |
High, read from source |
chrome-devtools-mcp docs/troubleshooting.md, docs/advanced-usage.md, docs/client-configurations.md, .claude-plugin/plugin.json |
macOS Files & Folders fix, timeout causes including frozen tabs, default-profile rule, --browser-url needs a separate profile, Codex command, plugin args pinned without --autoConnect |
High, upstream docs |
| Sentry Cookie Sync 1.6.1 extension source | Copies sentry.io session, su, staff, sc, and sudo cookies to dev.getsentry.net, only for orgs seen in open :7999 dev-ui or *.sentry.io tabs |
High, read from source |
getsentry/sentry setup-dev skill |
Says Cookie Sync is required for the full devserver; conflicts with the extension's HTTPS-only host permissions, so not adopted | Rejected |
| Maintainer's working setup | Okta device trust rejects fresh profiles; nvm PATH gotcha |
Medium, observed in practice |
Decisions
- Adopted: probe trust with curl, then route with
openssl verifyof the served certificate against the local mkcert CA. curl's wording does not tell the fallback from an untrusted CA, and the issuer string cannot tell two mkcert CAs of the same user apart. - Adopted: keep the checks and safety rules in
SKILL.md, and the failure procedures inreferences/troubleshooting.md, since a working setup needs only the checks. - Adopted: run Step 2 outside shell sandboxes, which hide the keychain from curl and may block openssl's direct connection.
- Adopted: change MCP config only with the user's approval, since it persists, and pin the server version, since it controls a signed-in browser.
- Adopted: detect a failed openssl capture with
[ -s "$f" ], since LibreSSL and OpenSSL word the failure differently. - Adopted: ask for the org instead of using the bare
dev.getsentry.nethost, which can land in an arbitrary org under a staff session. - Adopted: the agent may create a local devserver account, since it only touches the local database.
- Rejected: a runtime pointer from
pr-screenshots, since skills must not require each other by name. This skill's description triggers on the same certificate and login errors.
Validation Log
- 2026-10-22: Steps 3 and 4 run against a live dev-ui.
list_pageslisted the user's tabs;/api/client-config/returnedisAuthenticated: trueover a secure context, on both the org subdomain and the bare host. - 2026-10-22: With a trusted certificate, the service-worker SSL console message did not appear, so it is treated as a sign of an untrusted certificate.
- 2026-10-22: A fresh headless Chrome profile loaded dev-ui without certificate errors, confirming the mkcert CA is trusted machine-wide.
- 2026-10-22:
/usr/bin/curlreturned 200 against the trusted dev-ui. - 2026-10-22: curl's message for dev-ui's fallback certificate differed between
tests: "unable to get local issuer certificate" for a cert generated by
@rsbuild/plugin-basic-ssl, "self signed certificate" for a hand-madeCN=localhostcert. An untrusted mkcert CA gives the former too. - 2026-10-22:
openssl verifyagainst$(mkcert -CAROOT)/rootCA.pemreturnedOKfor the live dev-ui's certificate and failed for a self-signedCN=localhostcertificate and for one from a scratch mkcert CA with the same issuer string. Expiry readscertificate has expiredon both OpenSSL 4 and macOS LibreSSL. An unreachable port prints different errors on each. - 2026-10-22:
@anthropic-ai/sandbox-runtime0.0.81's default config blocks the curl probe to loopback with "CONNECT tunnel failed, response 403". With loopback allowed, sandboxed/usr/bin/curlrejects the trusted certificate because the sandbox deniescom.apple.trustd.agent, while openssl still connects and verifiesOK. mkcert then reports the CA as already installed, which theOKrow uses to detect the sandbox.
Gaps
- Full devserver sign-in path not run end to end.
- Wrong-channel and macOS Files & Folders fixes taken from upstream docs, not reproduced.
Changelog
- 2026-10-22: Created.