Skip to main content
GitHub is where your agents write code, open pull requests, and review changes. Titus uses it to ship PRs, Scout uses it to review them, and Juno monitors progress across the repo.

​
What You Need

A GitHub personal access token for each agent. Fine-grained tokens are recommended so you can scope permissions to specific repositories.
GitHub integration is optional but strongly recommended for engineering and QA agents. Without it, Titus can’t open PRs and Scout can’t review them.

​
Step 1: Generate a Token

For each agent:
  1. Go to github.com/settings/tokens?type=beta
  2. Click “Generate new token”
  3. Configure the token:
    • Name: e.g., clawup-titus
    • Expiration: Set as appropriate (no expiration for long-running agents)
    • Repository access: Select the specific repos your agents should work with
  4. Set permissions:
  1. Click “Generate token”
  2. Copy the token — it starts with ghp_ or github_pat_
You can use the same token for all agents if you prefer simpler management. Separate tokens give you better audit trails per agent.

​
Step 2: Add Tokens to .env

Add each agent’s GitHub token to your .env file using the <ROLE>_GITHUB_TOKEN pattern:
When you run clawup deploy, these are validated and stored encrypted in Pulumi config (e.g., pmGithubToken, engGithubToken).

​
What Gets Installed

On each agent’s server, the deploy process automatically:
  1. Installs the GitHub CLI (gh) from the official apt repository
  2. Authenticates gh with the provided token (gh auth login --with-token)
  3. Configures git to use gh for authentication (gh auth setup-git)
  4. Sets GITHUB_TOKEN as an environment variable

​
How Agents Use GitHub

Agents use the gh CLI and git for all GitHub operations:

​
By Role

​
Manifest Configuration

Set your GitHub repo in the manifest so agents know where to work:
This maps to the {{GITHUB_REPO}} template variable in identity workspace files. During bootstrap, agents clone this repo and verify access.