> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/runners/set-default-runner.md).

# Set a Project's Execution Target

Each project runs on one execution target: the default **cloud** sandboxes, a **private runner** you host, or a **tunneled** sandbox that reaches a private app. New projects start on cloud; you only change this when the app under test isn't reachable from the public internet.

## Cloud (default)

Projects testing public or staging URLs need no configuration — every run gets an [isolated cloud sandbox](/runners/what-are-runners.md) automatically. There is nothing to install or select.

## Tunneled: pin a device

When a project runs in **tunneled** mode, the cloud sandbox routes through a tunnel device. A project uses its pinned device; if no device is pinned, it falls back to the **Default** device. You manage devices from **Settings → Tunnels**.

### Open the Tunnels panel

1. Sign in to TestVibe.
2. Select **Settings** from the navigation rail.
3. Select **Tunnels** under Workspace.

The panel lists every machine that has connected with the `tvtunnel` agent, with its online status.

### Set the Default device

1. Find the device you want most projects to use.
2. Mark it as **Default**.

Any tunneled project without a pinned device now routes through this device.

### Pin a device for one project

If a project's app lives in a different network than the Default device:

1. Open the project's device setting in **Settings → Tunnels**.
2. Pin the device that can reach that project's app.

Pinned projects always use their pinned device; everything else falls back to the Default device.

## Private runner

When a project runs on a **private runner**, runs are picked up by the runner you host inside your firewall — there is no device to pin. Make sure a runner is online for the project before starting a run. See [Private runners](/runners/self-hosted-runners.md).

## After Changing Targets

Run one small test to confirm the new target works:

| What to verify           | Expected result                                                                      |
| ------------------------ | ------------------------------------------------------------------------------------ |
| The run leaves preparing | A sandbox or private runner picks up the job and starts executing.                   |
| The target site opens    | The run reaches your app (directly, through the tunnel, or from the private runner). |
| Evidence is returned     | Screenshots, videos, and traces appear in the Runs section.                          |

If the run cannot reach the site or stays stuck, see [Troubleshoot execution](/runners/troubleshooting-runners.md).

## Related Help

* [Choose an execution target](/runners/choose-a-runner.md)
* [Private runners](/runners/self-hosted-runners.md)
* [Tunnel devices in Settings](/account-settings/tunnel-devices.md)
* [API keys](/account-settings/api-keys.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/runners/set-default-runner.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.