# GitHub adds new Copilot features as usage-based billing takes effect > Source: > Published: 2026-06-05 17:32:00+00:00 GitHub is expanding [Copilot](https://www.infoworld.com/article/3609013/github-copilot-everything-you-need-to-know.html) beyond the IDE with a new desktop application and a new collaborative work surface called canvas as part of its broader efforts to pitch the AI-assisted coding tool as the control center for agent-native software development. The desktop application announced at Microsoft’s annual Build conference this week is designed to give developers a dedicated environment for working with AI agents throughout the software development lifecycle, rather than limiting those interactions to code-generation tasks inside an editor, the company wrote in a [blog post](https://github.blog/news-insights/product-news/github-copilot-app-the-agent-native-desktop-experience/?utm_source=live-blog-copilot-app-desktop-blog-cta&utm_medium=blog&utm_campaign=msbuild-2026). The application includes a collaborative workspace called canvas where developers can brainstorm ideas, refine requirements, generate plans, and iterate on projects alongside AI, it said. It also has new Agent Merge and code review features that enable developers to automate Copilot to combine tasks of different agents to complete a specific goal or conduct autonomous code reviews according to set standards, it said. These new features could reduce context switching, increase engineering efficiency, and accelerate delivery cycles, said [Phil Fersht](https://www.hfsresearch.com/team/philfersht/), CEO of HFS Research. However, despite the new features, much of the conversation among developers in recent weeks has centered on a different topic: this week’s [shift to a usage-based billing model for GitHub Copilot](https://www.infoworld.com/article/4164236/github-shifts-copilot-to-usage-based-billing-signaling-new-cost-model-for-enterprise-ai-tools.html) that it announced in April. The changes were met with a wave of criticism on the GitHub [community forum](https://github.com/orgs/community/discussions/192948?sort=top#discussioncomment-17134630), where some users accused the company of a “bait and switch,” while others requested refunds or announced plans to cancel their subscriptions. For analysts, though, the pricing change was, at least from GitHub’s point of view, necessary and justified. “The pricing change is justified by where GitHub is going, not by where the product is today. Running multiple agents in parallel with sandboxes, canvas reviews, and Agent Merge looping through CI is closer to cloud compute than an IDE plugin, and you cannot price compute on a flat seat fee. So metered billing is the right call structurally,” said [Advait Patel](https://www.linkedin.com/in/advaitpatel93), a senior reliability engineer at Broadcom. Fersht said developers and CIOs need to focus on Copilot’s metamorphosis from being a coding assistant into a platform for orchestrating software-development agents and workflows. “That changes the ROI conversation significantly. CIOs should stop thinking about Copilot as a seat-license productivity tool and instead evaluate it as an AI-powered software delivery platform,” he said. “The metrics shift from ‘lines of code generated’ to broader operational outcomes such as release velocity, code quality, defect reduction and engineering efficiency.” GitHub is not the first company offering vibe-coding tools to rethink its pricing strategy as AI agents proliferate across enterprises and evolve to take on more complex software-development tasks that are computationally more intensive. Over the past year, [platforms such as Claude Code, Replit, Cursor, and Kiro have repeatedly adjusted their pricing structures](https://www.infoworld.com/article/4048198/the-era-of-cheap-ai-coding-assistants-may-be-over.html) to account for mounting infrastructure costs, limited GPU availability, and the expense of serving increasingly sophisticated AI models and agents, despite furor among their users. That common pressure across AI coding vendors is why [Amit Chandak](https://www.linkedin.com/in/amitchandak78/), chief analytics officer at IT consulting firm Kanerika, thinks developers and CIOs should focus less on GitHub’s pricing mechanics and more on whether these increasingly capable tools are delivering measurable business value. “The new features that GitHub announced can act as productivity multipliers as well as features that increase consumption without delivering proportional business value. Without productivity baselines established before adoption, enterprises risk absorbing higher costs with no clear line back to delivered value,” Chandak said. For Fersht, developers and CIOs will need to focus on governance, monitoring and financial controls as the pricing model is changing. “The governance challenge is very real. Autonomous agents can continuously reason, test, revise and interact with multiple systems in ways that create far less predictable consumption patterns than traditional SaaS tools,” he said. Patel, however, advised users and decision-makers to be more skeptical, especially since the new features are currently in technical preview. “Customers are being asked to pay variable rates now for value that has not been validated in production. Do not assume new capabilities justify higher spend,” he said. “Instead, run a 90 day pilot, measure PRs merged per dollar before and after, and let the data decide. If the ratio improves, the pricing is fair. If it does not, you are paying for promise, not delivery,” Patel added.