> Call the `diagnose` tool first. Full index: /llms.txt. Errors: /reference/problems.

# Test a hosted URL

Use this path when your app is already deployed at a public HTTPS address, such as a staging site or a preview.

#### In the web app

1. Sign in at [app.talotrace.ai](https://app.talotrace.ai) and create a project. Choose a web app and enter its start URL.
2. If the app needs a login, add a test account under **Test data**. Use an account made for testing, never a real customer's.
3. Open the chat and say what you want to check, for example "Test sign-up and checkout". TaloTrace explores the app and proposes [scenarios](/concepts/scenarios-and-test-plans).
4. Open **Scenarios**, read each one and keep the ones that match what you want tested.
5. Start a run from the scenario or from a test plan. TaloTrace shows an [estimate](/concepts/credits) first.
6. Watch the run. When it ends, [read the run](/guides/read-a-run): the verdict, the failure with its cause and fix, the video and the evidence.

#### With your agent

1. Set up your agent once with [One-command setup](/install/setup-command).

2. Ask it to test your deployed address. It calls `diagnose`, finds or creates your project and app, and starts the run:

   ```text
   start_run(project_id, app_id, target={"kind": "web", "start_url": "https://staging.example.com/"}, selection, request_id)
   ```

3. Wait for the report. It names the run, the verdict, a link to watch the run and, on a failure, the cause. See [Runs](/reference/mcp/runs).

#### From a terminal

1. Sign in with tool access, then run the check against your address. Leave out `--ports`: an HTTPS page needs no tunnel.

   ```bash
   talotrace check --project <project id> --app <app id> --scenario <scenario id> --start-url https://staging.example.com/ --timeout 10m --evidence-dir ./evidence
   ```

2. The command waits for the verdict, writes `outcome.json` and any failure bundles to `./evidence`, and exits with a [code](/reference/cli/exit-codes) your pipeline can read. See [CLI commands](/reference/cli).

Questions that need your answer appear as [cards](/concepts/cards) in the **Inbox**. A run waits for a card only when it cannot go on without it.

To test an app that runs only on your laptop, use [Test localhost with Claude Code](/quickstart/web-local-claude-code) instead.