6 posts tagged with "copilot"

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.

GitHub just shipped an experimental feature in Copilot CLI (announced April 6) that does something no mainstream coding agent has done before: it uses a second model from a different AI family to review the primary agent's work before it executes. The feature is called Rubber Duck, and it's one of the first real-world implementations of cross-model review built into a tool developers actually use daily. If you care about multi-agent workflows or code quality, this one is directly relevant.

AI tooling is moving fast — fast enough that "just Google it" no longer works. We just shipped a dedicated AI-Assisted Development section to the Web Hub so the whole team is working from the same playbook.