fix: restore automatic thread settling defaults

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}

[t3dotgg]

#8321 changed the default auto-settle policy to Never, including for existing users.

This reverts that change. It restores the independent merge and inactivity controls, with merged or closed pull requests settling by default and inactive threads settling after 3 days. The prior behavior is restored across web, desktop, and mobile.

Verification:

• 371 focused tests passed across 9 test files
• Typechecks passed for all 5 affected packages
• Targeted lint and formatting passed

Browser verification was not run.

Built with GPT-5.6 Sol in T3 Code using the Codex harness.

---

Note

Medium Risk
Changes default and persisted settling behavior across web, desktop, and mobile thread lists; users upgrading from the exclusive-mode schema get new defaults rather than preserved mode choices.

Overview
Replaces the exclusive Thread settling mode (never / PR / inactivity) with two independent controls, undoing the prior default of manual-only settling.

Settings & contracts:sidebarAutoSettleMode is removed in favor of sidebarAutoSettleOnMerge (default on) and sidebarAutoSettleAfterDays (default 3 days, or null to turn off inactivity settling). Web Settings → General gets separate switches for merged threads and inactive threads; mobile drops the Thread Settling screen and adds an Auto-settle merged threads toggle on the main settings list.

Settling logic (effectiveSettled): Merge and inactivity can both apply—closed PRs still auto-settle; merged PRs settle only when the merge toggle is on. changeRequestAutoSettles respects autoSettleOnMerge and falls back to settling when PR timestamps are missing (restoring older behavior).

Sidebar, chat, thread menus, and mobile thread list v2 all pass the new flag through; docs and tests are updated to match.

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

Note

Replace sidebarAutoSettleMode with sidebarAutoSettleOnMerge boolean across client settings

• Removes the SidebarAutoSettleMode enum and replaces it with a boolean sidebarAutoSettleOnMerge (defaults to true) in settings.ts. sidebarAutoSettleAfterDays is retained for inactivity-based auto-settle.
• Updates effectiveSettled and changeRequestAutoSettles in threadSettled.ts so merged PRs settle by default unless autoSettleOnMerge is false; closed PRs always settle.
• Replaces the old mode selector in web and mobile settings UIs with separate toggles: one for auto-settling merged threads and one for enabling inactivity-based auto-settle. The mobile dedicated settling screen is removed.
• Risk: changeRequestAutoSettles now returns true (settle) when changeRequest.updatedAt or thread timestamps are missing or malformed; previously returned false. This may cause threads with missing timestamp data to settle unexpectedly.

📊 Macroscope summarized 241e0f2. 16 files reviewed, 3 issues evaluated, 1 issue filtered, 2 comments posted

🗂️ Filtered Issues

docs/user/thread-sidebar.md — 0 comments posted, 1 evaluated, 1 filtered

• line 10: The new unconditional claim that pinned threads settle when inactive is false after a user turns off Auto-settle inactive threads. That setting writes sidebarAutoSettleAfterDays: null, and effectiveSettled returns false for the inactivity path in that case, so the documentation will incorrectly tell those users that their inactive pinned threads still move to Settled. [ Out of scope (post-validation triage) ]

[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: eb6132b1-a984-4cfc-ae18-ac9109f5aa40

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

---

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

[macroscopeapp]

🟡 Mediumhome/HomeScreen.tsx:681

HomeScreen no longer passes the persisted autoSettleAfterDays value to buildThreadListV2Items, so the function always falls back to 3 days. This causes users who disabled inactivity settling (null) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

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

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 681:
`HomeScreen` no longer passes the persisted `autoSettleAfterDays` value to `buildThreadListV2Items`, so the function always falls back to 3 days. This causes users who disabled inactivity settling (`null`) or selected another duration to have threads settled after three days; pass the resolved persisted value through this call.

[macroscopeapp]

🟡 Mediumpersistence/mobile-preferences.ts:170

sanitizePreferences drops persisted autoSettleMode and autoSettleAfterDays values without translating them, so users with autoSettleMode: "never" reload with the defaults autoSettleOnMerge: true and autoSettleAfterDays: 3 and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

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

In file @apps/mobile/src/persistence/mobile-preferences.ts around line 170:
`sanitizePreferences` drops persisted `autoSettleMode` and `autoSettleAfterDays` values without translating them, so users with `autoSettleMode: "never"` reload with the defaults `autoSettleOnMerge: true` and `autoSettleAfterDays: 3` and threads begin settling automatically. Preserve the legacy fields long enough to map them to the new preferences before applying defaults.

[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 241e0f2. Configure here.}

[cursor]

Settings search catalog order mismatch

Low Severity

The search catalog lists auto-settle-inactive-threads before auto-settle-merged-threads, but General settings renders the merge row first. Search results follow catalog order, so matches for these settings appear in the opposite order from the page.

Additional Locations (1)

• apps/web/src/components/settings/SettingsPanels.tsx#L1952-L1981

^{Triggered by learned rule: Restore defaults on General settings page is intentionally global — not scoped per-page}

^{Reviewed by Cursor Bugbot for commit 241e0f2. Configure here.}