Pick.
Open your staging page. Probe finds the Jira ticket for it, or paste any key.
Probe is a Chrome extension for Jira teams. Open any ticket, run it on the real page, and see what breaks.
For developers, QA, designers and product managers.
KB-1432 lands in Ready for review. The developer thinks QA will look. QA thinks design did. Everyone assumes someone else checked it.
Four people open the same page and test four different ways. A screenshot in Slack. A note in Jira. A "works for me". A design gap spotted by eye.
The clutter clears. Probe lands on the page and opens in a Chrome side panel. It already knows which ticket you are on.
Probe reads the acceptance criteria in Jira, the code changes in the pull request and the Figma prototype. Three sources become one list of steps.
A cursor clicks, types and checks on the real page. Steps tick green. When one fails, a red pin drops on the page with a screenshot, the console error and the failed network call.
Amaka reads the clean report. Kemi sees the page against the Figma frame. Tunde sees 12 of 12 checks passed. Dayo fixes the pinned bug and runs it again.
All of it happens in a Chrome side panel, next to the page you already have open.
Open your staging page. Probe finds the Jira ticket for it, or paste any key.
It reads the acceptance criteria, the code changes and the Figma prototype, then writes plain steps.
It clicks, types and checks on the real page while you watch.
Anything that fails gets a pin with a screenshot, the console and the network call.
Point at the report to see what each part does.
Probe works beside your QA team, not instead of them. Everyone on the ticket gets the same way to check.
Tokens and AI keys are stored locally in your browser. There is no Probe account to hold them.
Probe acts on that page and nothing else.
Values typed into fields are never sent to a model.
No. Probe gives your QA team reports with steps and logs, so they start from evidence instead of a blank page. And it gives everyone else on the ticket a way to check too.
No. Probe is a Chrome extension. It talks to your tools and your AI provider with your own keys, and there is no Probe account or server in the middle.
Only what it needs to write and run the checks: the ticket, the code changes, the Figma frames and the structure of the page you opened. Values typed into fields are never sent to a model.
Any web page you open in Chrome, such as your staging or production app. It only acts on the page you opened.
Yes, if your provider offers one. Probe works with Claude, OpenAI and Gemini keys. Free tiers have lower limits, so long runs may take longer.
Probe still writes checks from the ticket and the code changes, and it can still compare the page to a Figma frame. A prototype flow simply adds more steps.