# Browser checks: test your live app with Aria

> Open your live app in Aria's browser, check a flow in plain words, save it, run it on a schedule, sign in with test accounts, and fix what fails.

Source: https://getaria.cloud/docs/checks (updated 1 November 2026)

Aria can open your live app in a real browser, try what you ask and show every step with a picture. Open a project and go to **Browser**, pick a site, and say what to check. You can save a check, run it on a schedule, and hand what it finds to Aria AI to fix.

## How do I open my app live?

**Browser** shows a tile for each site, and **Try the API** for each API. Choose **Open live** on a site. You can click and type in it, and switch between **Desktop**, **Tablet** and **Phone**.

The session stays signed in for this project, and it ends after 15 quiet minutes. On the Mac you can also run the page on this Mac, in WebKit. Aria cannot drive that one, so use **Live with Aria** when you want Aria to work in it.

## How do I check something?

1. Open a site and choose **Check something**.
2. Say it in your own words, such as "Sign in as Shopper, add a shirt to the cart, pay".
3. Choose **Check it**.

Aria AI plans the steps. Each step shows with a picture you can open. The verdict is **Looks right**, **Works, with errors** or **Something failed**. Console errors, failed requests and errors in your server logs while it ran are listed under **Problems** in plain words, each with what it means.

Choose **Watch Aria do it** to see it work in the page. You can take over at any time, and hand back when you are done.

## What can I do with what it finds?

- **Fix with Aria** asks Aria AI to look into it. Any change waits for your approval.
- **Copy a prompt** gives you words for your own coding agent.
- **Looks good** and **Something's wrong** record what you think of the result.
- **Save as a check** keeps it to run again.

**History** lists earlier checks, with their steps.

## How do I run a check on a schedule?

Choose **Create an automation**. Pick what to check: that a site loads, a saved check, or something new in your words. Then choose how often: every 15 minutes, every hour or every day.

Aria runs it in a real browser. A failure shows in Activity and **Needs you**, and it emails your team. You can pause, resume or delete an automation, and see how its recent runs went.

## How do checks sign in?

Add test accounts under **AI & MCP**, then **AI access**. Each has a label, a sign-in page and a login. Aria keeps the password encrypted, and the AI never sees it. If your app has Supabase, Aria can make the user for you, confirmed, and deletes it when you remove the account.

Aria reads your database's roles and suggests which kind of user a check needs. Choose **Sign in as** when you run a check.

## How does Aria AI get to run checks?

Under **AI & MCP**, then **AI access**, the **Run browser checks** switch lets it open the live app and try what changed, after a push or when you ask. See [Aria AI](https://getaria.cloud/docs/aria-ai).

## How do I check code before it goes out?

On the Mac, **Files** sits your folder beside GitHub and your server, and shows what differs. **Check & push** looks at secrets, dependencies and the code, then pushes with your own git. On the web, Files shows GitHub and your server, and points you to the Mac app for pushing.

Next: [Backups on Aria: schedule, restore and your own key](https://getaria.cloud/docs/backups)