Setup

Enter your API keys to get started. All credentials are stored locally in your browser — nothing is sent to our servers.

Credentials

Enter your API keys. All values are stored locally in your browser.

Enables issue sync, semantic search, and duplicate scanning. You can add this later.

Setup Guides

AIssue needs a GitHub token to read issues from your repositories. Choose the token type that fits your setup:

Option A: Fine-grained token (recommended for personal repos)

  1. Go to GitHub → Settings → Developer settings → Fine-grained tokens
  2. Enter a Token name (e.g. “AIssue”)
  3. Set Expiration — up to 1 year
  4. Under Repository access, choose “All repositories” or select specific repos
  5. Under Permissions → Repository permissions, set:
    • Issues → Read-only
    • Metadata → Read-only (auto-selected)
  6. Click Generate token and copy it immediately

Option B: Classic token (required for SSO organizations)

If your repositories belong to an organization that uses SAML single sign-on (SSO), you need a classic token — fine-grained tokens cannot be authorized for SSO orgs through the token settings page.

  1. Go to GitHub → Settings → Developer settings → Tokens (classic)
  2. Enter a Note (e.g. “AIssue”)
  3. Set Expiration
  4. Select the repo scope (or just public_repo if you only need public repositories)
  5. Click Generate token and copy it immediately
  6. Back on the token list, click Configure SSO next to your new token
  7. Click Authorize next to your organization's name, then complete the SSO prompt
Without SSO authorization, GitHub returns 404 Not Found for private organization repos — even if the token has the right scopes.
Authenticated rate limit: 5,000 requests/hour. Without a token, GitHub allows only 60 requests/hour.