惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

有赞技术团队
有赞技术团队
G
Google Developers Blog
T
Tailwind CSS Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
J
Java Code Geeks
P
Proofpoint News Feed
V
Visual Studio Blog
爱范儿
爱范儿
The Cloudflare Blog
博客园 - 叶小钗
V
V2EX
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
M
MIT News - Artificial intelligence
Microsoft Security Blog
Microsoft Security Blog
博客园 - 聂微东
H
Help Net Security
B
Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 【当耐特】
量子位
宝玉的分享
宝玉的分享
WordPress大学
WordPress大学
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
GitHub Copilot AI Credits Billing Explained: What's Free,...
Clemente Nogueira · 2026-06-16 · via DEV Community

Clemente Nogueira

TL;DR

On June 1, 2026, GitHub Copilot switched from flat-rate pricing to a token-based "AI Credits" system, and the community forum responded with over 900 downvotes. Most of the outrage is aimed at the wrong target. Code completions are still unlimited on every plan. What actually changed is chat, agent mode, and PR review — and the real complaint isn't the price, it's the unpredictability. This article breaks down the actual numbers, what's still free, where the AI coding tools market stands in June 2026, and the hybrid Copilot + Claude Code workflow — anchored by a single AGENTS.md file — that I switched to as a result.

The problem

GitHub officially moved Copilot from a flat subscription to usage-based AI Credits on June 1. The community forum thread reacting to it crossed 900 downvotes within days. That's a strong signal, but it's worth pausing before reacting to forum sentiment alone, because a chunk of that anger is based on an incomplete picture of what actually changed.

What actually changed

The new model is straightforward on paper: one AI Credit equals one US cent, and each plan's base allowance is set above the subscription price rather than equal to it. The $10 Copilot Pro plan now comes with 1,500 AI Credits per month — worth $15 at that rate. I'm on the Pro+ tier myself, at $39/month for 7,000 credits, worth $70. On paper that's generous. In practice, it's exactly where the burn rate becomes a real concern, because the headline number looks like more room than agentic workflows actually use.

There's a second change worth flagging alongside the billing shift: GitHub deprecated GPT-4.1 across every Copilot surface on June 1 — chat, inline edits, ask mode, agent mode, and code completions. If you had a specific reason to be on that model, it's gone.

Here's the part that actually matters, though. The core complaint isn't the price — most developers won't blow through their credits under normal day-to-day use. The complaint is unpredictability. A flat rate means you know your spend before the month starts. A credit system means your spend depends on what you do, which model handles it, and how long your prompts run. Run out mid-sprint, and you're blocked until the cycle resets. That shift from certainty to metered uncertainty is the legitimate part of the frustration, and it's worth taking seriously even if the framing on the forum skews toward outrage over analysis.

What's still free vs. what burns credits

This is the detail most of the discourse is skipping past, and it changes how you should actually respond to the change.

Inline completions — ghost text, Next Edit Suggestions — are still unlimited across every paid Copilot plan. These were the original features that made Copilot what it is, and they don't touch your credit balance at all.

Three things do burn credits: chat (asking Copilot questions in the sidebar), agentic workflows (multi-step tasks run through agent mode), and code review (having Copilot review your pull requests).

So the useful question isn't "is this bad?" — it's "where do I actually spend my AI time?" If your workflow leans on ghost text with the occasional chat question, this change probably barely touches you. If you've built your workflow around agent mode for long-running, multi-step tasks — which is exactly what I had done — you'll feel it. In my case, I'd already built a library of reusable agent prompts, and under the new pricing I can no longer run them in a way that's financially sustainable.

Where the AI coding tools market stands in June 2026

The Copilot billing change doesn't exist in isolation — the whole AI coding tools landscape has shifted noticeably over the past six months.

According to JetBrains' AI Pulse survey of over 10,000 professional developers, Claude Code now holds the highest product loyalty metrics in the category: a 91% CSAT score and an NPS of 54 (NPS runs from -100 to +100, so 54 is exceptional for any developer tool). On actual workplace adoption, Claude Code and Cursor are now tied at 18% each, up from roughly 3% for Claude Code in mid-2025 — a 6x jump in six months. Copilot is still the most widely adopted tool overall at 29%, but that growth has stalled; both awareness and adoption have flattened.

