feat(swift-ios): default new tasks to recent project

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[saphid]

What changed

Default the native SwiftUI New Task flow to the available project from the most recently active thread.

Selection order stays narrow:

1. A valid explicit project selection.
2. The project from the newest lastActivityAt thread, falling back to updatedAt.
3. The first alphabetically grouped available project.

Missing or unavailable projects are skipped; equal timestamps use thread ID as a stable tie-break.

This is SwiftUI-only under apps/swift-ios. It does not implement the React Native apps/mobile portion named in #5785, add a recents section, reorder project lists, or persist another preference.

Base: pingdotgg/t3code:t3code/rebuild-mobile-app-swift at f98cab553546558e28d6e22f3dbe9807ecc3325f.
Current head: b6444b8ad3a2c9d1520c482c8b9171b970f57994.

The current-head repair only updates native Swift Contract test fixtures from the legacy flat providers catalog to production's environment-scoped providersByEnvironment; product behavior is unchanged.

Why

The previous alphabetical default could open a phone task in an unrelated project.

UI evidence

Current head — New Task defaults to the retained Simulator's most recently used available project, Thread Menu Proof:

Playable current-head Simulator flow (MP4 wrapper)

The child picker state remains isolated in #6131; this PR does not add the separate recents-section UI.

Verification

• Current head b6444b8: HomeThreadMetadataTests + DailyUXNewTaskTests — 29 passed, 0 failed.
• Exact-current-head apps/swift-ios/Scripts/ci-test.sh: exit 0; 234 tests in 29 suites.
• Integrated iOS Simulator: exact-current-head app built and launched successfully; the New Task deep link selected Thread Menu Proof without another tap. Runtime accessibility also reported Choose project | Thread Menu Proof.
• Current-head image and video were visually inspected; durable assets return HTTP 200 with image/png / video/mp4.
• git diff --check: passed.
• Direct independent review: Claude Opus 5 high, exit 0; no actionable findings on the fixture-only repair or product selection behavior.
• Current-head GitHub Contract fixtures and native tests, Test, Check, mobile static analysis, and release smoke all passed. Macroscope correctness skipped the fixture-only refresh; approvability completed neutral because human review is required. A manual refresh request was denied for contributor permissions. The exact product head retains the later t3-code approval, and both superseded threads are resolved. The Vercel authorization failure is unrelated to this SwiftUI-only change.

Checklist

• Small and focused
• Explained the SwiftUI-only scope
• Current-head screenshot and playable video
• Focused, full native, and integrated exact-head verification
• Fresh independent cross-provider review
• Current-head GitHub native/test jobs complete
• Maintainer scope alignment / human review

Built with GPT-5.6 Sol in the Codex harness.

---

Note

Medium Risk
Changes default project selection for new tasks, which can send work to the wrong project if ranking or auto-adoption misfires. Explicit selection and draft safeguards reduce that risk.

Overview
Defaults New Task to the most recently used project instead of the first alphabetical group.

Selection priority is now: explicit/requested project → project from newest thread activity (lastActivityAt, then updatedAt) → alphabetical fallback. Ranking deduplicates by project group, skips unavailable/disabled projects, and keeps the exact worktree that was used.

NewThreadView can later adopt a recent project once activity arrives, but only while awaiting recents and only if the user has not explicitly chosen project/model/workspace, has no draft content, and draft restore has finished. Opening New Task from the workspace also passes the currently selected project as the requested ID.

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

Note

Default new task project selection to the most recently used project

• When opening the new task sheet, the project now defaults to the currently selected project (if any), then the most recently used project by activity timestamp, then the first project alphabetically.
• Adds DailyUXCreationContext.recentProjects to rank projects by last activity, deduplicated by logical group, and initialProject to resolve the correct physical worktree representative.
• The new task screen can automatically switch from a fallback project to the first recent project once activity data arrives, but stops if the user makes an explicit selection or has draft content.
• Behavioral Change: WorkspaceView.openNewTaskOrProjectCreation now passes the current selectedProjectID instead of nil, so the sheet no longer opens with an unset project when a project is already selected.

