Changelog

Your Changelog agent reads your GitHub repositories and drafts a Web Article, X and LinkedIn posts, and a short video about what you shipped. It can also write an X Article and an email to your subscribers. Nothing publishes until you approve it.

Set it up during onboarding or from Changelog under Agents in the sidebar. Public repositories work without connecting GitHub. For a private one, choose Continue with GitHub during onboarding, or Connect GitHub on the Changelog page. Coming from the Changelog page on paragraph.com, you can pick a repository before you have an account, and Paragraph asks you to sign in when you choose Create Changelog.

Start a runCopy Anchor Link

On the Changelog page, type what you want to announce and choose Draft. Leave it empty and choose Pick for me to let the Changelog choose from what merged since the last run. When nothing new is worth announcing, it can pick older work you never announced that customers can still use, reaching back up to six months. You can also start from one of your Ideas: choose one below the box, pick it from Idea in the box, or type @ and pick it by name.

For you lists anything waiting on you, with the count beside it. See runs opens every run, under three tabs. Active holds runs you haven't scheduled or published anything from, newest first. A run moves to Published once you schedule or publish any piece of it, even with other drafts still waiting, and that tab lists runs by when they went out. Each run's menu has Regenerate and Archive, the same as on the run itself. An archived run moves to Archived, where Bring back returns it. An idea whose only drafts you archived counts as unwritten again, so the Changelog can pick it for a later run.

On a paid plan, the Changelog writes when something ships. It checks what your team merges every 30 minutes. Once a change has been quiet for 12 hours, the Changelog's editor decides whether it's worth announcing now, or holds it back, for example to go out with other small changes later. It starts at most one run a day and three a week, between 8 a.m. and 8 p.m. in your timezone. While ideas from a connected data source we've set up for you are waiting, like benchmark results, it skips the 12-hour wait and can start up to five runs a day and fifteen a week, one at a time. A run that fails for a passing reason, like GitHub being busy, tries again on its own and doesn't use up the day's run. To run it only when you choose, turn off Run automatically. On the Free plan, a Changelog runs only when you choose Run now. If your workspace moves to Free, its Changelog stops running on its own.

Review a runCopy Anchor Link

A run's page lists every piece it makes, grouped by day, with a status for each. Pieces appear as they're written, so you can start reading the Web Article while the social posts are still drafting. Pick a piece to see it as it will go out, then choose Edit to change the words, or change its account or time. Why now explains which story the run picked and why.

To have Paragraph make the change instead, choose Ask to change at the top of the run, next to its menu, and type what you want in the box that opens at the bottom of the page. Paragraph knows every piece in the run and which one you have open when you send, so "shorten this" means the piece on your screen. The box stays open as you move between pieces, and each ask goes with the piece you're looking at. You can also ask for several pieces at once, like "add the feature screenshot to the Web Article and the first X Post." It edits the drafts in place, and the list of pieces shows which ones it's changing as it works. A pill above the box shows how your last ask went and how long it took. Choose it to open the whole conversation beside the page.

It can also change the Web Article's images. Ask it to "tweak the 2nd image in the Web Article" to keep that image and change one thing about it, to "regenerate the cover" for a new one, or to add an image after a heading you name. The same designer that made the run's images makes the change, so a tweak keeps the image's design, including fixing words drawn in it, and a new image matches the others. A change to an image takes a few minutes. Images count in reading order, and the cover isn't counted. Attach an image to your message to show it what you want. It changes only the image you name, so the rest of the Web Article stays as it was, and any other piece using the same picture keeps it. The one exception is a social post still showing the Web Article's cover, which changes along with it. Ask for options instead, and it shows you a few without changing anything.

Ask for an image without naming a placement, such as "make an on-brand image for this launch", to get an image in chat without changing any piece. Edits with the original design file keep element and text sizes unless you ask to resize them or change the typography. Images without a design file are redrawn first, so their appearance may differ.

The same goes for the X and LinkedIn posts, the email, and the X Article. Ask it to "put a diagram of the new flow on this post" or "give the X Article its own cover", and it makes the image in your brand and saves it on that draft. A change to a draft's image keeps its design, the same as in the Web Article.

Asking for "a new X Post" or "another LinkedIn post" adds a separate draft and keeps the one you're viewing. The new draft uses the account of the post you're viewing on that channel, unless you name another account. Paragraph confirms which account the draft will publish from. To change the post you're viewing instead, ask to rewrite or change it.

It never publishes or approves anything, and a piece you already approved needs your approval again once its words or images change. It can't change a piece that's already out. Use each piece's account and time controls to check where and when it will go out before approving.

The Web Article goes to your website only. When Newsletter is on, a major release also gets an Email piece made from the Web Article, with its own subject and time. You can edit the email, approve it, or skip it without touching the Web Article, so you can publish the Web Article without emailing anyone, or email your subscribers without publishing it.

A smaller update goes to your site without an email, so your subscribers hear about what matters most, and the run says No email this time. A run you start with your own focus always makes the email.

