9 posts tagged with "agents"

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.

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.

Anthropic has released Claude Opus 4.7. Opus 4.6 has been central to our workflow — it powers Claude Code, our ⭐ recommended agent for complex tasks — so any new Opus release is worth paying attention to. That said, our first impression is that this isn't the across-the-board leap some might expect. Here's what we know and what we think.

Roadmap.sh has published two new learning paths directly relevant to the Aliz stack: one for Claude Code (Anthropic's CLI-based coding agent, already our ⭐ recommendation for complex tasks) and one for OpenClaw (an open-source AI agent orchestration framework). These join roadmap.sh's existing web, JavaScript, TypeScript, and Node.js roadmaps as structured, community-maintained learning resources.

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.

Andrej Karpathy — the same person who coined vibe coding — recently published a gist describing a pattern he calls the "LLM Wiki". The core tension it addresses is simple: RAG re-derives knowledge from scratch on every question. What if the LLM built something persistent instead — a structured, interlinked wiki that compounds over time? It's a deceptively simple idea with some genuinely interesting implications.

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.