# 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. ## 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 2025 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 · From USD 7.99 a month. 14 days free, no card. ## 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 ### 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. ### 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. ### A draft to start from 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 Your workspace starts empty. ### What I did in 2025 Work · Done · Shared · Ruth #### Mon 13 Jan *Start the year’s thread once, and set Remind me… for 1 December.* **You** · 09:05 One thread for the year, next to the feed from the payments repository. I note what the pull requests don’t show. #### Tue 4 Mar *The merge filed itself in the feed; you reference it and say why it mattered.* **You** · 16: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 #### Thu 22 May *The work that leaves no commit.* **You** · 18:10 Sam’s first on-call week. Paired with him on Monday; he ran Thursday’s incident on his own. #mentoring #### Tue 17 Jun *A thank-you, kept before the chat scrolls it away.* **You** · 09:40 From Ines in support, after the refund fix: [Image: Screenshot of the thank-you message] #### Wed 10 Sept *The numbers, while you still have them.* **You** · 10:15 ↳ payments-api pull requests · 9 Sept | Ledger move | Result | |---|---| | Invoices moved | 1,184,302 | | Downtime | None | | Rollbacks | One, in staging | #### Mon 1 Dec *You ask; the agent reads the year and drafts.* via **Claude Code** · 09:12 Draft self-review, from this thread and the feed: | Theme | Behind it | |---|---| | Reliability | Webhook retries #1184; the ledger move #1312, with no downtime | | Mentoring | Sam’s first on-call week | | Support | The refund fix, and the thanks from Ines | *You add the part only you saw, and share the year with your manager.* **You** · 09: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. #### Thu 4 Dec *Done. Archive it in January, and Search still finds it for the next promotion case. Done* **You** · 17:30 Review done with Ruth. 2026 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. [Script or API](https://thread.page/help/connections/custom.md) ### 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 **GitHub** · 16:12 Pull request merged: Retry failed webhooks with backoff github.com/acme/payments-api/pull/1184 #### Set it up Automation Add notes from another app GitHub 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 **payments-api 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. ### 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 Coding agent Read and add Selected folders and threads: Work 1. Connect Claude Code or Codex in **Settings → Connections → Coding agents** (see [Coding agents help](https://thread.page/help/connections/coding-agents.md)) 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 2025 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 2025.” ## Also An agent you haven’t connected can still read the thread: **Copy as text** in the thread’s menu copies all of it, ready to paste. That works on Free too, and ThreadPage sends nothing. ## 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. 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. [Start free trial](https://thread.page/auth/sign-up?returnTo=%2Fapp%2Fsettings%2Fbilling%23trial) 14 days of Pro, no card. Then from USD 7.99 a month. [Start a thread](https://thread.page/app) More use cases ### [Notes on each of your reports](https://thread.page/use-cases/manager-notes.md) A private thread per person: 1:1s, wins, worries and what each of you promised. When reviews come, the year is already there. Free · nothing to set up ### [Where your coding agent stopped](https://thread.page/use-cases/agent-work-log.md) Claude Code hits its limit on Monday afternoon. You write to @codex, and it carries on from the pinned plan and the last note. Pro · Claude Code and Codex [How to keep a work log](https://thread.page/guides/work-log.md) [All use cases](https://thread.page/use-cases.md)