Choose + beside Ask to change to create an email, social post, image, or video. Email copies the Web Article into an editable draft. Something else… opens the run's chat, and it's what a run with no Web Article offers. Pieces added to the same bundle from Content also appear in the run and join its scheduling and recipient checks.

The size of the update shapes the rest of the run too. A major release gets the full set: a detailed Web Article, an announcement and follow-ups on each channel, and the video. A smaller update usually gets a short Web Article and one post per channel that stands on its own, sometimes with an image. When video is on, every update with an X or LinkedIn announcement gets a short video to lead it. Your run instructions and Editorial context come first, so ask for more when you want it.

To change the video, open it, choose Ask to change, and say what you want, like "make the background blue". Paragraph edits the same video, which takes a couple of minutes. To start over, ask Paragraph to replace it, like "replace the video with one about the scheduling dialog", or choose Rebuild video. If the run skipped its video for a small update, asking for one makes it. The video you have stays until the new one is ready. The announcements that carry it move to the new video unless they're already out, and if you approved one, it needs your approval again.

Newsletters attached to a video's saved cut also follow its revisions within the same run, including additional videos. Approved newsletter sends return for review. Messages already sent or sending keep their reviewed cut.

To keep the video and make another, ask for one more, like "add a second video about the scheduling dialog". It takes a few minutes and shows up under Media as its own piece. The video you have and the announcements that carry it stay as they are, and the new video isn't put on any post. Adding a video needs a plan that includes video generation.

To remove a video from the run, ask Paragraph to remove it and confirm the review it shows. This removes its membership in the run and bundle, keeping the reusable video project, source, renders, and library files. A video that's still rendering or has an approved delivery must stay until that work is stopped.

Suggested timesCopy Anchor Link

When you start a run with Run now, your Changelog agent suggests a time for each piece as soon as the Web Article and social posts are written. The video renders last and can take a while, so it doesn't wait for it. You can approve those pieces right away, but Automatic approval waits until the run finishes, so the launch doesn't go out without its video. A run that starts on its own, on the Changelog's schedule or from an idea, waits for the video and times the whole launch once it's ready, so nothing is approved without it. If the video can't be made, the launch is timed without it. When the video is ready, it leads your X and LinkedIn announcements, since a video reaches more people than a link or a still. On X the Web Article link moves to a reply, and on LinkedIn it stays in the first comment, with the video in place of the cover. If you've already approved an announcement, given it an image of your own, or made it a thread, it goes out as it is. Follow-up posts don't carry the video. Hover over a piece's time to see why it was picked. It plans around everything already booked in your workspace, so two pieces never go out from the same account at once, and it takes your run instructions and Scheduling notes into account. It also sees when your past newsletters got the most opens and clicks. It doesn't see engagement on X or LinkedIn.

By default, the launch goes out together on a Tuesday, Wednesday, or Thursday at 11 a.m., at least a day after the drafts are ready so you have time to review them. The launch is the Web Article, its email, and the X and LinkedIn posts that announce it, and it goes out together: the Web Article first, then its posts a minute later, once it's live. A launch post you set an hour or more away from the Web Article keeps its own time. An update with no Web Article launches with its posts. An X Article follows on the next weekday, and follow-up posts come about one a day after that, Monday through Friday, pausing for the weekend. Each publication gets one launch a day and each account one original post a day, counting what you've approved or placed yourself across your workspace. Times other runs only suggested don't take a day. When a week is already full, the launch moves to the next week with an open day, and its follow-ups come after it. Emails to your subscribers stay at least 24 hours apart. When we don't know where your readers are, times are set for US Eastern time. These are starting points, so a note like "nothing on Fridays" or an instruction in the run changes them. To post on a weekend, name the day ("launch on Saturday morning"). Timing like "two days after the Web Article" moves to Monday when it lands on a weekend.

Suggested times are proposals, not bookings, so they stay current. Each time you open a run, the times you haven't approved are checked against your calendar as it is then. If anything they were planned around has changed (another piece was approved or went out, a piece was added to or removed from the run, an account was connected, or a time is about to pass), the run picks fresh times in your timezone, and its times read Picking times… until they're ready. Times you approved or set yourself stay as they are. You never have to ask for times: if picking them fails, the run tries again, and again the next time you open it.

Click a time to move it to a nearby slot or set your own day and time. The Web Article sets the launch: moving it moves the launch posts with it (each keeping its time from the Web Article) and the follow-ups after it, on the same weekdays and at the same times of day. Moving any other piece moves just that piece, so a launch post can go a couple of hours after the Web Article. In a run with no Web Article, its first piece sets the launch.

Approve and publishCopy Anchor Link

You review and publish a run right on its page. The list on the left shows your launch, then every other piece by the day it goes out. Each piece's mark is a check: click it to leave that piece as a draft, and anything that links to it or shares it stays back too. A run's Web Article can't be left out, since the launch is built around it. If an X or LinkedIn account isn't connected, the bottom of the list says so, with a way to connect it.

