Flarite Docs

GitHub Integration

Explore repos, manage issues, review pull requests, inspect Actions workflows, and track releases — all in plain English.

What you can do

  • Repositories — List, search, and inspect repos across your personal account and organizations.
  • Issues — Browse open issues, filter by label or milestone, and summarize issue threads.
  • Pull Requests — List open PRs, view diffs, check review status, and inspect CI check runs.
  • Actions — View workflow runs, inspect logs for failed jobs, and monitor build health.
  • Branches — List branches, find stale branches, and compare branch states.
  • Releases — Browse tagged releases and inspect release notes across all your repos.
  • User & Org — Fetch your GitHub profile, list org memberships, and view team details.

Getting your GitHub Personal Access Token

Flarite uses a Personal Access Token (PAT) to access the GitHub APIs on your behalf. GitHub supports two PAT formats — use a Fine-grained token for the most secure, scoped access.

TipFine-grained tokens (recommended) let you scope access to specific repositories and explicitly grant only the permissions Flarite needs. Use Classic tokens only if you need access across all organisations or legacy integrations.

Fine-grained Token (recommended)

  1. Go to github.com → Settings → Developer settings → Personal access tokens → Fine-grained tokens.
  2. Click "Generate new token".
  3. Set an expiration (90 days recommended) and give it a name like "Flarite Access".
  4. Under Repository access, choose All repositories or select specific ones.
  5. Grant the following Repository permissions:
Contents          — Read-only
Issues            — Read-only
Pull requests     — Read-only
Actions           — Read-only
Metadata          — Read-only  (required)
  1. Grant the following Account permissions:
Email addresses   — Read-only
  1. Click "Generate token" and copy it — it will look like github_pat_….
  2. Paste it into Flarite → GitHub → API Tokens.

Classic Token (alternative)

  1. Go to github.com → Settings → Developer settings → Personal access tokens → Tokens (classic).
  2. Click "Generate new token (classic)".
  3. Select the following scopes:
repo              — Full control of private repositories
read:org          — Read org & team membership
read:user         — Read user profile data
  1. Click "Generate token" — the token will look like ghp_….
  2. Paste it into Flarite → GitHub → API Tokens.
⚠️
ImportantYour token is displayed only once on GitHub. Copy it before leaving the page, then paste it into Flarite immediately. Flarite encrypts it with AES-256 before storage.

Example prompts

"List all open pull requests in my-org/backend"

"Show me the last 10 failed Actions runs in my repo"

"Which issues are labelled 'bug' and have no assignee?"

"Summarise the release notes for v2.1.0 of my-org/frontend"

"List all repos in my-org that haven't had a push in 60 days"

"What's the CI status for the latest commit on the main branch of my-app?"

Supported tools

Flarite exposes the following GitHub tools to the AI model: get_user_profile, list_repositories, get_repository, list_issues, get_issue, list_pull_requests, get_pull_request, list_workflow_runs, get_workflow_run, list_branches, list_releases, get_release, and more.

💡
NoteFlarite does not create, modify, or delete GitHub resources — all tools are read-only by default. Write operations (creating issues, merging PRs) are planned for a future release.