get_feature
Read one feature in full, including its Gherkin source.
Request
GET /api/v1/ops/projects/{project}/features/{feature}
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
project | path | string | yes | The project's public id. |
feature | path | string | yes | Feature id or name. |
- cURL
- CLI
- MCP
curl -H "Authorization: Bearer $TESTVIBE_API_KEY" \
"$TESTVIBE_SERVER/api/v1/ops/projects/$PROJECT/features/12"
testvibe features show "Login Functionality"
Tool get_feature — { "feature": "Login Functionality" }.
Response
{
"id": 12,
"name": "Login Functionality",
"kind": "feature",
"status": "generated",
"gherkin": "Feature: Login Functionality\n Scenario: Valid user signs in\n Given I am on the login page\n When I sign in with valid credentials\n Then I see the inventory page\n",
"rationale": null,
"updatedUtc": "2026-06-10T14:32:07Z"
}
rationale is set on suggestion features — the exploration agent's reasoning for proposing them.
Errors
| HTTP | When |
|---|---|
404 not_found | No feature named or numbered like that in this project. |