ThreadPage
Open threadsBack to threadsBack to searchBack to draftsBack to trashBack to archiveBack to imagesBack to shared placesBack to storageBack to settings

All 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.

See the thread

At a glance

For
Engineers before a review, and anyone asked what they shipped this year.
You keep
Two threads in a Work folder: a feed of the repository’s pull requests, and What I did in 2026 for your own notes.
Files itself
  • Every pull request in the repository you work in most, as it opens, merges or closes, in the feed.
  • A draft of your review from Claude Code or Codex, when you ask.
The moment
On 1 December your reminder brings the thread back, and your agent reads the year and drafts the review. You spend the evening adding what only you saw, not digging through git log.
Plan
Pro Try it free for 14 days, no card needed.

Before

In January you promised yourself a brag document. It lasted until March. Now the self-review is due on Friday, and you rebuild the year from git log, chat search and memory. The pull requests are there; the week you spent getting Sam through his first on-call is not.

Why a thread, not a brag document or git log

  1. Half of it is already written

    Every pull request lands in the feed with its date and link. In your thread you reference yours and add the line git can’t hold: why it mattered.

  2. The human work has a place

    Mentoring, an incident you ran, a thank-you from support: a dated note, with a screenshot if you have one.

  3. A draft, not a blank page

    An agent you connect reads both threads and adds a draft as a note. With Read only it drafts in the chat instead.

A thread, over time Example

Your workspace starts empty.

Work

What I did in 2026

DoneSharedRuth

  1. Mon 12 Jan

    1. Start the year’s thread once, and set Remind me… for 1 December.

      You09:05

      One thread for the year, next to the feed from the payments repository. I note what the pull requests don’t show.

  2. Wed 4 Mar

    1. The merge filed itself in the feed; you reference it and say why it mattered.

      You16:30

      payments-api pull requests · 4 Mar

      The retries took three weeks: the provider’s sandbox drops about one event in fifty, so I built a replay tool first. Missed-payment tickets fell from about ten a week to one. #impact

  3. Fri 22 May

    1. The work that leaves no commit.

      You18:10

      Sam’s first on-call week. Paired with him on Monday; he ran Thursday’s incident on his own. #mentoring

  4. Wed 17 Jun

    1. A thank-you, kept before the chat scrolls it away.

      You09:40

      From Ines in support, after the refund fix:

  5. Thu 10 Sept

    1. The numbers, while you still have them.

      You10:15

      payments-api pull requests · 9 Sept

      Ledger moveResult
      Invoices moved1,184,302
      DowntimeNone
      RollbacksOne, in staging

  6. Tue 1 Dec

    1. You ask; the agent reads the year and drafts.

      via Claude Code09:12

      Draft self-review, from this thread and the feed:

      ThemeBehind it
      ReliabilityWebhook retries #1184; the ledger move #1312, with no downtime
      MentoringSam’s first on-call week
      SupportThe refund fix, and the thanks from Ines

    2. You add the part only you saw, and share the year with your manager.

      You09:40

      Added what the thread couldn’t know: the ledger move was my proposal, from a design doc in February. Shared this thread with Ruth at Can view.

  7. Fri 4 Dec

    1. Done. Archive it in January, and Search still finds it for the next promotion case. Done

      You17:30

      Review done with Ruth. 2027 gets a thread of its own.

It files itself. You read.

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

Custom connections and API

  • Pull requests from GitHub

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

    In payments-api pull requests

    via GitHub16:12

    Pull request merged: Retry failed webhooks with backoff

    github.com/acme/payments-api/pull/1184

    Set it up

    Custom connectionAdd endpointGitHub pull requests

    1. In Settings → Connections, choose Add connection → Automation or API and name it GitHub: its notes will say so.
    2. Choose Add endpoint, payments-api pull requests and GitHub pull requests.
    3. In the repository’s Settings → Webhooks, paste the URL and the secret, choose application/json and Pull requests.

  • Your review, drafted

    Ask Claude Code or Codex to read both threads and add a draft of your self-review as a note.

    Set it up

    Assistant connectionFull workspace accessSelected folders and threads: Work

    1. Connect Claude Code or Codex in Settings → Connections (see Connections help) and choose Customize access → Selected folders and threads → Work. With Read only it drafts in the chat instead.
    2. Ask: Read What I did in 2026 and my merged pull requests in payments-api pull requests, and draft my self-review in three themes, with the notes behind each. Add it as a note in What I did in 2026.

Also

An agent you haven’t connected can still read the thread: Copy as text in its menu copies it at once, on Free too, and sends nothing anywhere.

Limits

  • Adding the webhook needs admin access to the repository.
  • No admin rights? Whoever has them can add the webhook: the URL only adds notes to that one thread.
  • ThreadPage doesn’t run your agents: they run where they always do.

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

Start with one thread.

Open threads

Free in your browser. No account needed to start.

More use cases

All use cases