← back NO. #335c7764

NO.: #335c7764
Topic: OTHER
Source: Simon Willison
Published: 2026-04-22 03:30:02
Importance: ★ 8/10 — radar 80
Original: simonwillison.net/2026/Apr/22/changes-to-github-copilot/#atom-everything

GitHub Copilot Tightens Individual Plan Limits and Reshapes Pricing

GitHub is tightening GitHub Copilot Individual plan usage, pausing new signups for some individual plans, and moving Claude Opus 4.7 behind the higher-priced $39/month Pro+ tier. For indie developers, this signals that agent-style coding workflows are becoming materially more expensive to serve, so tools that looked predictable at a flat monthly price may now carry stricter token and session limits.

[ KEY POINTS ]

GitHub officially announced tighter usage controls for Copilot Individual plans, unlike the confusion described around competing products.
Key changes mentioned here: stricter limits, paused individual-plan signups, removal of older Opus models, and Claude Opus 4.7 restricted to Pro+ at $39/month.
The stated reason is higher compute demand from long-running, parallel agent workflows.
The article highlights a shift from request-based economics toward token-based limits per session and per week.
For indie developers, budgeting and workflow design matter more now because heavy agent use can hit reliability or quota limits faster than before.

Originalsimonwillison.net/2026/Apr/22/changes-to-github-copilot/#atom-everythingRead original →

// related

#0001
#0001Other GeekNews12 hours ago
`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge
40radar
Bambu Studio3D printing slicer — based on PrusaSlicer
Copyleft obligations can reach bundled dynamic libraries and install info. If you fork AGPLv3 software, partial source drops are not enough.
- AGPLv3 Corresponding Source covers code needed to generate, install, run, and modify the work, not just visible app changes.
- A tightly coupled proprietary networking library may need source disclosure if it is dynamically linked into the modified app.
- Forking strong-copyleft projects for commercial software demands release-process checks before binaries ship.
Source: news.hada.io/topic?id=29694Read original →
FIG-0011:1
40radar
FIG-0011:1
#0002
#0002Other GeekNews12 hours ago
What's New in `Chrome` from Google I/O 2026
50radar
The web is shifting from human clicks to agent-driven browsing and AI-assisted development. Worth tracking before specs turn into defaults.
- Paul Kinlan, who leads Chrome DevRel, framed the last 6 months as a fast reset for web development workflows.
- One axis is preparing sites for agents that browse on users' behalf. Structured, machine-readable UX will matter more.
- Another axis is developer tooling. Chrome is positioning DevTools around AI-assisted debugging and building, not just inspection.
- The source is short and lacks API-level details, so this is a watchlist item rather than something to implement today.
Source: news.hada.io/topic?id=29693Read original →
FIG-0021:1
50radar
FIG-0021:1
#0003
#0003Other GeekNews15 hours ago
JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off
40radar
Small browser UIs can become heavy fast. WebAssembly helps, but async bridging to the JavaScript event loop keeps the payoff situational.
- Nested syntax and callbacks make JavaScript complexity grow quickly; bundle size is often a design outcome, not just tooling noise.
- Small UI surfaces can still pull in many libraries. Dependency defaults deserve review before reaching for another package.
- WebAssembly opens the browser to other languages, but Pyodide-style async event-loop integration adds real coordination cost.
Source: news.hada.io/topic?id=29675Read original →
FIG-0031:1
40radar
FIG-0031:1

GitHub Copilot Tightens Individual Plan Limits and Reshapes Pricing

// related

`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge

What's New in `Chrome` from Google I/O 2026

JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off