Failures across browsers
Tom Reilly, QA lead at Northwind, asked which sessions had failed in last night's build. Memtro listed the failed sessions with the failure reason, operating system and browser of each, and a link to each on the dashboard.
BrowserStack + Memtro
Which sessions failed in last night's BrowserStack build, and on which browsers?
BrowserStack shows you your Automate plan and parallel sessions in use. Memtro reads projects, builds and sessions with status, failure reason, platform and duration. It also reads Test Management projects, test cases, test runs with progress, and the results recorded in a run. When asked and granted, it can mark an Automate session passed or failed, and rename or delete a session or build. It can create, clone, close or delete a test run, record a test result, and create a test case. The access key has its user's own access, so Memtro reaches only what that user can.
In Memtro
What you can do with BrowserStack in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right BrowserStack tool, reads what it needs, and answers with the source cited.
What it does
- 01Reads the Automate plan with parallel sessions running and allowed, and sessions queued against the queue limit.
- 02Lists builds with status and duration, and each build's sessions with failure reason, platform and duration.
- 03Lists Test Management projects, test cases with priority and status, test runs with progress, and the results recorded in a run.
- 04When asked and granted, marks a session passed or failed with a reason, which shows on the dashboard, or renames a session or build.
- 05When asked and granted, deletes a session or a whole build permanently, with their videos and logs.
- 06When asked and granted, creates, clones, closes or deletes a test run, records a test result, or creates a test case.
Acts when asked
When you ask it to
These tools change something in BrowserStack. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Mark an Automate session passed or failed
- 02Rename an Automate session
- 03Delete an Automate session
- 04Rename an Automate build
- 05Delete an Automate build and its sessions
- 06Create a test run
- 07Clone a test run
- 08Close a test run
- 09Delete a test run
- 10Record a test result in a test run
- 11Create a test case
In practice
Ask it like you would a colleague
Once BrowserStack is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
BrowserStack + Memtro
Which sessions failed in last night's build, and why?
How many parallel sessions are we using right now?
How far along is the regression test run?
Which test cases failed in the release candidate run?
Clone the regression run with only the failed test cases.
Re-running the failures
Priya Sharma, test manager at BigCo, asked Memtro to set up a retest of everything that failed in the release candidate run. With the action granted, Memtro cloned the run with only the failed test cases, ready for her team in Test Management.
Teams
Where it fits
The teams that lean on BrowserStack most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in BrowserStack is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Work managementBrowserStack with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementBrowserStack with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementBrowserStack with LinearIssues, projects and teams, synced hourly into memory.
- SupportBrowserStack with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportBrowserStack with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportBrowserStack with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisBrowserStack with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisBrowserStack with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisBrowserStack with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withUsername and access key
- 1
In BrowserStack, open Account → Settings and copy the API username shown beside the access key, not your login email.
- 2
Open Connections → BrowserStack in Memtro and paste the Username and Access key. The same key serves Automate and Test Management.
- 3
An administrator grants actions such as delete a build or record a test result by name to the teams that may use them.
- 4
Ask which sessions failed in last night's build.
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The BrowserStack tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in BrowserStack?+
Only when you ask, and only what it has been granted: mark an Automate session passed or failed; rename an Automate session; delete an Automate session; rename an Automate build; delete an Automate build and its sessions; create a test run; clone a test run; close a test run; delete a test run; record a test result in a test run; create a test case. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a BrowserStack connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my BrowserStack data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect BrowserStack?+
Username and access key. In BrowserStack, open Account → Settings and copy the API username shown beside the access key, not your login email.
Connect BrowserStack in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.