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

# Glossary

* **API key**. A secret that lets the CLI or an agent act in one project without a browser sign-in. It has a name, an expiry and can be revoked.
* **App**. The product under test in a project: a web app, or an Android app you upload builds of.
* **Build**. An app file you upload for a phone to run, such as an APK.
* **CLI**. The talotrace command on your computer. It signs you in, serves your local ports, runs a live phone and starts runs.
* **Evidence**. What a run recorded: steps, requests, console lines and snapshots. It is kept for a limited time.
* **Live phone**. A cloud phone that runs your working tree, so you can try a change before you build it.
* **MCP server**. The TaloTrace tools your coding agent calls over the Model Context Protocol.
* **Problem**. A refusal with a stable code, a status, what it means and the next step. The problems page lists every code.
* **Profile**. The release channel the CLI follows: dev, stg or latest. Each has its own package and API.
* **Project**. The unit of testing. It holds apps, scenarios, test plans, test data and runs.
* **Request card**. A question TaloTrace opens for you during discovery or a run, which you or your agent answers.
* **Run**. One execution of scenarios against a build or a live phone, with a verdict and evidence.
* **Scenario**. One test: a goal and the steps to reach it.
* **Test data**. The logins, files and records your tests use. Secrets are sealed and never read back.
* **Test plan**. A named group of scenarios you run together.
* **Tunnel**. The connection that serves a port on your computer to TaloTrace runs while the CLI is open.