Connect GitHub

The GitHub plugin uses the GitHub account already connected in Settings > Git Forge. There is no separate GitHub token field in the plugin.

Connect

1. On the host that will own the connection, open Settings > Git Forge.
2. Sign in to GitHub, or add the GitHub token used by Git Forge.
3. Open Settings > Plugins and select that host.
4. Expand GitHub. A successful connection shows the GitHub account as ready.
5. Open GitHub from the sidebar.

When you are looking at another host, open Git Forge settings on that host to change its credentials. On a CLI host, manage this same credential with the glueprint forge commands. The glueprint tasks token and glueprint tasks instance commands intentionally do not accept GitHub.

What the plugin shows

View	What it lists
My work	Pull requests waiting on your review, your own pull requests, and issues assigned to you, across every repository your login can reach, with real counts.
Pull requests	One cross-repository list with filters for open, needs my review, mine, draft and merged, plus search.
Issues	One cross-repository list with filters for assigned, created by me, mentions me, and all open.
Actions	Workflow runs for the repository you select, or the newest runs across the repositories that match a project on the host. Re-run everything, re-run only the failed jobs, or cancel.

The sidebar lists the repositories that match a Glueprint project on that host first, then every other repository your login can reach. Searching the second list asks GitHub, so a repository missing from the first page is still findable.

Start an agent from GitHub

• On an issue, Start work opens the usual composer: choose the Glueprint project, review the prefilled prompt and send. The issue is attached as context and Glueprint suggests a branch name and a new worktree.
• On a pull request, Glueprint offers the action that fits its state — review it, fix its failing checks, or address the feedback on it. Each one starts a session in the pull request’s worktree with the pull request as context.
• A pull request in a repository that is also a project on the host opens in Glueprint’s review sheet. A repository with no matching project opens on github.com.

Permissions

Reading pull requests and issues needs nothing beyond the Git Forge sign-in. Re-running or cancelling a workflow run is a repository write and needs the repo or public_repo scope. When it is missing, the page says so and gives you the exact fix: a command to run for a GitHub CLI sign-in, or which scope to add when you regenerate a token.

Fine-grained tokens and GitHub App installations do not report their scopes. Glueprint does not block them for that: the areas stay available and a write that is refused explains which permission it needed.

Issue states

Glueprint keeps GitHub’s native issue state and also places it in a common status category:

GitHub state	Glueprint category	Available change
Open	Todo	Close as completed or close as not planned
Closed -- completed, or no close reason	Done	Reopen
Closed -- not planned	Canceled	Reopen
Closed -- duplicate	Canceled	Reopen

If the host is running an older build

A host whose Glueprint build predates the GitHub plugin’s current surface shows the previous GitHub Issues view instead: choose a repository, then work with its issues. Update that host, or select a current one from the host row.