fix(clients): move settled pinned threads into the settled section

[t3dotgg]

Pinned threads stayed at the top after their pull requests merged or they became inactive.

Web, desktop, and mobile now place automatically settled pinned threads in Settled. Snoozed threads still stay hidden until they wake.

Model: GPT-5.6 Sol
Harness: Codex

---

Note

Medium Risk
Changes sidebar thread classification on web and mobile, which can move previously pinned rows into Settled and affect how users find them.

Overview
Pinned threads no longer stay at the top after they auto-settle. After snooze, settlement is checked before pinning, so inactive or merged-PR threads land in Settled even if pinnedAt is set. Snooze still hides them until they wake.

Web and mobile share this order. The pin glyph still shows on settled/slim rows (isPinned from pinnedAt), and mobile slim menus include Unpin. Docs and pinnedAt comments match: pins keep active threads on top, not settled ones.

If Auto-settle merged threads is off, a pinned merged thread stays a pinned card.

^{Reviewed by Cursor Bugbot for commit 00b1450. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Move settled pinned threads into the settled section in Sidebar and ThreadListV2

• Adjusts thread bucketing precedence in threadListV2.ts and Sidebar.tsx to evaluate settlement before pinning, so settled pinned threads go to the settled section.
• Updates ThreadListV2Row and SidebarThreadRow to derive pin state and menu actions from thread.pinnedAt instead of a section prop, keeping the pin marker visible across sections.
• Risk: Alters thread classification order in buildThreadListV2Items and Sidebar; any code assuming pinned threads always remain in the pinned section may break.

^{Macroscope summarized 00b1450.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0feeef2f-3080-4531-8c0c-876e90177761

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.4 KiB	13.4 KiB	−8 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−3 B (−0.0%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.0 KiB	55.0 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	13.4 KiB	13.4 KiB	−1 B (−0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−2 B (−0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	55.8 KiB	55.8 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 4d12e52 · PR result: 00b1450 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 65033b9. Configure here.}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[macroscopeapp]

One finding: the new pinned-vs-settled ordering leaves pinned rows without any in-row pin state cue or unpin affordance once they classify into the settled/snoozed shelves. Details inline.

^{Posted via Macroscope — UI Consistency}