If the run includes an email and nobody is subscribed yet, that email is held back the same way: the newsletter shows No recipients at the top of the piece, and the publish button asks who it should reach before it schedules anything. Add recipients takes addresses typed or pasted one per line, or choose Add from a file to pick a .csv or .txt list. Leave it out keeps the email as a draft and publishes everything else.

Adding recipients never sends anything: the email still waits for the publish button, like every other piece. This takes up to 100 addresses at a time. For a bigger list, ask Paragraph to import it first, then come back and publish the run. Once someone is subscribed, the email's row shows how many people it reaches.

The button at the top right says what happens: Schedule 7 pieces books everything checked at its time. To send something right away, choose Now from its time at the top of the piece. Now on the Web Article sends the launch now and moves the follow-ups to the same weekdays after it. Now on any other piece sends just that piece, unless it waits on a piece that isn't out yet, like a post that shares another. Nothing goes out until you press the button, which then reads something like Publish 1 now, schedule 6 and asks before it sends.

The menu at the top right has Unschedule all, which takes every booked piece off the calendar, Archive, which tidies the run away once you're done with it, and Regenerate, which starts a new run on the same idea from scratch. The new run takes the earlier run's place on the calendar, so you don't get two launches about the same thing. If any of the earlier pieces has already gone out, they stay, and the new run is scheduled as a launch of its own. See Calendar.

You don't have to wait for the video either. Once the written pieces have times, you can approve them while the video renders. When the video is ready, it joins your X and LinkedIn announcements if you haven't approved them yet. Nothing you already approved or published changes.

When you give us your website, your first run starts by learning your brand from it: your visual brand, a profile of your company, and your brand voice. That usually takes a minute or two, and it means the first Web Article, social posts, and images already look and sound like you. The bar at the top of the dashboard checks off each one as it's saved, and View brand opens them under Brand.

Your first run doesn't make you wait for everything. As soon as the Web Article and the X and LinkedIn posts that announce it are written, the run leads with Publish all three so your first launch goes out together, while the rest of the run (follow-up posts, and the video when it makes one) is still being written. Until your launch goes out, the run shows just those three pieces and their images, with the rest under Coming later. If the video finishes before you publish, it joins your launch on the X and LinkedIn announcements, with the Web Article link in the X reply. When the rest is ready, you get an email, and it waits on the run with suggested times like any other run.

Publishing everything at once lists where each piece goes. If X or LinkedIn isn't connected yet, choose Connect on its row: it opens the sign-in in a new tab, and the row picks it up when you come back. If you'd rather not connect now, publish what's connected and come back for the rest. When the pieces are live, the dialog links each one and shows what the run still has coming.

If suggested times pass before you approve them, the run picks new ones the next time you open it.

If a step fails, Retry step runs just that step again.

SettingsCopy Anchor Link

Open the gear on the Changelog to change:

• What it makes. Switch the Web Article, social posts, X Article, video, and Newsletter on or off, as long as one stays on. The Web Article starts on. With it off, the run still researches and writes the story and makes your other pieces from it, but nothing goes to your website, and no post links to an article. If only Newsletter or video is on, a smaller update can finish with nothing to review. Newsletter starts on and makes an email for major releases. First runs and runs with your own focus can make one too. The email waits for your approval before it sends. X Article starts on for new Changelogs. It needs X Premium on the connected account, so without it the Article stays a draft and isn't published.
• Repositories. Choose which repositories it reads: up to three from one GitHub account or organization, like a private app and the public SDK it's built on. If one is missing, choose Manage GitHub access.
• Additional context. Who to write for, product names, a call to action, or words to avoid. Pieces are written for new customers (people who don't use your product yet) unless you name a different reader here, like "Write for developers integrating our API."

How it worksCopy Anchor Link

The Changelog reads what merged in your repositories, and what your team records in Linear if you've connected it, and groups related work into ideas. Its editor picks the story most worth telling that it hasn't covered yet, and may decide nothing is worth announcing yet. It then reads the code behind that story, checks that it's actually available, and writes in your saved voice. Where a picture explains a change better than words, like a new workflow or a before and after, an image designer draws it in your brand and places it in the Web Article with a caption. It designs the cover too. When the change is something your customers see on screen, the designer can rebuild that screen from your code, and it may attach an image to an X or LinkedIn post that stands on its own. You can replace or remove any of them in the editor. Before a draft reaches you, it opens every link to confirm the page exists and checks each claim about your product against what it read. Its access to GitHub is read-only. While it researches, it can also look things up in your connected tools, using only the tools that read. It uses a tool that makes or changes something, like a video service, only when your run instructions ask for it. For an idea from a registered custom data source, the release data is the evidence for its numbers, and the Changelog can read the source again, for example to compare with an earlier release. It can write about an internal source's data too, in its own words, leaving out names and anything customers can't see yet.