feat(sidebar-v2): bring back thread pinning

[t3dotgg]

Sidebar v2 shipped without a way to keep an important thread from drifting: active cards hold creation order, and the settle/snooze lifecycle eventually parks everything on a shelf. There was no way to say "this one stays on top."

Pinning brings that back. Pinned threads render as full cards above the inbox behind a thin divider (no header text — the pin glyphs carry the meaning). A pin overrides the lifecycle: while pinned, a thread can neither auto-settle out of sight nor be hidden by snooze state, and its settle/snooze affordances yield to a single Unpin. Unpinning returns the thread to wherever it would otherwise classify.

Pin state is server-backed and syncs across devices, following the snooze template layer for layer:

• Contracts: optional pinnedAt on thread + shell (pre-pin servers still decode), thread.pin/thread.unpin commands and events, and a threadPinning capability so clients hide the affordance under version skew.
• Server: decider cases (idempotent by re-emission, archived threads rejected; no other invariants — a pin only ever promotes visibility), projector, projection pipeline, pinned_at column via migration 036, and snapshot/persistence plumbing.
• Web: pinned partition ahead of snooze/settle, pin glyph on cards, Unpin hover action, Pin/Unpin in the context menu.
• Mobile: same partition in thread list v2, Unpin as the swipe primary on pinned rows, Pin in card long-press menus.

Covered by focused tests at each layer: decider pin/unpin invariants, projector lifecycle, persistence round-trip, client reducer events, and a mobile partition test proving a pinned thread cannot vanish into a shelf.

---

Built by Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Medium Risk
Touches orchestration decider event bundles and list classification across web, mobile, and DB projections; behavior is well-tested but pin/settle/snooze interactions affect core inbox ordering.

Overview
Adds thread pinning end-to-end so important threads stay as full cards above the inbox instead of drifting into settle/snooze shelves.

Contracts & clients: Optional pinnedAt on thread shells, thread.pin / thread.unpin commands and events, and a threadPinning capability (same version-skew pattern as snooze). Client runtime dispatches pin/unpin; web and mobile gate UI on the capability and surface Pin/Unpin in context menus (mobile long-press menus + pin glyph on pinned rows).

Server & persistence: Decider handles pin/unpin (idempotent re-emission, archived threads rejected). Pinning promotes visibility by also emitting unsettle/unsnooze when needed; settling a pinned thread also emits thread.unpinned. Projector, projection pipeline, and queries carry pinnedAt; migration 036 adds pinned_at to projection_threads. Server advertises threadPinning: true.

List behavior (web sidebar v2 + mobile thread list v2): Partition order is pinned → active → snoozed → settled. Snooze still hides a thread (pin preserved underneath); pinned threads skip settled classification. Tests cover decider, projector, persistence, reducer, and mobile partition parity with web.

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

Note

Add thread pinning to sidebar v2 on web and mobile

• Adds a pinned block that appears above the active inbox in both the web sidebar (SidebarV2.tsx) and mobile thread lists, showing pinned threads in creation order with a pin icon.
• Introduces thread.pin and thread.unpin orchestration commands with full decider, projector, and projection pipeline support; settling a pinned thread also emits thread.unpinned.
• Adds database migration 036_ProjectionThreadsPinned.ts to add pinned_at to projection_threads.
• Pinning is gated by a new threadPinning server capability; environments not advertising this capability hide pin actions.
• Pinned threads are exempt from auto-settle; snoozed pinned threads are hidden until they wake, then return to the pinned block.

^{Macroscope summarized 5d8f568.}

[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: c90c084a-a72f-4953-88ec-706df2cdc316

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

[macroscopeapp]

Approvability

Verdict: Needs human review

1 blocking correctness issue found. This PR introduces a complete thread pinning feature with new commands, events, database migration, and UI across web and mobile. As a new user-facing capability with multiple unresolved bugs identified (including high-severity issues with re-pin idempotency and mobile swipe actions), it warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Settle leaves latent snooze

Medium Severity

When thread.settle runs on a pinned thread, the decider clears the pin but leaves snoozedUntil/snoozedAt unchanged. After unpin, list partition treats snooze before settled, so the thread moves to the snoozed shelf instead of the settled tail despite the user choosing Settle.

 

^{Reviewed by Cursor Bugbot for commit 0f171bd. Configure here.}

[cursor]

Pinned menu ignores settlement

Low Severity

Pinned rows always use PINNED_MENU_ACTIONS with Settle, regardless of settlementSupported. Swipe correctly falls back to Archive when settlement is unsupported, but long-press Settle hits the server guard and shows an error instead of offering archive like other legacy rows.

Additional Locations (1)

• apps/mobile/src/features/threads/thread-list-v2-items.tsx#L840-L842

 

^{Reviewed by Cursor Bugbot for commit 0f171bd. Configure here.}

[macroscopeapp]

🟠 High

t3code/apps/mobile/src/features/threads/thread-list-v2-items.tsx

Lines 513 to 517 in 5d8f568

	const primaryAction = useMemo(() => {
	// Pre-settlement server: archive is the swipe action, as in v1. (Slim
	// rows cannot occur here — unsupported environments never classify as
	// settled.)
	if (swipeActions.primary === "archive") {

A pinned card's primary swipe action is still Settle (or Archive on legacy servers), not Unpin — so the main mobile swipe gesture on a pinned row settles or archives the thread instead of unpinning it. The pinnedRow flag only controls the pin glyph and the long-press menu item; it is never passed into resolveThreadListV2SwipeActions or the primaryAction memo, so the swipe path never produces an Unpin action. Route the pinned state into primaryAction selection and return handleUnpin for pinned rows.

Suggested change

	const primaryAction = useMemo(() => {
	if (pinnedRow && props.pinningSupported) {
	return {
	accessibilityLabel: `Unpin ${thread.title}`,
	icon: "pin.slash" as const,
	label: "Unpin",
	onPress: handleUnpin,
	};
	}
	// Pre-settlement server: archive is the swipe action, as in v1. (Slim
	// rows cannot occur here — unsupported environments never classify as
	// settled.)

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/mobile/src/features/threads/thread-list-v2-items.tsx around lines 513-517:

A pinned card's primary swipe action is still Settle (or Archive on legacy servers), not Unpin — so the main mobile swipe gesture on a pinned row settles or archives the thread instead of unpinning it. The `pinnedRow` flag only controls the pin glyph and the long-press menu item; it is never passed into `resolveThreadListV2SwipeActions` or the `primaryAction` memo, so the swipe path never produces an Unpin action. Route the pinned state into `primaryAction` selection and return `handleUnpin` for pinned rows.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

There are 4 total unresolved issues (including 2 from previous reviews).

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

^{Reviewed by Cursor Bugbot for commit 5d8f568. Configure here.}

[cursor]

Mobile snoozed shelf lacks Unpin

Medium Severity

When a pinned thread is snoozed, its mobile long-press menu incorrectly shows only "Wake" and "Delete". The "Unpin" option is missing, requiring users to wake the thread before unpinning, which differs from web behavior.

 

^{Reviewed by Cursor Bugbot for commit 5d8f568. Configure here.}

[cursor]

Re-pin emits promotion events

High Severity

thread.pin always emits thread.unsettled / thread.unsnoozed when settled or snooze fields are set, even on idempotent re-pin when pinnedAt is already set. Retries or duplicate pin commands on a pinned-and-snoozed thread can wake it early instead of no-op re-emission.

 

^{Reviewed by Cursor Bugbot for commit 5d8f568. Configure here.}