AI coding tools ship at a pace that makes tracking changes genuinely difficult. Claude Code drops a new version and the changelog is buried in a GitHub release. Codex updates land without fanfare. Gemini CLI changes flags between versions and the only documentation is a commit message. Changelogs.info exists because I got tired of checking four different repos every week to find out what broke or what's new.

The problem

These tools move fast. A new Claude Code release might land three times a week. Each one has release notes somewhere — GitHub releases, Discord announcements, blog posts, changelog files in the repo. No single place aggregates them. If you're using multiple AI coding tools (and most serious developers are), keeping up is a full-time information management problem.

Beyond raw changelogs, there's the reference problem. What's the flag for enabling plan mode? What environment variables does Claude Code respect? What's the config file format for OpenCode? This information exists, but it's scattered across docs, README files, and GitHub issues. I wanted one place where I could look up "how do I configure X in tool Y" without a 10-minute search.

How it works

The site pulls changelog data from GitHub's releases API. Each tracked tool has a configured source — org/repo, release tag pattern, parsing rules for the release notes format. A background polling job runs periodically, pulls new releases, parses the notes into structured data, and updates the site's content.

The cheatsheets and config references are manually curated but structured for fast lookup. Organized by tool, then by topic (configuration, flags, environment variables, keyboard shortcuts). Designed to be the page you keep open in a tab while you work.

The design matches the neo-brutalist aesthetic of the rest of my projects — high contrast, aggressive typography, sharp edges. Different site, same visual DNA.

Technical approach

Built with Astro, same as cyperx.dev. Static generation with data pulled at build time from the GitHub API. Tailwind for layout. Deployed to Cloudflare Pages. The architecture is deliberately simple — no database, no server, no authentication. Just a static site that rebuilds when there's new data.

The GitHub API rate limits are manageable with reasonable polling intervals. Each tool's releases endpoint gives structured changelog data that parses cleanly into the site's content format. The build step fetches fresh data, generates pages, and deploys. Total build time is under a minute.

Current status

Live at changelogs.info. Tracking Claude Code, Codex, Gemini CLI, and OpenCode. Cheatsheets are growing as I document the tools I use daily. The core functionality — changelog aggregation and display — is solid. I'm expanding the cheatsheet coverage and adding config reference pages for each tool.

• Astro — Static site generation with dynamic data at build time.
• Tailwind — Layout and utility styles.
• GitHub API — Data source for release notes and changelogs.
• Cloudflare Pages — Hosting with automatic deploys from git push.