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

# GitHub

> Give the Sazabi agent the GitHub CLI (gh) in its sandbox to interact with GitHub repositories, pull requests, and issues.

[All GitHub integration capabilities](https://docs.sazabi.com/catalogs/integrations/github.md)

## About

This CLI connection makes the GitHub CLI (`gh`) available in the Sazabi agent's sandbox. Connecting it authenticates the CLI with your `GH_TOKEN`; repository access through the GitHub App integration is separate and covers the agent's code-search tools. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.

## Prerequisites

* A Sazabi project.
* A GitHub token (`GH_TOKEN`) — either a fine-grained personal access token (PAT) or a GitHub App installation token with access to the repositories the agent needs to read or write.

## Set up in the dashboard

Configure the sandbox in the dashboard under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis).

**Step 1**

### Find GitHub in the catalog

In [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis), find GitHub under **Browse sandbox CLIs** and choose to connect it.

**Step 2**

### Provide credentials

Enter the required value: `GH_TOKEN` — a GitHub personal access token or App installation token with the scopes your agent needs (at minimum `repo` for repository access). Save to store it securely; Sazabi injects it into the sandbox when the agent runs.

## Set up with the CLI

You can also configure the GitHub CLI connection with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/sandbox-clis.md)).

```bash theme={"system"}
sazabi sandbox-clis connect github --env GH_TOKEN=<your-github-token>
```

To validate the credentials without saving, run the same command with `test` in place of `connect` (the test command also requires the `--env` flags).

## Verify

Ask the agent, in a thread, to run the `gh` CLI (a read-only or status command) and confirm it returns real output from your account. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated, recheck the credentials.

## Troubleshooting

**Command not found** — Confirm the GitHub CLI connection is enabled for the project under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis).

**Authentication fails** — Recheck the credential values; a rotated or revoked token must be re-entered under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis) or with `sazabi sandbox-clis connect github`.

## Further reading

> [card] [Working with the agent](https://docs.sazabi.com/guides/investigate/working-with-the-agent.md)
>
> Put the connected CLI to work in an investigation thread.

> [card] [Set up the sandbox](https://docs.sazabi.com/guides/investigate/sandbox.md)
>
> How the sandbox works and its security model.

> [card] [Sandbox CLIs](https://docs.sazabi.com/catalogs/sandbox-clis.md)
>
> Browse the catalog and connect more tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.