^{Macroscope summarized b6444b8.}

Delivery: direct
Validated against Theo commit: f98cab5
Depends on: none
Merge order: this PR only
Validation status: Current head b6444b8 is locally and CI proven, approved, thread-clean, and mergeable. Macroscope approvability remains neutral pending human review; the unrelated Vercel authorization failure is a maintainer-side gate.

[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: 3e4956d0-cf57-492c-afef-302499f29480

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

This PR introduces a new feature for automatically defaulting new tasks to recently used projects, changing user-facing behavior. Unresolved review comments identify a logic bug where failed explicit project requests prevent proper fallback to recent projects.

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

[saphid]

@t3dotgg Ready for your review against the current SwiftUI branch. Final head 7f25c1293; focused/full native and integrated evidence are in the PR body, current-head CI is green, and all review threads are resolved. MacroScope correctness is clean and approvability defers this user-facing change to human review.

[saphid]

Rebuilt as one focused commit on exact current Theo 5b7ee58f6, replacing both the stale branch topology and the conflicting recency models.

Final contract: project groups are ranked by their newest thread activity (lastActivityAt ?? updatedAt) with deterministic tie-breaking; missing/unavailable groups are ignored; settled/archived threads still count as historical use. New Task honors an explicit available project, otherwise uses that ranking, then a stable alphabetical fallback. The approved picker's separate UserDefaults click-recency clock is intentionally not imported. A later Recent Projects picker PR must consume this same ranking.

Verification:

• focused DailyUXNewTask 20/20
• full native 330 pass / one expected skip / zero failures
• exact final app build succeeded
• isolated integrated proof: Home contained a Zulu thread and New Task defaulted to Zulu Recent
• git diff --check clean
• Tailnet-only video: https://alexs-macbook-pro-1.tail4e5636.ts.net:8766/swiftui-recent-project-ranking-proof-20260810.mp4

Conflict classification: stale branch history plus a real semantic conflict between thread activity and UserDefaults click recency; resolved in favor of one thread-activity source of truth. Direct Opus review was unavailable due confirmed HTTP 429 before inference; no independent verdict is claimed.

[saphid]

The dependent picker presentation is now preserved separately at saphid/swiftui-recent-projects-picker (53445705c), one commit on this PR head. It consumes recentProjects(in:) directly—no UserDefaults recency store. After #5802 lands, it can be rebased into its own focused PR.

Behavior: up to three canonical Recent groups, alphabetic deduplicated remainder, name/path search, explicit empty/no-match states. Verification: focused 22/22; full native 332 pass / one expected skip; integrated New Task default → Recent/Other → search Alpha → select Alpha; git diff --check clean. Tailnet-only proof: https://alexs-macbook-pro-1.tail4e5636.ts.net:10013/recent-project-picker-final-53445705c.mp4

Independent Opus review remains unavailable at the confirmed 429 quota boundary; no verdict is claimed.

[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 2c1466f. Configure here.}

[saphid]

Exact final-head simulator proof (2c1466f): New Task defaults to the recent pingdotgg/t3code project and keeps the exact Simulator Showcase checkout context.

The final DailyUXNewTaskTests suite passed after the review fixes. The current native-CI red is the base-branch provider-catalog fixture failure fixed separately in #6130.

[t3-code]

one blocking state-selection edge case remains.

[t3-code]

correction after independent review: the earlier requested-project concern is not blocking. initialProject falls through to the recent project or first available project when an explicit request is unavailable, so the composer does not remain empty. reviewed the exact-base selection and late-adoption paths; approved.

[saphid]

@macroscope review

Please refresh correctness and approvability against current head b6444b8. The two earlier review threads were superseded by the later corrected approval and are now resolved; current-head native and general CI pass.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.