Start work from a task

Every supported external task row has a session action. Start -> begins a linked session flow. After a matching session exists, the same action becomes Open ->.

Open in provider is separate: it opens the task’s provider URL and does not create or navigate to a Glueprint session.

Start a linked session

1. Open Tasks and select the provider, host, instance, and container.
2. Find the task and click Start ->, or open its detail sheet and click Start -> there.
3. Choose the Glueprint project that contains the code. Glueprint selects an exact GitHub repository match or a remembered project for the provider container when it can; otherwise it asks you.
4. Review the session composer. The task is attached as context and the prompt begins with Work on the linked task.
5. Choose the agent and workspace, edit the prompt if needed, and start the session.

The provider container and Glueprint project are separate. A provider repository, project, or team can help you choose the right project, but Glueprint asks you to select the local project that the agent will work in.

Worktree choice

You can run at the project root, choose one of the project’s existing worktrees, or create a new worktree through the composer. Glueprint suggests a branch name from the task key and title and preselects New worktree so the worktree and task link are created together. Review the branch before sending.

Where the link appears

The new session records the task’s provider, owning host, instance, container, ID, key, title, and URL. Glueprint uses that identity to keep the link unambiguous across hosts and provider accounts.

You see the provider icon and task key on the session card, workspace tab, and session header. Selecting the header chip opens the task in Glueprint. When only the saved task URL is usable, Glueprint opens the provider page.

The message composer can also add a provider task as a task chip from its add menu. Sending that message includes the task as context. Only Start -> creates the durable session link.

In a workspace’s right-side Tasks tab, Linked from sessions lists external tasks referenced by sessions in that workspace. Each row can Open in provider or Open session. If current provider data cannot be read, the row keeps the saved link and shows Status unavailable.

Opening an existing linked session

Glueprint checks its known sessions before asking the provider for start-work data. If the exact task is already linked, Open -> navigates to that session even when the host is offline, the provider credential needs attention, or remote task-provider access is plan-gated. This navigation does not make a provider request.

What Glueprint writes back

Starting work on a GitHub issue leaves its state unchanged. The task-to-session link is stored with the Glueprint session and does not add a provider comment. Other providers describe their follow-up behavior in their connection guides.

Status changes, assignments, comments, and task edits you choose in the Tasks view are written to the provider immediately as their own actions.