You're receiving this because you have an annual Copilot Pro or Pro+ plan.

GitHub Copilot isn't the same product it was a year ago. It has evolved from an in-editor assistant into an agentic platform capable of running long, multi-step coding sessions, using the latest models, and iterating across entire repositories. Agentic usage is becoming the default, and it brings significantly higher compute and inference demands.

To keep up with the way you use Copilot, we're transitioning to usage-based billing, and we want to give you enough time to prepare. If you're also an admin on a Copilot Business or Enterprise plan, you'll receive a separate email covering what's changing for your organization.

Last week, we made temporary updates to Copilot individual plans to improve reliability and performance ahead of the broader move to usage-based billing. We will loosen usage limits once usage-based billing is in effect.

What's changing on June 1 for Copilot Billing

Premium request units, or PRUs, will be replaced by GitHub AI Credits which are a monthly allotment of credits consumed based on token consumption (input, output, and cached tokens) according to the listed API rates per model. This change aligns Copilot pricing with actual usage and is an important step toward a sustainable, reliable Copilot business and experience for all users. Copilot code review’s agentic architecture runs on GitHub Actions. Copilot code review will now consume GitHub Actions minutes, in addition to GitHub AI Credits. These minutes are billed at the same per-minute rates as other GitHub Actions workflows. Fallback experiences will no longer be available. Under the new model, usage will instead be governed by available credits. What's changing on June 1 for Copilot Annual Plans

GitHub is retiring Copilot annual plans. As a current annual subscriber your Copilot Pro or Pro+ plan will continue as-is with premium request-based pricing. When your annual plan ends, your account will automatically transition to Copilot Free, which you can continue using at no cost. The experience on annual plans will change significantly: model multipliers will increase, and standard-tier models (currently 0x) will no longer be available, reflecting increased compute costs and the transition to usage-based billing, and no new models or features will be added to annual plans going forward. To keep getting new models and features, we recommend switching to a Copilot Pro or Pro+ monthly plan with the new usage-based billing system starting June 1. If you switch before your annual subscription expires, you'll receive prorated credits for the remaining value of your annual plan.

If you switch to a monthly plan, Copilot Pro is $10/month and Pro+ is $39/month, and each includes $10 and $39 in monthly AI Credits, respectively.

You can find more details on usage-based billing in our blog post and FAQ. We appreciate your patience as we build a more sustainable Copilot for everyone.

The GitHub Team

Comments URL: https://news.ycombinator.com/item?id=47924285

Points: 9

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=47846540

Points: 1

# Comments: 0

It works only with ActorDo, the work assistant I'm building for busy professionals.

Comments URL: https://news.ycombinator.com/item?id=47832445

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47574289

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47509036

Points: 50

# Comments: 3

- server manages thousands/millions of individual SQLite database files, one per tenant, behind a single gRPC/HTTP API

- provides per-tenant write serialization, a connection pool

- WAL-based replication to object storage (S3-compatible) - optional

- and an optional extension system for encryption (SQLCipher)

- optional extension vector search (sqlite-vec)

It will be suitable for products with tens of thousands of small, isolated tenant datasets where cost, operational simplicity, and data isolation matter more than global transactions or cross-tenant queries.

I'd probably use Go for this.

Note: Turso already has libsql with a server component but seems they are are fully committed to rewriting their own database.

This is just an idea, looking to see what's your view on this. It will be open-source if launched.

Wrote some specs here with help from Claude https://docs.google.com/document/d/1xgbPemWHatuCppw2x0_fgUV9...

Use case: - you need physical segregation of data per tenant - you want to have all the benefits of Sqlite ecosystem

For example: - HIPAA with each tenant separated - one failing tenant does not affect all the others.

Comments URL: https://news.ycombinator.com/item?id=47362174

Points: 3

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=46899569

Points: 1

# Comments: 0

I’m building ActorDo, an AI work assistant that actually helps people get work done. Email, calendar, tasks, context. Product is live. Users are using it.

Now I’m looking for a growth partner, not a tactic executor. With experience on US market.

This is about: - positioning and narrative - real distribution wedges - fast experiments and feedback loops

Close to product. Close to users. No fluff.

Looking for a self-driven growth marketer who likes early-stage chaos, thinks in systems, and wants real ownership.

If this clicks, let’s talk. Must provide references.

ActorDo info: https://actordo.com

Comments URL: https://news.ycombinator.com/item?id=46829714

Points: 14

# Comments: 3

Comments URL: https://news.ycombinator.com/item?id=46816546

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46704204

Points: 13

# Comments: 3

For example The Hustle is owned already.

But is much easier to get things running with AI.

Choose your favourite project or suggest one, while promoting yourself.

It starts at $1

Comments URL: https://news.ycombinator.com/item?id=46691628

Points: 2

# Comments: 7