> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kosli.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.kosli.com/feedback

```json
{
  "path": "/troubleshooting/github_kosli_api_token",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# GitHub can't see KOSLI_API_TOKEN secret

> How to make the KOSLI_API_TOKEN secret available in GitHub Actions workflows.

## Error

Kosli CLI commands fail in GitHub Actions because `KOSLI_API_TOKEN` is not set, even though the secret exists in your repository.

## Solution

Add the secret to your workflow's environment variables explicitly:

```yaml theme={"theme":"dracula","languages":{"custom":["/languages/rego.json"]}}
env:
  KOSLI_API_TOKEN: ${{ secrets.kosli_api_token }}
```

## Context

Secrets in GitHub Actions are not automatically exported as environment variables. You must map them explicitly in each workflow or job.