copilot cloud agent is moving into the ticket queue, not just the editor

GitHub made Copilot cloud agent for Linear generally available on July 23, 2026. assign a Linear issue to Copilot and it analyzes the ticket, opens a draft pull request, works in an ephemeral GitHub Actions-backed environment, streams progress into Linear, then asks for review when it is done.

the important part is not that Copilot can open a PR. that was already the direction of travel. the important part is where the command starts: inside the issue tracker, with model choice, branch selection, custom agent selection, and mid-run steering exposed in the Linear workflow.

what changed

Linear users can now assign work directly to Copilot cloud agent. per issue, teams can choose the model, point Copilot at a custom repo agent, set the base and working branches, and mention Copilot in a Linear comment to steer a live session. the integration requires GitHub org owner permission and Linear workspace admin privileges to install.

availability is broad enough to matter: GitHub says the Linear path is included with Copilot Pro, Pro+, Business, and Enterprise. that makes it a real workflow primitive, not an Enterprise-only preview hidden behind procurement.

the second release matters too

on the same day, GitHub put agent automation controls for GitHub Issues into public preview. automations can now attach rationale and confidence to supported issue changes, and can hold suggested updates for review instead of applying them immediately. covered actions include labels, fields, issue type, closing issues, and assignees.

has:suggestions now finds issues with pending automation suggestions. repository admins can also set confidence thresholds so high-confidence changes apply automatically while medium and low confidence suggestions wait for a human.

honest take

this is GitHub admitting the next coding-agent surface is not the chat box. it is the queue. the ticket becomes the prompt, the branch becomes the work area, and the review request becomes the handoff.

the caveat is in GitHub's own framing: approvals are a workflow convenience, not a server-side security boundary. if an agent has permission to change issues, the review layer is process discipline, not hard isolation. teams should treat it as a way to keep humans in the loop on messy triage and automation decisions, not as a substitute for permission design.

the next thing to watch is model routing. one day after the Linear GA, GitHub added Claude Opus 5 to Copilot for Pro+, Max, Business, and Enterprise users across the model picker. expensive long-running agents plus ticket-native assignment is exactly where cost controls, branch policies, and audit trails stop being admin garnish and start becoming product features.