GitHub Issues & PRs
Device Flow connection, Issues/PR node, push rules, and voice shortcuts.
The GitHub tool node manages Issues and Pull Requests for the active project’s GitHub.com remotes. Generic External MCP clients never see GitHub tools.
Connect
- Settings → Connections → GitHub
- Start Device Flow (
reposcope) - Enter the code on GitHub, then wait until the card shows connected
- Disconnect anytime (local keyring record removed)
Only the public client id is configured at build time — no client secret in the app. The access token is OS-keyring only; UI sees account login metadata.
Node UI
Singleton Tool node. Canvas stores only kind, optional title, selected remote name, and Issues vs PRs view — not the issue bodies themselves.
| Capability | Behavior |
|---|---|
| List | Open/closed/all filters; title, state, excerpt, labels, assignees, number |
| Create / edit | Flip-style form |
| Close / reopen | State action |
| Details / merge UI | Opens exact github.com URL in the system browser |
| PR create | Never auto-pushes; requires local HEAD, expected HEAD, and remote HEAD to match |
| Explicit push | Separate non-force push action when branch is missing/differs |
Merge is external-only (browser). BLXAde does not force-push.
Remotes
- Parsed only from GitHub.com remotes via fixed
gitinvocations - Credential-bearing URLs, foreign hosts, and unsafe names are rejected
- Default remote is derived for tools/voice when possible
Agents and Voice
| Actor | Access |
|---|---|
| Global Agent | Full GitHub tool set |
| Workspace Agent CLI | Same shared native queue |
| External MCP | None |
| Fast Voice | EN/DE phrases to open/close node and create simple issues |
Mutations are queued per repository with short-lived idempotency so voice, UI, and agents do not double-apply the same operation blindly.
Example (German Fast Voice): create an issue from a short spoken form; the node focuses and the queue accepts once.
Tips
- Open the project that has the correct remotes before using the node.
- For PRs, push the branch first (explicit action), then create the PR.
- Prefer Details in browser for complex merge conflicts.
Related: Canvas nodes, Agents, Voice.