[SavioBS629]

Summary

Routes EU accounts to BrowserStack's EU hosts automatically. Nothing to configure: the server reads the account's region from BrowserStack auth, using the username and access key it already has.

• Local: the region is looked up once, before the server starts.
• Hosted: servers for the same account share one lookup (kept for an hour), and every tool call runs in its own account's region, so concurrent users on different regions don't affect each other.
• Other regions: IN accounts keep the default hosts for now (Test Management and capability discovery still probe for them).
• If the lookup fails: an account already looked up keeps its last known region. Otherwise, calls that need the region return an error asking the user to retry rather than guessing a host; Test Management still finds the account's region by probing. The lookup is retried after 5 seconds.

Routed

• Test Management (tools and tm capability)
• Automate and App Automate, including uploads, hubs, and the devicecontrol / mobiledevicecontrol capabilities
• Accessibility and App Accessibility (tools and the app_accessibility / web_accessibility capabilities)
• Test Reporting & Analytics, RCA, build insights, self-heal and AI test failure analysis (tools and tra capability)

Hosts resolve in one place (src/lib/regional-host.ts). Explicit CAPABILITY_REGISTRY_BASE_URL_*, BROWSERSTACK_AUTOMATION_BASE_URL and O11Y_TFA_RCA_BASE_URL overrides still win.

No telemetry is sent for EU and IN accounts, and submitFeedback isn't offered to them. While the region is unknown, telemetry sends only usage fields (no error text or free-text inputs) and submitFeedback declines.

For library users

BrowserStackMcpServer.create(config) looks up the region before building the server, so the tool list matches the account. new BrowserStackMcpServer(config) still routes every call by region, but lists tools as for a US account.

Not routed yet

• Regional hosts for IN accounts
• Percy, askBrowserStackAI and the loadtesting capability
• App Live upload
• Automate and App Automate dashboard links, and generated SDK config snippets

Testing

npm run build passes. Unit tests cover the region lookup (token parsing, one lookup per account, expiry, failure), per-call routing for concurrent accounts, each product's regional host, telemetry fields and submitFeedback. Verified end to end against an EU account: local stdio, and hosted with OAuth, AccessToken and browserstack-* header sign-in all reached the EU hosts directly.

Squash on merge.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Central YAML (base), Organization UI (inherited), Workspace UI (inherited); Enforced overrides: Organization
• Review profile: ASSERTIVE
• Plan: Enterprise
• Run ID: b4f2abc0-7ebf-4c35-ae5d-3437ebc9fef7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[sarve-shreyas]

Review of the GRR region routing. Inline comments cover lines in the diff; three issues are outside it:

1. AI-TFA / RCA collaboration tools are not routed (src/tools/tfa-rca-utils/constants.ts:6). submit-turn, trigger-report, build-failure-themes and tfa-rca-collaboration still get their host from O11Y_TFA_RCA_BASE_URL, which defaults to US api-automation.browserstack.com, and getRegionalHost never reaches them. With eu, the build data and turn text go to the US host and either fail with 401/404 or put GRR data in the US. The PR description says TRA/RCA are routed, so this looks like a gap.
2. Dashboard-link parsing is inconsistent (src/tools/accessiblity-utils/report-fetcher.ts:~207, app-report-fetcher.ts:654/660). manualReportIdFromDashboardLink / buildIdFromDashboardLink accept only the regional app-accessibility host, so a US link pasted under eu used to resolve and now doesn't. The automate.browserstack.com / APP_AUTOMATE_HOST checks still accept only US hostnames, so EU dashboard links are never recognised either. Accepting every known regional host would fix both.
3. Duplicated host-kind selection (src/lib/regional-host.ts:~177). automateApi and appAutomateApi point to the same table, and the sessionType === Automate ? ... : ... ternary is repeated in about 7 files (fetch-screenshots, video, selfheal, list-session-ids, resolve-hashed-build-id…). Some call sites also use getRegionalHost("automationApi") where getAutomationBaseUrl() exists. A single hostForSession(sessionType) helper would keep them from drifting.

[sarve-shreyas]

Re-reviewed the commits since my last review (24266f6…1efef0d, excluding the upstream/main merge).

