# Where tests run

> Choose between running tests on Cloud machines from Testsigma Lab and on your own machines through the Arcus Agent.

Arcus runs automated tests in one of two places: **Cloud**, on browsers, operating systems, and real devices from Testsigma Lab, or **Local Agent**, on a machine running the Arcus Agent, such as your own computer. A run configuration sets which one a test run uses. In a Copilot session, you choose it under **Where to run**, where the option is called **My local machine**.

| | Cloud | Local Agent |
|---|---|---|
| Setup | Nothing to install | The [Arcus Agent](https://testsigma.com/docs/arcus/v2/get-started/installation/arcus-agent/) installed, running, and signed in |
| Web | Browsers and operating systems from Testsigma Lab | The browsers installed on the machine |
| Mobile | Real devices from Testsigma Lab | Phones and emulators connected to the machine |
| Windows desktop apps | Not available | A Windows computer |
| Apps that aren't public, such as a local build | Not reachable | Reachable from the machine |

![The Copilot configuration, with Saved configuration, What you are authoring, Where to run, and Test machine outlined](https://s3.amazonaws.com/static-docs.testsigma.com/new/arcus/2026-11/copilot_config_where_to_run.webp)

## Which machines run test plans

A machine runs test runs and test plans only when its agent profile is used for execution:

- **Authoring**: Copilot sessions only. **My Local Device** says "This device is for authoring, so it doesn't run test plans."
- **Authoring + Execution**: a person's own machine that also runs test plans.
- **Execution only**: a machine set aside for runs, such as a CI runner or a shared lab machine.

![The Active sessions tab of My Local Device for an authoring machine, with the Default and Authoring chips, the tab, the Test plans and Copilot runs counts, and the message This device is for authoring, so it doesn't run test plans outlined](https://s3.amazonaws.com/static-docs.testsigma.com/new/arcus/2026-11/arcus_agent_active_sessions.webp)

Every machine starts on the **Default** profile, which is used for authoring. An admin changes what a machine is used for in **Settings** > **Profiles and agents**. See [Agent profiles](https://testsigma.com/docs/arcus/v2/settings/organization/agent-profiles/).

A profile used for execution is **Global**, shared with the account, or **Local**, kept to the person who set up the machine.

## Sessions and queues

Cloud and Local Agent each have their own number of parallel sessions and minutes, and both share one queue. When every parallel on a side is busy, a test run waits in the queue and starts when a slot frees. See [Session limits and queues](https://testsigma.com/docs/arcus/v2/run-tests/session-limits-and-queues/). To run a test run's cases at once across your parallels, see [Parallel settings](https://testsigma.com/docs/arcus/v2/run-tests/run-configurations/#parallel-settings).
