Skip to main content
The features on this page are turned on per organization while we finish them. If one isn’t on for your organization yet, ask for it from the console, or ask your Puggy contact. Everything else in these docs is available to every organization.

​
Request early access

Automation and Retests stay visible in the console even before they’re on for your organization. Instead of the feature, you see a short explanation of what it does and a Request early access button.
  • Automation: choose Automation in the sidebar.
  • Retests: open a session and choose the Retests tab in the right panel.
Choose Request early access. The request is for your whole organization, so one person asking is enough, and asking again doesn’t send a second request. The button is replaced by Requested, and everyone in your organization sees the same. The Puggy team gets an email with your organization and who asked, and replies to that person once the feature is on. Retests run as automation runs, so turning on Retests turns on Automation too. When a feature is on, the page shows it as usual the next time you open it.
Video clips can’t be requested from the console yet. Ask your Puggy contact.

​
Video clips

Keep just the part of a long recording that matters.
  • On the session detail page, choose Save a clip and pick Last 30 seconds, Last minute, Last 2 minutes, or Last 5 minutes from Save the end of the recording.
  • Clips appear in the version strip above the player when they’re ready.
  • Share a clip on its own with a public video link.

​
Retest

Check whether a bug is really fixed by replaying the recorded session against your fix.
  1. Save a bug report for the session.
  2. Open the Retests tab in the right panel and choose Retest.
  3. Enter the URL of the deployed fix, then Review and start.
  4. Puggy replays the recording and an AI verifier gives a verdict: Fixed, Still failing, or Inconclusive.
Coding agents can start and read retests through the MCP server with an API key that has the automation:read and automation:write scopes.

​
Automation

Run test cases against your app with an AI agent.
  • Start a run from Automation in the sidebar with your app’s URL, and optionally a project and a test account.
  • Write test cases with a name, instructions, and acceptance criteria, or import them from a CSV or Excel file with Test Case Name and Test Steps columns.
  • Watch the agent work step by step with screenshots.
  • Each case gets a verdict: passed, failed, partial, or inconclusive. Download an HTML report and an evidence bundle when the run finishes.