What it posts
7 kinds, 4 live the moment you invite itKindStateWhat it is
A release is out
On by default
npm has a new version and the changelog run has started. The gap between this and the finished page is usually half an hour.
The changelog is live
Always
The full read is published. This is the post beside this table, and the one every server gets.
npm's stable channel moved
Always
A version that shipped days ago is now what
npm install gives you. Usually nobody announces this anywhere.
Anthropic posted their own notes
On by default
Their notes land after the fact, sometimes days later. This one goes into the release's thread, or as a reply to the original post, and it never pings.
Anthropic edited the docs
Off until you opt in
Pages added, edited and removed across their published documentation, with line counts and a link to the diff.
Anthropic is having an incident
Off until you opt in
Every incident on
status.claude.com, from investigating through to resolved, with what it is affecting. This is the one thing the bot watches by itself rather than being told about. It covers every Anthropic service rather than Claude Code alone, and picking individual ones is not built yet.
The build is waiting on npm
Owner feed
The version is on the registry but the platform binary is not downloadable yet, so nothing can be read from it.
Three more kinds exist and none of them reaches a server: the waiting-on-npm card above, plus two pipeline health feeds. A server can never be subscribed to any of them by accident.
What you type
every one needs Manage ServerCommandWhat it does
/changelog set-channel
Announce new Claude Code releases in this channel. It checks it can actually post there before it accepts one.
/changelog config
Open the configuration panel for this server.
/changelog status
Show where announcements are going, every toggle, and whether the bot is connected right now.
/changelog latest
Show the most recent changelog announcement, just to you.
/changelog test
Post the most recent changelog to the configured channel, without pinging anyone. Pass threads: true to open one as well, so you know the bot can before a real release tries it.
/changelog disable
Stop announcing releases in this server. Reversible, and it forgets nothing else.
/changelog config opens the one panel, only you can see it, and every press re-checks Manage Server before it writes anything. Per-announcement channels opens a second view where any kind can be pointed at a channel of its own: releases in one, documentation edits in another, incidents somewhere nobody is trying to read. Anything you do not move stays on the default channel.
A Discord outage costs you nothing
written down before it is sentGuaranteeWhat it means
Durable queueEvery announcement is on disk before the pipeline is told it was accepted. A restart mid-fanout resumes and nothing is lost.
Backoff, then stopA transient failure retries at 30s, 2m, 8m and 32m. A permanent one is abandoned rather than hammered.
DeduplicatedEach release carries an idempotency key, so a pipeline retry cannot post the same release twice to five hundred servers.
Fast fanoutEight servers are posted to at once, inside Discord's own rate limit, and the queue drains from there.
It unsubscribes itselfDelete the channel or remove its permissions and the bot clears its own config instead of piling up 403s forever.
Nothing is recreatedSchema changes only ever add. A server's settings have never been dropped by a deploy and cannot be.
What it cannot do
it runs on the Guilds intent aloneThe permissionWhy it holds
NoIt cannot read your messages.Message Content is a privileged intent and this bot does not have it. There is no version of it that can see what anyone typed.
NoIt cannot see your member list.Server Members is the other privileged intent, and it is not requested either. It knows a role id you gave it and nothing about who holds it.
NoIt cannot ping everyone.There is exactly one place a mention can be built and it only ever names the single role you configured. There is no setting for
@everyone, and the code cannot build one.YesThree permissions.View Channel, Send Messages, Embed Links. Threads want a fourth and it is a separate, optional invite.
Three steps, about a minute
no dashboard, no account- Invite it. The link asks for the three permissions above and nothing else.
- Run
/changelog set-channel. Pick where the posts go. It refuses a channel it cannot post in and tells you which permission is missing. - Run
/changelog test. The most recent release lands in that channel, with no ping, so you can see it before a real one arrives.
Add it with threads instead if you want the discussion thread as well. Threads need Create Public Threads on top of the three. If you skip it, everything else still works and only the thread does not open.