Skip to content

Your project'sQA.

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.

Someone checked it. Probably.

KB-1432 lands in Ready for review. The developer thinks QA will look. QA thinks design did. Everyone assumes someone else checked it.

Everyone checks. Nobody checks the same thing.

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.

Meet your project's QA.

The clutter clears. Probe lands on the page and opens in a Chrome side panel. It already knows which ticket you are on.

It writes the checks from what your team already wrote.

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.

It runs them. And pins what breaks, right where it breaks.

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.

One check, the whole team on the same page.

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.

Pick, read, run, pin.

All of it happens in a Chrome side panel, next to the page you already have open.

Pick.

Open your staging page. Probe finds the Jira ticket for it, or paste any key.

KB-1432 Transfer amount validationDetected
KB-1418 Card freeze toggle
KB-1407 Beneficiary search

Read.

It reads the acceptance criteria, the code changes and the Figma prototype, then writes plain steps.

Ticket
Code changes
Figma prototype

Run.

It clicks, types and checks on the real page while you watch.

₦ -500

Pin.

Anything that fails gets a pin with a screenshot, the console and the network call.

₦ -500
console RangeError: amount must be > 0
network POST /api/transfers 500

Everything a good check needs.

Point at the report to see what each part does.

Built for the whole team, not one desk.

Probe works beside your QA team, not instead of them. Everyone on the ticket gets the same way to check.

  • DevelopersCheck your ticket before it moves on.
  • QA engineersStart from a real report, not a blank page.
  • DesignersSee where the build misses the design.
  • Product managersKnow a ticket works before release.

Works with the tools your team already uses. Bring your own AI key.

  • Jira
  • Figma
  • Bitbucket
  • GitHub
  • Claude
  • OpenAI
  • Gemini

Private by default.

Your keys stay on your machine.

Tokens and AI keys are stored locally in your browser. There is no Probe account to hold them.

It only touches the page you opened.

Probe acts on that page and nothing else.

Typed values stay private.

Values typed into fields are never sent to a model.

Good questions.

Does it replace our QA team?

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.

Does it need an account or a backend?

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.

What does it send to the AI?

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.

Which sites does it work on?

Any web page you open in Chrome, such as your staging or production app. It only acts on the page you opened.

Can I use a free AI key?

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.

What if my Figma has no prototype?

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.

Start free.

Free

For anyone trying Probe on their own tickets. Bring your own AI key.

Add to Chrome

Team

For product teams checking tickets together. Pricing to be announced.

Talk to us about Team

Check your nextticket with Probe.

Add to ChromeEarly access. We email you the install link.