Copilot for Linear separates who can start work from who can steer it

GitHub made its Copilot cloud agent integration for Linear generally available on July 23, 2026. Assigning a Linear issue to Copilot starts work in a cloud development environment and returns a pull request for review. GitHub write access controls who can trigger that work. Issue contributors without write access can still guide it, and GitHub says the entire issue description and comments are stored in the pull request as context.

That distinction affects who can direct engineering work and which planning conversations cross into GitHub. Before enabling the integration, decide which people may trigger Copilot, which people may steer an active session, and which issue text is acceptable to store in the resulting pull request. This article follows the documented path and identifies the local access and writing practices the product leaves to each organization.

The documented path starts with two administrators and ends with human review

The GitHub announcement says installation requires a GitHub organization or enterprise owner and a Linear workspace administrator. During setup, the administrator chooses which Linear teams the agent can access, and users with access to those teams can interact with it. The app is installed once for the GitHub organization; members then connect their own Copilot accounts.

On first use, a member connects a GitHub account and selects the repository Copilot will use. A user with write access to that repository can then assign the issue to Copilot. The GitHub integration documentation says the agent captures the entire issue description and comments as context and stores that context in the pull request.

GitHub then runs the work asynchronously in an ephemeral development environment powered by GitHub Actions. The integration creates a linked draft or WIP pull request, sends progress updates to the Linear issue, and requests pull-request review when the work is complete. A person still reviews the proposed change and decides what happens to it.

Our earlier articles cover ticket-level permissions, evidence, gates, and rollback and the general safeguards for cloud coding agents. The product-specific decision here is whose Linear input may shape work in the selected repository.

Repository write access controls the trigger while Linear participation can shape the input

The person triggering Copilot must have write access to the selected repository. Assigning Copilot from Linear does not give a user repository authority they lack in GitHub.

The set of people who can influence the run can be broader. GitHub says issue contributors without repository write access can guide Copilot through the issue conversation, and its GA announcement adds mid-session steering through Linear comments. Linear also says any user with access to a selected team can interact with an installed agent, while the human teammate remains the primary assignee and owner of delegated work.

The triggering user's write access does not attest to every sentence already in the issue or to later steering comments. Before rollout, compare Linear team access and issue-writing habits with repository access and pull-request visibility. Decide whose input is appropriate for that GitHub record.

Linear guidance supplies defaults, and the integration decides how to apply them

Copilot can receive a model choice, custom agent, base branch, working branch, and steering instructions from an issue. Teams can put recurring preferences into workspace or team guidance. According to Linear's agent documentation, workspace guidance applies across the organization, team guidance takes priority when both exist, and all guidance is passed to the agent.

Linear also states that interpretation and application depend on the specific integration. Guidance can express a convention, but the documentation does not present it as an authorization mechanism. The applicable access rules remain separate, which is the same distinction explained in why instructions do not enforce agent permission.

GitHub's separate issue-mutation review controls govern rationale, confidence, and suggestion review for supported changes to GitHub issues. Copilot for Linear hands issue context into a code-producing session and pull request. The two product surfaces answer different permission and review questions.

General availability establishes the workflow while operating results remain unknown

The rollout language differs by source and should stay precise. The announcement names Copilot Pro, Pro+, Business, and Enterprise; the current docs say all paid Copilot plans. Installation also requires a GitHub account, a Linear account, and membership in a Linear team, with a separate installation path for GitHub Enterprise Cloud organizations that use data residency.

The primary sources document the actors, context transfer, execution environment, pull-request handoff, progress updates, and review request. They provide no adoption figures, success rates, completion times, cost per task, reliability measurements, or review burden. They also leave sanitization, the exact comment history covered by “entire,” and retention beyond the pull-request storage statement unspecified.

Enable the integration only when the people and the context boundary match

The product connects Linear assignment to asynchronous coding work, while the organization owns the surrounding choices. Installation, team access, repository permissions, issue-writing habits, pull-request visibility, and review ownership must work together. Product capability is one layer; local ownership and data boundaries decide whether the handoff fits the team.

Enable Copilot for Linear when selected team access matches who may interact with the agent, repository write access identifies who may start work, and issue text is suitable for storage in the target repository's pull request. Otherwise, narrow the teams or repositories, or change how the team handles issue content before enabling the integration. Installation should follow that decision.

BaristaLabs can help align these decisions through AI consulting. Talk with us about one Linear-to-GitHub workflow before rollout.