Weekly Changelog Agent with OpenClaw

Three GitHub reads, one Slack message, five fixed sections, once a week. None of that needs a heavyweight harness, and OpenClaw is simple to point at a job with edges this clear. NoClick runs it on Friday afternoon whether or not the team remembered it exists.
Loading preview…
Free to start · guided setup · switch agents any time.

Live demo

Watch it work before it's live

Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.

Friday 15:00 changelog tick

Friday schedule#changelog

It is Friday 15:00 in Berlin. Twenty three pull requests merged across the api and dashboard repos this week, including one that renames a field in the settlement webhook payload and one that removes a reporting endpoint two customers still call. The audience is support and the twelve merchants on the beta.

What you'll need

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect GitHub

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. Repo context

    Which repositories to cover, who reads this changelog (customers, support, the whole company), and who to tag when a repository goes silent or a call fails.

  4. Changelog style

    How your changelog should read: how technical to get, whether dependency bumps and internal refactors make the cut, and how long it can run before people skim.

  5. Runs on OpenClaw

    Preselected for this page — connect your OpenClaw account during setup, or switch to NoClick's built-in models with one click.

  6. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

A considered pairing

Why OpenClaw for this agent

Small job, fixed shape

Section names, ordering and the one-sentence-per-line rule are all written down. The harness follows a spec rather than designing one.

Friday without a volunteer

Changelogs get written in weeks somebody has time. A scheduled hosted run removes that dependency entirely.

Good to know

Before you fork

What if a repository goes quiet?

A repository returning nothing for the week is named in NOT SEEN with the reason, and the owner from your repo context gets tagged. That is deliberate, because silence usually means a broken credential rather than a calm week. You find out on Friday instead of at the next release.

Other editions

Run it with a different agent

claude-codeClaude CodeOpenAICodexopencodehermesMore OpenClaw agents

Make it yours

Put Weekly Changelog Agent to work on OpenClaw.

Free to start. Guided setup, a staged test run, and a workflow you can change at every step.