Every merge, on tape.

releasetape records every pull request your team merges. It mutes the noise, labels what matters, and plays it back as a changelog for your users, notes for your engineers and a read-ahead for whoever plans what's next.

Start with GitHub Hear a real changelog
brainful/web, main branch WK40 SUN 14:02 3 tracks, always recording
Track
MergesEvery pull request, labeled as it lands. Maintenance is muted.
R
ReleasesWhat users hear.
Read-aheadWhat it points to.
Replaying the week behind a real Brainful release. Tape runs right to left. Muted clips stay out of the changelog and go to internal docs.

One recording, three mixes.

Front of house, the stage monitors and the archive all take the same tracks and mix them differently. releasetape does the same with your merges, so the changelog, the docs and the plan never drift apart.

Front of house

For your users

A public changelog at your address, with RSS, email and an embed for your app. It only plays what a customer would notice.

Inline AI, unified activity and recoverable workAsk AI directly from your workspace, follow activity in one responsive view, and restore work after it has been discarded.
Brainful changelog, 4 October
Monitors

For your engineers

The band hears everything, muted tracks included. Architecture notes, decisions and follow-ups, kept current as the code changes.

agent_stream.py owns all streaming.
Callers: AskCommand, ScoutPanel.
Risk: chunk order untested on retry.
Next: shared backoff in transport.
The archive

For what's next

Every session is kept. Played back over weeks, it shows where effort goes, what keeps breaking, and which themes are ready to ship.

Auth has had four partial fixes in six weeks, each in a different place. One pass on sessions would likely close all four.
Example read-ahead

Pull any week off the shelf.

The tape never stops, so nothing is lost between releases. These are the last 13 weeks of a23one's own products, boxed and labeled by releasetape.

Track sheet
a23one,
Released to users

    What changed
      In one line

      Real, unedited output. Click a box or use the arrow keys to pull another week.

      Patch in once.

      first

      Install the GitHub app

      Read-only access to the repositories you choose. It takes about a minute and never writes back.

      then

      Merge as usual

      Same branches, same reviews, same pace. There's no form to fill in and no new step.

      from then on

      It's always recording

      Minutes after each merge the changelog, team notes and read-ahead are updated. Edit anything, any time.

      Questions from the crew.

      Does releasetape need write access to my repos?

      No. The GitHub app asks for read-only access to code and pull requests. releasetape never pushes commits or changes your branches.

      Can I edit what gets published?

      Yes. Every release lands in your dashboard, where you can change the title, the text or the change type before or after it's published.

      Does it work with private repositories?

      Yes. Your public changelog only shows what you publish. Source code is never exposed.

      How does it tell user-facing work from maintenance?

      It reads the actual diff, including file paths, change types and surrounding code, and judges each change by its effect on users. CI config, dependency bumps and internal refactors are muted from the changelog and kept for your internal docs.

      What about my existing history?

      When you connect a repository, releasetape backfills its history, so your changelog is complete from the first day.

      Hit record once. It never stops.

      Start with GitHub

      Free to start. Read-only GitHub access.