The Copilot SDK gives you the same agent runtime that powers Copilot CLI — as a programmable library. You define agent behavior and tools, and Copilot handles planning, tool invocation, file edits, and the entire orchestration loop. No need to build your own agent framework.
Usage-based billing went live on June 1. Two days in, most developers have zero visibility into what's actually burning their premium requests. Chronicle just shipped a new cost-focused command — /chronicle:cost-tips — that surfaces exactly that. Think of it as the spending companion to the workflow-quality /chronicle:tips command we covered in April. It builds on the same session insights infrastructure in VS Code but points the lens squarely at your wallet. This post is commentary on why it matters right now.
Google I/O 2026 just wrapped, and Chrome's web platform announcements deserve a dedicated look. While the keynote predictably led with Gemini and Android, the Chrome team quietly shipped — or signaled — some of the most consequential changes to browser capabilities we've seen in years. If you build for the web, this was a big one.
Three themes dominated: AI built directly into the browser platform, new rendering capabilities that eliminate entire categories of workarounds, and developer tooling that acknowledges the reality of AI agents writing and testing code. None of these are incremental CSS features or minor API additions. They represent Chrome's bet on what web development looks like in 2027 and beyond.
What follows is a breakdown of the five announcements that matter most, with practical guidance on what to try now versus what to watch.
The State of Web Dev AI 2026 survey results have been published. This is the newest addition to the "State of" survey family by Devographics — the team behind State of JS, State of CSS, and State of HTML — now focused specifically on how developers use AI in their web development workflows.
Gergely's post on the LLM Wiki pattern hit close to home. I've been doing something adjacent for a while — personal knowledge management with Obsidian and local LLMs — and I immediately wanted to try the pattern on my own vault. Here's what I ran into, what worked, and what didn't.
VS Code 1.118 shipped an experimental feature called Chronicle on April 29, 2026, and it solves a problem most of us have been working around for months: your Copilot Chat history is now a queryable artifact, not a scroll-to-find afterthought. If you've ever prepped for a standup by scrolling through yesterday's agent sessions, or tried to remember what you did across three branches last Thursday, Chronicle targets exactly that pain. The full details are in the VS Code 1.118 release notes — this post is commentary on why it matters, not a restatement of the feature spec.
If you've set up GitHub Copilot, written a .github/copilot-instructions.md, maybe defined a custom agent or two — and then wondered "what now?" — the answer is awesome-copilot. It's the single most useful community resource for anyone pushing Copilot beyond defaults. Maintained under the github org, it has built a large community of users and contributors. It covers agents, instructions, skills, plugins, hooks, and agentic workflows — basically every customization surface Copilot exposes. If your setup ends at a .github/copilot-instructions.md, this repo is where you go next.
When your product is an AI assistant, using AI to build it feels natural — but doing it well is harder than it sounds. The AI-Assisted Development section describes these patterns in the abstract. This post is what they look like after a year in production on a real Aliz frontend: a React + TypeScript chat-based AI assistant with theming, 18-language internationalization, MCP integrations, and multi-environment deploys. The codebase is large enough that no single prompt can reason about it coherently, which is the whole reason the team stopped reaching for a tool and started building a system — the same shape described in Multi-Agent Orchestration. Three layers of AI setup, a team of specialist agents, and a workflow called QRSPI hold it together.
GitHub has announced changes to its Copilot Individual plans — Free, Pro, and Pro+ — taking effect in April 2026. The details are in the company news post and the changelog entry. Our reaction: unsurprising — and overdue. For historic context (see the Copilot plans page and GitHub's 2025 Pro+ announcement): Copilot Pro has been $10/month since launch, back when frontier models were cheaper and agent mode didn't exist, and Pro+ arrived in April 2025 at $39/month. The economics of that original entry-level tier were never going to survive a world of agentic coding on frontier models. This post is commentary, not a restatement of GitHub's announcement — read the source for the actual numbers.
In a recent blog post we explored Karpathy's LLM Wiki pattern — the idea that an LLM should build a persistent, interlinked wiki instead of re-deriving knowledge from scratch on every query. A few days later, it clicked: Aliz Web Hub — a Docusaurus site where AI agents contribute documentation via GitHub PRs — is essentially the same pattern with different tooling. The project predates Karpathy's gist. The parallel was noticed after, not before. The pieces map surprisingly cleanly.