Agentic testing

Share a run

A share link turns one finished run into a public report page that anyone with the link can open, with no Coldtea account and no sign-in. Use it to hand a result to someone outside the app: a designer, a customer, a teammate without access.

This is different from the GitHub-gated report used in PR reporting. That report checks that the viewer can read the bound repo. A share link skips that check: the link itself is the credential.

A share link is the run's report URL with a token on the end. Anyone who has the link can open the report, so treat the link like a secret and send it only to people who should see the run.

Minting a link is a deliberate act against one named run. Ask an agent to share a run and it hands back the public URL. See MCP and local API.

Once you issue a share link, you cannot take it back. Mint one only when you mean the run to stay openly reachable.

What the shared report shows

The public report shows the run's verdict, summary, steps, screenshots, target, and the recording. It shows nothing else: no credentials, no log files, and nothing about your Coldtea workspace. Screenshots and recordings load through short-lived links rather than public file locations.

Social card

A shared report carries a preview card for social and chat. When someone pastes the link into a tool that unfurls links, the card shows the run's title, its verdict summary, and how many steps passed. A link without the share token unfurls to nothing.

Runs and results

How to read one run: the statuses it moves through, the verdict or couldn't-run reason it ends on, and the evidence Matcha collected.

PR reporting

Bind a GitHub repo and Matcha runs against your changes, keeping one pull-request comment that summarizes the runs and links each report.

On this page

What a share link isThe link cannot be revokedWhat the shared report showsSocial cardRelated