[jagrat7]

Problem

Snooze options in Settings → Threads are always sorted soonest first, and every snooze menu uses that same order. To get a preferred option to the top, you had to delete every option above it and add them back. There was no way to move one.

Change

• Snooze menus now list options in the order they appear in Settings, not by wake time. Hiding a "Today" option once its time has passed still works. When two options wake at the same minute, the one higher in the list is kept.
• Each row in the settings editor gets a drag handle. Dragging (mouse, or keyboard with Space plus the arrow keys) saves the new order right away. Rows no longer re-sort when focus leaves the list.
• Reset now also shows when only the order differs from the defaults.
• The ordering logic lives in packages/client-runtime's resolveSnoozePresets, so the web/desktop sidebar, the thread action menu, and mobile all follow the saved order. Mobile has no snooze editor, so nothing else changes there.
• The user guide line that said menus list options soonest first is updated.

Settings rows (drag to reorder) ──save──▶ settings.snoozePresets (ordered)
                                                   │
                                  resolveSnoozePresets (keeps order, drops
                                  passed "Today" and same-minute duplicates)
                                                   │
                       web sidebar · thread menu · mobile thread list

Scope and approval

This configures an existing capability: the customizable snooze options added in pingdotgg#26208. It only controls the order of options a user has already chosen. No new snooze kinds, storage fields, or schema changes. snoozePresets was already an ordered array.

PR #26208 deliberately chose automatic ordering ("Menus always list options soonest first, so there is no reordering to manage"), and #26427 made the editor match. This PR reverses that choice, so upstream would need maintainer sign-off. Existing users with saved presets will see their menu in saved order, which is usually the sorted order the editor already wrote.

Verification

• vp test run packages/client-runtime/src/state/threadSnoozed.test.ts: 36 passed. The two resolveSnoozePresets cases that asserted soonest-first ordering now assert settings order, and both failed before the change.
• vp run check:changed: format, lint, knip, typecheck (7 packages), tests, and React compiler all pass.
• Manual pass in the dev web app: moved Tomorrow to the top with the drag handle. "Menu now" updated, and the thread context menu's Snooze submenu then listed Tomorrow first.

Before: the editor always sorts rows soonest first, with no reorder control (screenshot from the current app):

After: rows have drag handles, and the description says menus follow this order:

After: the thread's Snooze menu follows the saved order:

Reorder, then open the menu:

Not verified: dragging with a real mouse in the recording. Browser automation could not produce the intermediate pointer moves dnd-kit needs, so the recording shows the keyboard reorder instead. The mouse path uses the same PointerSensor setup as the existing route list in EnvironmentRoutesList. Mobile was not run, because it only consumes the shared ordering function that the tests above cover.

Claude Opus 5.5 via Claude Code in T3 Code.

---

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: jagrat7/t3code
• Branch: feat/snooze-preset-order
• File: .coderabbit.config.ts
• Commit: cf57df4
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: 48227f24-e186-42be-8d5a-0263a35f906d

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔍 Default ordering needs approval check

With unedited presets, resolveSnoozePresets now follows the built-in array even when wake times differ. The contribution rules require prior approval for changed product defaults; the PR description does not link it.

---

Was this helpful? React with 👍 or 👎 to provide feedback.