ThreadPage
Start writing

All use cases

Release notes drafted from your pull requests

Every merged pull request files itself in a thread. On release day @GPT drafts the notes from them, and the release you publish lands where customers read it.

Start free trial

14 days of Pro. No card needed. Ends automatically. Choose to continue with Pro for $99.99 a year ($8.33 a month). See monthly pricing

Start writing
See plansSee the thread

At a glance

For
Maintainers and small teams who ship from GitHub.
You keep
Two threads: a feed of the repository’s pull requests, and Releases, shared by link with your customers.
Files itself
  • Every pull request in the feed as it opens, merges or closes.
  • Each release you publish on GitHub, with its notes, in Releases.
  • A draft of the notes from @GPT, on your own API key, when you ask.
The moment
On release day @GPT reads the merged pull requests in the feed and drafts the notes. You fix one line and publish, and the release lands in Releases, where customers read it.
Plan
Pro Customers read Releases through a link, without an account.

Before

Release day. The changelog is due, and 23 pull requests have merged since 2.3. You open each one again to work out what a customer would notice, then write it up in a hurry. The customers who asked for the CSV export find out it shipped from a reply to a support ticket.

Why a thread, not a CHANGELOG file

  1. The pull requests are already there

    Each one lands in the feed with its title, link and date as it merges.

  2. A first draft from the feed

    @GPT reads the titles of the pull requests merged since the last release, groups them for a customer and leaves out dependency updates.

  3. Customers read it where you link it

    Releases is shared with Anyone with the link. Each release you publish on GitHub appears there with its notes.

A thread, over time Example

Your workspace starts empty.

Work

invoice-app pull requests

Active

  1. Wed 21 Oct

    1. The feed fills itself as pull requests merge.

      via GitHub14:02

      Pull request merged: Add CSV export for invoices

      github.com/acme/invoice-app/pull/318

  2. Thu 22 Oct

    1. via GitHub09:40

      Pull request merged: Fix rounding in multi-currency totals

      github.com/acme/invoice-app/pull/321

  3. Fri 23 Oct

    1. via GitHub16:15

      Pull request merged: Bump dependencies

      github.com/acme/invoice-app/pull/324

  4. Tue 27 Oct

    1. Release day: one request in the feed, on your own OpenAI key.

      You10:05

      To @GPTReplied in 1 min

      @GPT draft the release notes for 2.4 from the pull requests merged since 2.3 on 6 October. Group them as New, Fixed and Changed, for customers, and leave out dependency updates.

    2. Its draft is a note, under the pull requests it read.

      From @GPT10:06

      Release notes for 2.4, a draft:

      New: export your invoices as a CSV file.

      Fixed: totals on multi-currency invoices are no longer a cent off.

      Changed: payment reminders go out at 09:00 in your customer’s time zone.

    3. You correct what it couldn’t know, publish, and the release files itself in Releases.

      You10:20

      Fixed the CSV line: the export is in the Invoices menu. Published 2.4 on GitHub with these notes.

      Releases · 27 Oct

It files itself. You read.

Your tools write into the threads you choose, with only the access you give them.

Script or API

  • Pull requests from GitHub

    Every pull request in the repository that is opened, ready for review, merged or closed becomes a note in the feed.

    Set it up

    AutomationAdd notes from another appGitHub pull requests

    1. In Settings → Connections → Automations, choose Connect an automation → Add notes from another app and name it GitHub: its notes will say so.
    2. In Adds to, choose invoice-app pull requests; in What it sends, GitHub pull requests.
    3. In the repository’s Settings → Webhooks, paste the URL and the secret, choose application/json and Pull requests.

  • Published releases, for customers

    Each release you publish becomes a note in Releases, with its name, link and notes. Customers read the thread through its link.

    In Releases

    via GitHub10:21

    Invoice app 2.4

    github.com/acme/invoice-app/releases/tag/v2.4.0

    New: export your invoices as a CSV file, from the Invoices menu.

    Set it up

    AutomationAdd notes from another appGitHub releases

    1. In Settings → Connections → Automations, choose Connect an automation → Add notes from another app. Name it GitHub releases, choose Releases and GitHub releases.
    2. In the repository’s Settings → Webhooks, paste the URL and the secret, choose application/json and Releases.
    3. In the Releases thread’s menu, choose Share…, set General access to Anyone with the link and send the link to your customers (see Sharing help).

  • The notes, drafted

    Write to @GPT in the feed. It reads the merged pull requests and answers with a draft, on your own API key.

    Set it up

    AI modelYour OpenAI or Anthropic API keyPro with Sync

    1. In Settings → Connections, open AI models, choose Claude or GPT, paste an API key from Anthropic or OpenAI and choose Connect. AI models need Pro with Sync turned on.
    2. In the feed, write @GPT, the release and what to leave out, then choose Send.

Limits

  • Adding the webhooks needs admin access to the repository.
  • A shared link is for the people you send it to: search engines don’t list it, so it doesn’t replace a public changelog page.
  • @GPT reads each pull request’s title and link, not its description or code: clear titles give a clear draft.
  • @GPT needs an API key from OpenAI, and the provider bills the key for every answer. In a thread you share, it answers only after you choose Allow here.
  • ThreadPage sends what the model reads to OpenAI with your key.

GitHub, GPT, Claude, OpenAI, and Anthropic are the names of their owners. ThreadPage is independent and not affiliated with or endorsed by them.

Start with one thread.

Start free trial

14 days of Pro. No card needed. Ends automatically. Choose to continue with Pro for $99.99 a year ($8.33 a month). See monthly pricing

Start writing
See plans

More use cases

  • The brag doc your repository helps write

    Your repository’s pull requests file themselves into a thread of their own. You note what git can’t see, and at review time your agent drafts from both.

    Pro pull requests and agents

  • An incident, written down as it happens

    Two lines whenever something changes, and each note keeps its minute. On Friday, @Claude reads the thread and drafts the postmortem’s timeline.

    Pro sharing and @Claude
All use cases