Task providers
Bring external issues into Glueprint and start linked agent sessions from provider work.
- Topic
- Task Providers
- Available on
- Available onDesktopWeb PortalCLI Daemon
- Reviewed
- September 14, 2026
On this page
Plugins bring external work into Glueprint alongside its built-in boards and tasks. Open the GitHub plugin to work with issues in your repositories, or use Tasks for Glueprint boards. Start linked sessions without copying issues into a board.
| Source | Task container | Connection |
|---|---|---|
| Glueprint | Board | Built in |
| GitHub Issues | Repository | Your existing Git Forge sign-in |
Credentials belong to a host
Every external connection belongs to the Glueprint host where you add it. The credential stays on that host. The web portal asks the selected host to read or change provider tasks and does not collect or keep the provider token.
This host ownership matters when you use more than one machine. A connection on your desktop is available while that desktop is online; a connection on a CLI daemon belongs to that daemon. Choose the correct host in the plugin or Settings > Plugins.
Where you can use task providers
| Surface | What you can do |
|---|---|
| Desktop | Connect providers on the local host, inspect another host’s status, browse tasks, make supported changes, and start sessions. |
| Web portal | Pick an online host, browse its task sources, make supported changes through it, and start linked sessions. Provider credentials cannot be entered in the portal. |
| CLI | Inspect sources and use the host as a task-provider owner. Manage GitHub credentials with Git Forge commands. |
| MCP | Let an agent list, search, read, create, update, transition, comment on, and start work from tasks through the built-in MCP server. |
Reaching a task source through another host, including from the web portal, uses Glueprint’s cloud relay and requires a Pro plan or higher. Local access on the host that owns the credential does not use that cross-host plan gate. See Plans and limits.
From an issue to a session
Suppose you select a GitHub repository and open an issue. Click Start ->, choose the Glueprint project that contains the code, and review the prefilled session composer. The linked task is attached as context and the prompt begins with Work on the linked task. Glueprint suggests a task-based branch name and selects a new worktree; you can change the prompt and workspace choice before sending.
Glueprint creates the session with a link back to the provider task. The task key appears with the session, and the workspace Tasks tab collects these links under Linked from sessions. If a session is already linked to that task, Open -> opens the existing session without contacting the provider first.
Next steps
Manage plugins
Open Settings > Plugins, select a host, and open a plugin to view its connections and configuration. Use the desktop sidebar’s More plugins menu to open or pin a plugin. Hiding a plugin preserves its connections and pins; showing it restores its pinned entry. Opening a hidden plugin shows it without automatically pinning it.
Built-in Glueprint boards remain part of Tasks. Their visibility and default-source controls are in the catalog’s Task preferences group. Skills, MCP servers, and agent packages are managed separately in Settings > Agent extensions.