Set a Project's Execution Target
Set a project's execution target — cloud, private runner, or tunneled — and pin a tunnel device per project.
Last updated
Was this helpful?
⌘Ctrlk
Set a project's execution target — cloud, private runner, or tunneled — and pin a tunnel device per project.
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.
Projects testing public or staging URLs need no configuration — every run gets an isolated cloud sandbox automatically. There is nothing to install or select.
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.
Sign in to TestVibe.
Select Settings from the navigation rail.
Select Tunnels under Workspace.
The panel lists every machine that has connected with the tvtunnel agent, with its online status.
Find the device you want most projects to use.
Mark it as Default.
Any tunneled project without a pinned device now routes through this device.
If a project's app lives in a different network than the Default device:
Open the project's device setting in Settings → Tunnels.
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.
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.
Run one small test to confirm the new target works:
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.
Last updated
Was this helpful?
Was this helpful?