GitHub Copilot

Discussion around GitHub Copilot over the past four weeks was dominated almost entirely by reactions to a pricing restructuring that took effect around June 1st. The volume of conversation was modest, but the emotional temperature around the pricing change was notably high, with commenters describing the shift as undermining the fundamental value proposition of a subscription model. Several mentions framed the new structure as opaque or deceptive, with phrases like 'hiding the price' and 'open ended cost' appearing across threads. One commenter went so far as to call it 'robbery' and noted they had already cancelled. The sense that a fixed subscription had been replaced with something resembling metered API usage drew pointed criticism, with discussion suggesting that the distinction between a subscription plan and a direct API key had effectively collapsed.

The score trajectory over the window tells a volatile story. Sentiment climbed sharply in the final week of April and again in mid-May, suggesting pockets of genuine enthusiasm, likely tied to feature coverage and workflow integration that a small number of commenters praised. However, those highs were followed by steep drops, and the late-May period recorded the lowest score in the window. The most recent data points show a partial recovery, though the overall mood remained unsettled.

Where opinion divided most visibly was on the practical impact of the credit consumption rate. Multiple commenters described burning through a significant share of monthly credits within a single day of casual use, framing this as alarming. A smaller thread offered a more technical counterpoint, questioning whether discounting mechanics were being misunderstood. Praise themes around feature quality and ease of use were present but lightly represented, suggesting that positive sentiment existed in the discussion but was being drowned out by pricing frustration during this particular window.