Where to Find Every AI Coding Tool's Changelog

Every AI coding tool ships changes on its own schedule, in its own place, and in its own format. Finding the right ai coding tool changelog for the tool you actually use should be trivial, but in practice the official source is scattered: some vendors keep a clean public changelog, some bury release notes in a help center, some announce on a blog, and some mix all three. This page is a directory. It collects the official changelog and release-note sources for the major AI developer tools in one place, with direct links, so you can bookmark the ones that matter and stop hunting. At the end, we cover how to track them all at once instead of checking each site by hand.

A quick note on what counts as "official" here. The source of truth for any tool is whatever the vendor itself publishes: the page they update when they ship. Third-party summaries (including ours) are useful for breadth and context, but when you need an exact version number, a breaking change, or a deprecation date, go to the vendor's own page. Every link in the tables below points to a first-party source.

Why every AI coding tool changelog lives somewhere different

There is no shared standard for how developer tools publish releases. A traditional library might tag a GitHub release and call it done. AI tools are messier because they are several products at once: a desktop or web app, a CLI, an API, and often a set of models, each of which can change independently. OpenAI is the clearest example, where the consumer ChatGPT app, the developer API, and individual models all have their own update streams. Claude Code keeps a versioned CLI changelog while the underlying models are documented separately. Editor tools like Cursor and Windsurf ship app updates on a fast cadence and publish a single product changelog.

The practical consequence is that "where is the changelog" has a different answer for almost every tool, and sometimes more than one answer for the same tool. That is exactly why a directory is useful: you only have to figure out each tool's home for releases once, then bookmark it.

The big table: tool to changelog source

Here are the official release sources for the major AI coding tools. Where a tool publishes in more than one place (for example, an app changelog plus separate model or API notes), the most useful primary source is listed first. URLs do change, so if a link moves, search for the tool name plus "changelog" or "release notes" and prefer the result on the vendor's own domain.

Claude, OpenAI, and Cursor in detail

The three tools most developers track day to day are Claude Code, OpenAI's products, and Cursor. Each has a slightly different setup worth understanding so you know where to look first.

Claude Code

Claude Code is Anthropic's command-line coding agent, and its release notes live in the official Claude documentation. That page tracks the CLI itself: new commands, configuration changes, permission defaults, and fixes. Because Claude Code's behavior also depends on the underlying Claude models, it is worth keeping the model documentation handy too, since a model update can change how the agent reasons even when the CLI version has not moved. We maintain a plain-language mirror at our Claude changelog, and the app that tracks it is Claude Drops.

OpenAI (ChatGPT and the API)

OpenAI is the case where "the changelog" is really two changelogs. The consumer ChatGPT app publishes release notes in OpenAI's help center, covering features, model availability, and interface changes. The developer API has a separate changelog on the platform site, which is the one to watch if you build against the API rather than using the chat app. If you ship code against OpenAI, bookmark both. Our summarized feed is at the Open Drops changelog, and the app is Open Drops.

Cursor

Cursor keeps things simple with a single product changelog on its own domain. Because Cursor ships frequently and bundles model and agent improvements into app releases, that one page is usually all you need to follow the editor. Note that Cursor's coding ability also rides on third-party models, so a Cursor release and a model release from Anthropic or OpenAI can both move your experience. Our version is at the Cursor Drops changelog, tracked by Cursor Drops.

The rest: Copilot, Windsurf, Gemini, and editors

Beyond the big three, a few more sources are worth knowing if your stack reaches into other tools.

• GitHub Copilot publishes through the general GitHub Changelog, which you can filter to Copilot entries. Copilot spans several surfaces (editor extensions, CLI, and GitHub itself), so watch for which surface a given change applies to.
• Windsurf maintains a product changelog on its own site, similar in style to Cursor's, focused on the editor and its agent features.
• Gemini and Gemini Code Assist updates land across Google's AI and Cloud release notes. Because Google splits consumer and developer products, the relevant page depends on whether you use the assistant in an IDE or call the model directly.
• VS Code publishes detailed monthly release notes that increasingly include AI features. If your AI tooling is a VS Code extension, the editor's own notes are a useful companion to the extension's changelog.

How to track every changelog at once

Bookmarking a directory solves "where is it," but it does not solve "did I miss anything." Checking nine pages by hand is exactly the chore that makes people fall behind. There are three practical ways to collapse the directory into something that comes to you:

1. Aggregate with RSS. Add every changelog feed from the tables above to one reader. This gives you a single chronological stream across all your tools, scanned on your schedule. The catch is that RSS is silent: it collects, but it never interrupts you.
2. Subscribe to a curated newsletter for context. A good weekly digest tells you which of the week's changes actually mattered, which is the judgment raw feeds lack. The tradeoff is latency and coverage that may not match your exact stack.
3. Use push for the handful of tools you cannot miss. Notifications are the only channel that reaches you when you are not looking, so reserve them for the tools you depend on day to day and let everything else sit in your reader.

If assembling that yourself sounds like more maintenance than you want, a dedicated tracker does it for you: it watches each tool's official releases, summarizes what changed in plain language, and pushes it to your phone. That is what the AI Drops apps do, one app per tool, so you get the curation of a newsletter, the speed of push, and per-tool focus without wiring anything up. For a deeper walkthrough of building a low-effort system, see our guide on how to keep up with AI tool releases, and browse the Guides hub for related tactics.

Bottom line

There is no universal home for the AI coding tool changelog, so the next best thing is a directory you trust plus a delivery channel that comes to you. Bookmark the official pages above for the tools you use, point an RSS reader at their feeds for breadth, and reserve push for the few releases you cannot afford to miss. If you would rather skip the setup, install Claude Drops, Open Drops, or Cursor Drops, or just keep our Claude, OpenAI, and Cursor changelogs open as a quick, summarized companion to each vendor's source of truth.