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

# murmur setup forge

> Configure the GitHub credentials agents use to clone repositories, push commits, and create pull requests without rerunning setup.

Configures the GitHub token your agents act with. It uploads the token to your developer profile on the server, so every agent you start, from the CLI, MCP, or the dashboard, uses the same token. Use it to rotate a token or switch between your `gh` CLI token and a pasted one.

Uses your existing Murmur sign-in and tenant. If no home or repository configuration exists, it signs you in, saves your selected tenant under `~/.murmur/`, and continues configuring GitHub access. To select a different Murmur account, use [`murmur login`](https://docs.murmur.dev/cli/login) first.

## Synopsis

```bash theme={null}
murmur setup forge
```

This command is interactive and takes no positional arguments or configuration flags. Use `--help` for usage.

## Choose GitHub access

Choose which GitHub token agents act with:

| Choice | Behavior |
| - | - |
| **Keep the GitHub token your Murmur profile already holds** | Offered first, and the default, when your profile already holds a GitHub token. Leaves it untouched and uploads nothing. |
| **From gh CLI** | Uploads the current `gh auth token`. Agents act as your `gh` login. If `gh` is not authenticated during setup, the command runs `gh auth login`. |
| **Paste a token** | Paste a [personal access token](https://docs.murmur.dev/security/github-pat.md). Murmur validates it and uploads it. Agents act as the account that owns it. |

The token is a snapshot taken during setup: agents use the uploaded value until you run `murmur setup forge` again. A later `gh auth login` or `gh auth refresh` does not change it.

The account that owns the agent's GitHub token can differ from your Murmur login. For example, you can remain signed in to Murmur as yourself while giving agents a bot account's PAT. Pasting a PAT does not switch your `gh` CLI login.

The command preserves your other credentials, Git author settings, SSH keys, and signing configuration.

## Examples

### Rotate a pasted token

```bash theme={null}
murmur setup forge
```

Choose **Paste a token** and paste the replacement PAT. See [PAT permissions and SSO authorization](https://docs.murmur.dev/security/github-pat.md) before creating the replacement.

### Use your gh login

```bash theme={null}
murmur setup forge
```

Choose **From gh CLI**. Agents you start from then on use your current `gh` token.

## Related commands

* [`murmur setup`](https://docs.murmur.dev/cli/setup): list configuration subcommands
* [`murmur login`](https://docs.murmur.dev/cli/login): sign in to Murmur or select an account
* [GitHub personal access tokens](https://docs.murmur.dev/security/github-pat.md): create and rotate a PAT


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