# Set the default runner

The default runner tells TestVibe which GitHub Actions runner labels to use for repository workflows. This affects AI generation and test execution unless a workflow or run uses a more specific setting.

You set the default from the repository's Runners settings page.

## Open Runner Settings

1. Sign in to TestVibe.
2. Select the GitHub installation, team, and repository you want to configure.
3. Open **Settings**.
4. Open **Runners**.

The Runners page shows available GitHub Actions runners for the selected repository.

## Understand The Runner List

The runner list includes:

| Column         | What it means                                                                                                                       |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Default        | Shows which runner labels TestVibe currently uses by default.                                                                       |
| Runner         | The runner name or runner option.                                                                                                   |
| Runs-on labels | The labels GitHub uses to select the runner.                                                                                        |
| Type           | Whether the runner is standard hosted, repository self-hosted, organization self-hosted, organization hosted, or saved in settings. |
| Status         | Whether TestVibe can see the runner as online, offline, active, or unavailable.                                                     |

If custom runner details are limited, your GitHub organization may restrict which runner metadata TestVibe can read. An organization admin can confirm runner access and labels.

## Set A Runner As Default

1. Find the runner or hosted runner label you want to use.
2. Review the labels in **Runs-on labels**.
3. Select **Set as default runner** for that row.
4. Wait for TestVibe to save the repository setting.

TestVibe stores the setting in your repository's TestVibe settings file, so the project keeps using the selected runner for future workflows.

## Refresh Or Create Runners

Use **Refresh runners** when a new runner was recently added in GitHub and does not appear yet.

Use **Create new runner** when you need to add a GitHub Actions runner to the selected repository. TestVibe opens GitHub's runner setup page for the repository. You may need repository admin permissions to create or configure runners in GitHub.

GitHub's [Adding self-hosted runners](https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/add-runners) page explains the GitHub-side setup flow. If your organization manages runner groups, see [Managing access to self-hosted runners using groups](https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/manage-access).

## After Changing The Default

Run a small test to confirm:

| What to verify        | Expected result                                                        |
| --------------------- | ---------------------------------------------------------------------- |
| The workflow starts   | The run should leave queued state once a matching runner is available. |
| The target site opens | The runner can reach your site URL.                                    |
| Evidence is returned  | Screenshots, videos, traces, and status updates appear in TestVibe.    |

If the workflow stays queued, see [Troubleshoot runners](/runners/troubleshooting-runners.md).

For the GitHub workflow syntax behind the selected labels, see [Choosing the runner for a job](https://docs.github.com/en/actions/how-tos/write-workflows/choose-where-workflows-run/choose-the-runner-for-a-job).


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.