# Missing secrets

Secrets are encrypted values that workflows can use without showing them in the TestVibe UI or GitHub logs. AI generation, login steps, staging credentials, and private test data often depend on secrets.

## Common Missing Secrets

| Secret                          | Common use                                                |
| ------------------------------- | --------------------------------------------------------- |
| `OPENAI_API_KEY`                | OpenAI or Codex-powered generation.                       |
| `ANTHROPIC_API_KEY`             | Anthropic or Claude-powered generation.                   |
| Test username or password       | Signing in to the app under test.                         |
| API token                       | Calling a backend or setting up test data.                |
| Environment URL or tenant value | Targeting the right staging, QA, or customer environment. |

Your team may use different names. The workflow, generated test, or failure message usually tells you which secret is missing.

## Symptoms

| Symptom                                  | What it usually means                                                    |
| ---------------------------------------- | ------------------------------------------------------------------------ |
| Generation stops before producing output | The selected AI provider key is missing or invalid.                      |
| Run fails during login                   | Test credentials are missing, wrong, or unavailable to the runner.       |
| Workflow says a secret is not found      | The secret name is missing at repository or organization scope.          |
| A value appears as empty in the workflow | The secret exists in the wrong repository, organization, or environment. |

## Add Or Replace A Secret

1. Open **Settings** in TestVibe.
2. Go to the repository **Secrets** or **API keys** area.
3. Add the secret name expected by the workflow or generated test.
4. Paste the value.
5. Save the setting.
6. Re-run generation or the test run that failed.

For the full setup flow, see [Add API keys and secrets](/workspace/add-api-keys-and-secrets.md).

## Important Notes

* Secret values are hidden after saving.
* If a secret value changed, replace it and run again.
* Organization-level secrets may need to be granted to the selected repository.
* GitHub Actions only receives secrets that belong to the repository, organization, or environment used by the workflow.


---

# 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/troubleshooting/missing-secrets.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.