Cursor has crossed $2B in annualized revenue and introduced parallel agents, letting you run up to eight agents simultaneously across different parts of your codebase through a visual dashboard. Windsurf rebranded entirely to Devin Desktop on June 2, with Cognition retiring the Windsurf brand and replacing the original local agent (Cascade) with a Rust-rewritten Devin Local.

The open-source side had its own shake-up this spring. Roo Code — one of the most-loved open-source coding agents — shut down completely on May 15 and had its GitHub repo archived, with its team pointing users toward Cline and a fork called Kilo Code. A third project, OpenCode, quietly became the most-starred open-source coding agent on GitHub, north of 160,000 stars, running entirely in the terminal. Amazon also threw a free agentic IDE into the mix with Kiro.

The number that reframes the whole conversation: developers today use an average of 2.3 AI tools simultaneously. Not one tool winning everything — a combination. Which means the real question was never "which tool is best?" It's "what is each tool best at, and how do I combine them?"

My hybrid workflow: AGENTS.md + Claude Code + Copilot

Here's the setup I landed on. At the center of it is a single file called AGENTS.md, committed to the repo root, that holds the project's architecture, stack, conventions, and hard constraints — the open standard that Copilot and most other AI coding tools read directly:

# AGENTS.md

## Project
Next.js 16 app, TypeScript, Tailwind, deployed on Vercel.

## Commands
- Dev: pnpm dev
- Test: pnpm test
- Lint: pnpm lint && pnpm tsc --noEmit

## Conventions
- Named exports only, no default exports in components
- Server components are the default

## Hard constraints
- Never commit .env or .env.local

One nuance worth being precise about: Claude Code doesn't read AGENTS.md directly — it only reads CLAUDE.md. The way AGENTS.md reaches Claude Code is a one-line import inside CLAUDE.md:

See @AGENTS.md for all project rules, commands, and conventions.

Add that line once, and Claude Code loads AGENTS.md automatically at the start of every session from then on — you still never restate the rules, you just need that single bridge line in place first. That eliminates the biggest hidden productivity tax in AI-assisted work: repeating context.

The split that's worked for me: Claude Code handles the long-form, multi-step agentic work — refactors that span several files, writing a test suite, debugging something that needs a lot of context held at once. GitHub Copilot handles keystroke-level completions — ghost text, inline suggestions, boilerplate — which are still unlimited and still genuinely excellent at that specific job. The result is that my Copilot credit usage barely moves, because I've stopped routing heavy agentic work through it, and the agentic work goes to a tool that was already better suited to it.

The mistake most developers make

The instinct after a pricing change like this is to pick a side — stay on Copilot and absorb the credits, or drop it entirely for Claude Code. Both are probably the wrong move. The 2.3-tools-average stat isn't an accident; it reflects how developers who are actually productive with AI tools work in practice — one tool for fast inline work, one for deep reasoning, increasingly tied together by a shared protocol like MCP.

If anything, the billing change is a useful forcing function. It pushes you to get intentional about where your AI usage actually goes, instead of defaulting into whatever setup you happened to start with.

Key takeaways

  • GitHub Copilot moved to AI Credits on June 1: Pro ($10/mo) includes 1,500 credits, Pro+ ($39/mo) includes 7,000 — 1 credit = $0.01. GPT-4.1 was deprecated across all Copilot surfaces the same day.
  • Code completions (ghost text, Next Edit Suggestions) are still unlimited on every plan. Chat, agent mode, and code review are metered.
  • The real frustration is unpredictability, not price — a fair complaint, especially for anyone leaning on agent mode for heavy multi-step work.
  • Claude Code now leads the category on loyalty (91% CSAT, NPS 54) and has closed the adoption gap with Cursor; Copilot's growth has stalled at 29%.
  • Developers use an average of 2.3 AI tools — the goal isn't picking a winner, it's building a deliberate hybrid setup.
  • A single AGENTS.md file at the repo root keeps Claude Code and Copilot briefed on the same project context without duplicating it.

Part 2 covers two completely free, open-source AI coding agents (Cline and Kilo Code) that drop into VS Code right where Copilot Chat sits — running a real task for $0.00. Linked from the YouTube video once it's live.

ai #github #productivity #programming #copilot

📺 Full video: Watch on YouTube