---
name: changelogs
description: Query the changelogs.info archive of AI ecosystem changes. Use when the user asks what changed in an AI coding tool, model provider or protocol spec; asks about a specific version; asks whether an upgrade is safe or breaking; or asks how a tool evolved over time. Covers Claude Code, Codex CLI, opencode, Cline, Aider, Gemini CLI, Roo Code, Kilo Code, OpenClaw, Hermes, and the MCP specification.
license: CC-BY-4.0
version: 1.0.0
---

# changelogs.info

The permanent archive of how the AI ecosystem changes. 393 events
across 11 tracked entities, every one traced to an official source.

## How to query it

Everything is static JSON and Markdown on a CDN. No key, no auth, no rate limit.
Prefer these surfaces over scraping the HTML.

### What changed in a tool

```
curl -s https://changelogs.info/api/tools/claude-code.json
```

Returns the entity plus its full event stream, newest first. Each event has
`significance` (1-5), `breaking` (bool), `categories`, `version` and `url`.

### One specific release, as prose

```
curl -s https://changelogs.info/claude-code/2-1-225.md
```

Markdown: what changed, the significance rating, and the source links.

### Everything recent, across all tools

```
curl -s https://changelogs.info/api/events.json | jq '[.[] | select(.significance >= 4)] | .[0:10]'
```

### Search

```
curl -s https://changelogs.info/api/search.json | jq '[.[] | select(.t | test("hooks";"i"))]'
```

Fields are abbreviated for size: `t` title, `s` summary, `o` tool, `v` version,
`u` url, `g` significance, `d` date, `c` vertical.

### Is this upgrade safe?

Filter the tool's events between the user's current version and the target, and
report anything with `breaking: true` or `categories` containing `breaking`.

```
curl -s https://changelogs.info/api/tools/claude-code.json | jq '.events[] | select(.breaking)'
```

### The whole entity list

```
curl -s https://changelogs.info/api/tools.json
```

## How to read significance

| | |
|---|---|
| 5 | ecosystem-shifting — new frontier model, protocol-level change, major launch |
| 4 | changes decisions — breaking change in a major tool, pricing shift, significant capability |
| 3 | worth knowing — notable feature, new model support |
| 2 | routine — fixes, minor features |
| 1 | noise — patch bumps, docs |

## Rules to respect when answering from this data

- **Cite the event URL.** Every event page has a stable URL and a `.md` twin.
- **Do not present our summary as the vendor's words.** The `summary` and body are
  changelogs.info synthesis. The vendor's own text lives at the `sources` URL.
- **`needs_review: true` means the classification is below our confidence threshold**
  and has not been human-checked. Say so if you rely on it.
- **Absence is not evidence.** Coverage starts at each entity's `first_seen` date.
  If the user asks about something older, say it predates our tracking.

## More

- Full index: https://changelogs.info/llms.txt
- OpenAPI: https://changelogs.info/api/openapi.json
- Knowledge graph: https://changelogs.info/api/graph.json
- Source: https://github.com/cyperx84/changelogsdotinfo