Catching up with Merged
Your agents and your colleagues merge a lot of code. Merged shows what was merged in the project’s repository, one post per stack, each with a one-line summary. Read the posts you care about, ask about a change, and mark them read.
Merged never posts anything to GitHub. It only reads. It is desktop only and not on the phone.
Before you start
Merged follows the GitHub repository of the window’s project, taken from its git remote. There is nothing to configure. It lists merges with gh, so GitHub CLI must be installed and signed in. If it isn’t, the section says so and offers Try again.
1. Open Merged
Select Merged in the sidebar, the fifth section (⌘5). A badge on it counts the posts you haven’t read.
The header shows the repository, how many posts are unseen, and since when merges are shown. The list refreshes every 5 minutes, and when you select Refresh in the sidebar.
2. Read the timeline
Each post is one stack of merged PRs. A PR that isn’t part of a stack gets a post of its own. Posts come in the order they were merged. Nothing is ranked or hidden.
A post shows:
- The title of the stack’s bottom PR, who wrote it, when it was merged, and how many PRs the stack has.
- A one-line summary of what the stack does.
- The stack’s PRs as links, the PRs of the stack that are still open, and the size of the change.
Select More for a longer summary. It is written the first time you open it, and kept.
Bots’ merges show as one line, tagged bot. They are never counted or summarised.
The first time you open Merged, it shows the last 24 hours. After that, a post stays until you read it. Read posts and bots’ posts drop out 7 days after their last merge.
3. Mark posts read
A post is read only when you say so. Scrolling, opening More, asking about it or opening it in the Review Room doesn’t mark it.
- Select ✓ Read on a post.
- Select Mark all read in the header for every post.
Read posts move below ”— seen —”, collapsed. When another PR of a read stack is merged, the post is unseen again and says what is new, for example “New since you read: #42”.
4. Ask about a change
Type a question into the post’s text box, Ask about this change…, and press Enter. The first question starts a companion for that post. It is a read-only agent: it can read the post’s diff and check out the code at its head, and it answers in the post’s thread. It can’t edit, post or comment on GitHub.
The companion uses the same provider and model as the Review Room’s Companion. It stops after 30 minutes without a question, or when you mark the post read. The thread stays, and your next question starts it again.
5. Open the Review Room
To read the change itself, select Review Room on the post. It opens on all PRs of the stack, inside Merged. Select ← Merged to go back to the timeline.
Summaries and cost
The summaries are written by models you can choose in Settings → Default Model: Post summary for the one-liner, and Post More for the longer summary. Each summary costs tokens once and is then kept. The longer one is written only for the posts you open with More.
If a summary fails, the post says so. Select Retry summary.