> 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/testvibe-api/api-reference/runs/run_feature.md).

# run\_feature

Dispatch a test run for a feature. Returns the `runId` immediately; the sandbox executes in the background (typically \~30 s).

{% hint style="warning" %}
The feature must have status **`generated`** — anything else is rejected with `409 conflict`.
{% endhint %}

## Request

```
POST /api/v1/ops/projects/{project}/features/{feature}/run
```

| Parameter | In   | Type   | Required | Description                                                                                                                           |
| --------- | ---- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| `project` | path | string | yes      | The project's public id.                                                                                                              |
| `feature` | path | string | yes      | Feature id or name.                                                                                                                   |
| `config`  | body | string | no       | Playwright configuration name (default `Default` — see [`list_configs`](/testvibe-api/api-reference/configurations/list_configs.md)). |
| `siteUrl` | body | string | no       | Test site URL override.                                                                                                               |

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X POST -H "Authorization: Bearer $TESTVIBE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"config": "Mobile"}' \
  "$TESTVIBE_SERVER/api/v1/ops/projects/$PROJECT/features/12/run"
```

{% endtab %}

{% tab title="CLI" %}

```bash
testvibe run "Login Functionality" --config Mobile --wait
```

{% endtab %}

{% tab title="MCP" %}
Tool **`run_feature`** — `{ "feature": "Login Functionality", "config": "Mobile" }`. Follow with `wait_for_run`.
{% endtab %}
{% endtabs %}

## Response

`202 Accepted`

```json
{ "runId": 214, "featureId": 12 }
```

Poll [`get_run`](/testvibe-api/api-reference/runs/get_run.md) (or use [`wait_for_run`](/testvibe-api/api-reference/runs/wait_for_run.md)) until `status` leaves `running`.

## Errors

| HTTP            | When                                                                  |
| --------------- | --------------------------------------------------------------------- |
| `404 not_found` | No such feature in this project.                                      |
| `409 conflict`  | Feature not runnable (not `generated`), or the dispatch was rejected. |


---

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

```
GET https://docs.testvibe.com/testvibe-api/api-reference/runs/run_feature.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.