GitHub Copilot's Cloud Agent Now Works Inside Linear, No Extra Fee

Linear has quietly become the issue tracker of choice for a lot of fast-moving engineering teams, and as of July 23, it's also a place where you can hand off a ticket to an AI agent without leaving the app. GitHub Copilot's cloud agent for Linear is now generally available, and the pitch is straightforward: assign an issue the way you'd assign it to a teammate, and Copilot starts working on it in the background while you do something else.

What actually happens when you assign an issue to Copilot

The mechanics are what you'd expect from an asynchronous coding agent, but the delivery surface is new. According to GitHub's changelog post, once a Linear issue is assigned to Copilot, the agent reads the issue contents, opens a draft pull request, and then does the actual implementation work inside an ephemeral GitHub Actions environment - a sandbox that spins up for the task and doesn't persist afterward. Progress updates stream back into the Linear activity timeline in real time, so the ticket itself becomes the place you watch the work happen, rather than a GitHub Actions log you'd otherwise have to go find. When the agent finishes, it requests a PR review, and a human takes it from there.

That's a meaningfully different handoff model than opening Copilot inside your editor. You're not pairing with it in real time - you're delegating a ticket the way you'd delegate to an async contractor, and the activity timeline is your check-in point instead of a chat window.

The controls are more granular than a simple "assign and wait"

GitHub didn't ship this as a black box. The same changelog post lists several controls meant to keep the agent inside your team's actual conventions rather than defaulting to generic output: model selection per task, custom agent configuration pulled from your repositories, the ability to specify base and working branches, mid-session steering through @Copilot comments on the issue, and workspace- or team-wide configuration through Linear's own agent guidance settings. The @Copilot comment steering is probably the detail worth testing first if you try this - it's what determines whether the agent feels like a tool you can redirect mid-task or one you have to cancel and re-assign if it heads the wrong way.

If your team is comparing Linear against a plainer GitHub-native workflow, our Linear vs. GitHub Issues comparison is worth a look before you commit to building a process around this integration - the agent workflow only matters if Linear is already where your team lives.

Who can turn it on, and what it costs

Setup has two separate permission requirements, and both are gates most individual contributors won't be able to clear on their own. You need to install the GitHub Copilot for Linear app from the GitHub Marketplace, plus hold GitHub organization owner permissions and Linear workspace admin privileges to complete it. In practice that means someone with admin rights on both platforms has to do the initial wiring before anyone else on the team can assign a single issue to Copilot.

Plan-wise, the cloud agent is available on Copilot Pro, Pro+, Business, and Enterprise - there's no Free-tier path and no separate "agent add-on" charge layered on top. The pricing itself comes from a different GitHub announcement than the one introducing the Linear integration: under the usage-based billing change that took effect June 1, Copilot Pro runs $10 per user per month and includes $10 in monthly AI Credits, Business is $19/month with $19 in credits, and both Pro+ and Enterprise sit at $39/month with $39 in credits apiece.

Code completions and Next Edit suggestions stay included on every plan regardless of tier and don't draw down your AI Credits, so the cloud agent runs alongside your existing daily-use features rather than competing with them for the same metered pool - though a long-running agent task against a large issue is exactly the kind of work that will eat into those credits faster than routine autocomplete. If you want the full breakdown of how the credit system works across tiers, our guide to Copilot's usage-based billing shift covers it in more depth than this changelog does. And if you're weighing Copilot against a different coding assistant entirely, our three-way comparison of Claude Code, Cursor, and GitHub Copilot is a better starting point than this integration alone.

Worth a beat on Linear's own pricing too, since this story is entirely about what Copilot charges, not what Linear charges: Linear's Basic plan runs $10/month, Business is $16/month, and Enterprise is custom - see our Linear pricing breakdown or the live pricing page for the current numbers. Nothing about this Copilot release changes any of that; it's a capability bolted onto Linear's existing paid tiers, not a Linear price change.

Is this worth setting up

The honest case for this feature is narrow but real: it removes a context switch that async engineering teams deal with constantly. Instead of triaging a Linear ticket, then opening GitHub, then prompting an agent separately, then reporting status back manually, the whole loop happens inside the tracker your team already checks every day. That's a genuine workflow win if - and only if - your team already has both Linear and a qualifying Copilot plan, and someone with the right admin access is willing to do a one-time setup.

If you're still deciding whether Linear itself is the right tracker for your team, start with our Linear review - this agent integration is a reason to lean toward Linear if you're already leaning that way, not a reason to switch trackers on its own.