Thanks. These are resolved:

• The us flag no longer disables the TM probe; the flag itself is gone and the region now comes from the account.
• The override check now compares origins (hostOverride).
• tm is in REGIONAL_HOSTS, and web_accessibility is now covered too.
• Multi-tenant: the region is looked up per account and scoped per call through AsyncLocalStorage.
• sessionApiHost() plus default host params remove the duplicated ternaries.
• TFA/RCA collaboration now routes through getO11yBaseUrl() → hostFor("automationApi", region). This was item 1 of my previous summary.
• I accept the decision to keep Percy, askBrowserStackAI, App Live upload, load testing and the US telemetry endpoint out of scope, since they're listed under "Not routed yet".

New, inline: an account whose region lookup fails is routed to US hosts and keeps feedback enabled, while telemetry treats it as restricted. There's also a question about how the region cache behaves in the hosted wrapper.

Still open from the last review (item 2, outside the diff): only the App Accessibility links were switched to isRegionalHostname. report-fetcher.ts:207 (automate.browserstack.com) and app-report-fetcher.ts:651 (APP_AUTOMATE_HOST) still accept only US hostnames, so EU/IN Automate and App Automate dashboard links still aren't recognised. If those dashboards have regional hosts, adding them to HOSTS and using isRegionalHostname would close this.

[sarve-shreyas]

@SavioBS629 I re-reviewed up to 1efef0d (#489 (review)). Most of the earlier points are resolved, thanks! Three new points:

1. Fail-open on lookup failure (region-context.ts:30): if the auth lookup fails or returns an unrecognised region, the account is unknown and calls route to US hosts for 30s. Telemetry treats the same case as restricted.
2. Feedback for unknown accounts (feedback-hint.ts:4): submitFeedback stays enabled for unknown accounts, which is inconsistent with telemetry.
3. Region cache in hosted mode (account-region.ts:21): could you confirm the hosted wrapper reuses one config object per tenant? Otherwise every call re-mints a token.

Also still open from last time: Automate and App Automate dashboard-link parsing (report-fetcher.ts:207, app-report-fetcher.ts:651) still accepts only US hostnames.

[sarve-shreyas]

Re-reviewed df5fef1…1851231.

Resolved from my last review:

• Fail-open on unknown region. assertRegionKnown() / routedRegion() now refuse with a retry message instead of falling back to US, TM still probes, and a 5s retry window fits the message.
• Feedback for unknown accounts. feedbackEnabled() now uses isRestrictedRegion.
• Region cache in hosted mode. It's keyed on a credential hash, bounded, and has a TTL, so servers built per request share one lookup.
• Region value casing. regionFromToken lowercases the value, so "EU" resolves.

New, inline: the known region is dropped when a refresh fails after the TTL, which now fails closed. IN accounts route to US, and the PR description doesn't say so. A startup-only nit on submitFeedback.

Still open (outside the diff): Automate and App Automate dashboard-link parsing (report-fetcher.ts:207, app-report-fetcher.ts:651) still accepts only US hostnames.

[SavioBS629]

On the Automate and App Automate dashboard-link parsing (report-fetcher.ts, app-report-fetcher.ts): keeping it out of this PR. Dashboard links are listed under "Not routed yet" and will follow once their regional hosts are confirmed.

[sarve-shreyas]

Re-reviewed 390c066. No new issues; everything from my earlier rounds is either fixed or explicitly deferred:

• Region kept on a failed refresh: accountRegion serves the last known region while a refresh runs and when it fails, and resets failedAt once a refresh succeeds. Only accounts that have never been looked up get the retry error.
• Startup with an unknown region: feedbackListed() keeps submitFeedback listed. The call check (feedbackEnabled()) and withFeedbackHint still decline or hide the hint while the region is unknown, so this is consistent.
• Deferred, as listed in the description under "Not routed yet": IN routing, Automate and App Automate dashboard links, and switching the hosted server to create().

Looks good from my side.

[sarve-shreyas]

Approving at 390c066. The deferred items (IN routing, Automate and App Automate dashboard links, and the hosted server switching to create()) are tracked under "Not routed yet".