Create content from any GitHub repository

Paste any GitHub repository. Paragraph turns what you merge into a changelog your customers can subscribe to, with posts for X and LinkedIn and a short launch video.

Connect a private repo

Trusted by teams at

  • Coinbase
  • Farcaster
  • Stable
  • Base
  • Nodle

This week your team shipped 47 pull requests, and your customers heard about none of them. Every release could bring you customers. Paragraph reads what merged and leaves out the noise, writes it for customers rather than for Git, and once you approve it, publishes it to your website, email, X, and LinkedIn.

This video came out of a Changelog run. The Changelog agent can make one for each release you announce, alongside the article and posts.

A week of commits, in language your customers use

Paragraph reads what merged, leaves out what doesn't matter, and groups the rest by what actually changed for the person using your product.

main this week
  • a91c4e2 feat(webhooks): retry delivery with backoff
  • 7f30bd1 wip left out
  • 4c8e0aa fix(auth): drop stale session on refresh
  • 1d92f77 chore(deps): bump zod to 4.1.2 left out
  • b6ac310 perf(search): rebuild index on write
  • e40f1c9 fix typo left out
Changelog v2.14

Webhooks retry on their own now

  • Webhook deliveries now retry with backoff, so a short blip on your side no longer drops the event. #412

  • You stay signed in when a session refreshes mid-request. #418

  • Search comes back about twice as fast on large workspaces. #421

Published Emailed subscribers Posted to X and LinkedIn Launch video on X

Four steps, then it runs itself

Set it up once on a Friday afternoon. After that the draft is waiting for you.

  1. 1

    Connect the repository. Access follows the GitHub account you connect, so Paragraph reads what that account can read, and nothing else.

  2. 2

    Pick a rhythm. Weekly, every release, or only when you ask. Paragraph gathers the work merged since your last entry.

  3. 3

    Read the draft. Changes are grouped by what they do for the person using your product, with the pull requests linked underneath.

  4. 4

    Approve it. The entry publishes to your changelog, emails your subscribers, and posts to X and LinkedIn, video included.

One entry, everywhere your customers already are

Publish the changelog, email the people who subscribed, post to X and LinkedIn, and follow up on X with a short video. Each version is written for where it lands, not pasted into it.

X

@acme

Shipped this week: webhooks retry on their own, sessions survive a mid-request refresh, and search is about twice as fast on large workspaces. Full notes:

acme.com/changelog

LinkedIn

Acme · Company page

Three things shipped this week, and all three started as something a customer told us was slow or annoying. Webhook deliveries now retry with backoff, sessions hold through a refresh, and rebuilding our search index roughly halved query time on large workspaces. Notes and pull requests here:

acme.com/changelog

X

@acme

This week's release, in 22 seconds.

Why teams keep it running

Proof that you're shipping

Customers, investors, and candidates can all see the pace without you stopping to write an update.

Written for customers, not for Git

Each entry leads with what changed for the person using your product, and keeps the technical detail one click away.

It stays yours

Your changelog lives on your domain with your subscribers and your RSS feed. Export it or move it whenever you want.

Paragraph writes the first draft. You decide what your customers read.

See how approvals work

More agents

Each one starts from something you already have, drafts the work, and waits for your approval.

Frequently asked questions

What developers ask before they point Paragraph at a repository.

Read the docs

Point it at the repo you shipped from this week

Paragraph reads what merged and shows you the first entry. Nothing publishes until you approve it.

Connect a private repo