[imqdee]

Problem

On mobile, Choose project first lists the projects without the No project row while an environment is still syncing. When the server config arrives, the row is inserted at the top and every project moves down one row, so a tap aimed at a project can land on No project instead.

#23391 meant to fix this by reserving the row, but only once the environment's server config is known (cached or live). Projects come from the shell cache, which is often ready before the config, so the shift still happens on cold start, after the config cache is cleared, and on a fresh pairing.

This qualifies as a small, focused fix for an obvious bug: one picker row, no change to what the row does once ready, and it completes what #23391 already set out to do.

Fix

resolveNewTaskScratchOption now reserves the row whenever an enabled, supported environment is listed, and returns a status instead of a ready flag. Disabled and unsupported environments are ignored, since they never receive a config and would otherwise hold the row pending forever.

• ready: an environment is connected and reports a scratch folder. Row enabled, as before.
• pending: no environment is ready yet. Row disabled, subtitle Waiting for your environment.
• unavailable: every environment is connected and reports no scratch folder (the server refuses to create it inside a git checkout). Row stays disabled with Not available on this environment rather than disappearing, so the list does not shift the other way either.

The environment chosen for the row keeps the same preference order (ready, then cached, then any). Only NewTaskRouteScreen reads it.

Verification

• vp test run apps/mobile/src/features/threads/new-task-project-selection.test.ts: 24 passed. The new case "reserves the option before any config arrives" fails on main (it returns null). Existing cases are updated to the status shape. Added cases cover unavailable, a mixed connected and connecting pair that stays pending, and disabled or unsupported environments being ignored.
• vp run check:changed: format, lint, knip, typecheck, tests and React compiler pass.
• Manual, iPhone 17 simulator (iOS 26.5), dev client against a local dev server with seeded projects. Repro: stop the server, delete the app's cached server-config row, relaunch, open Choose project, start the server.
  • Before (main): the list shows no No project row. When the app reconnects, the row is inserted at the top and the projects shift down one row.
  • After: the row is present and disabled (Waiting for your environment), then turns on in place. Nothing moves.
  • Unavailable: a dev server whose data dir sits inside the git worktree reports no scratch folder. The row stays disabled with Not available on this environment. On main it is hidden.

Syncing (before, after, changed pixels). On main the row is missing, with the fix it is reserved and disabled:

Synced. Same final layout, 0.0% changed pixels:

Server without a scratch folder (after):

Reconnect, before: the row is inserted and the projects jump down (mp4)

Reconnect, after: the row turns on in place (mp4)

Not checked: Android, since no Android SDK is available on this machine. The Android row uses the same scratchSubtitle and disabled props through NavigationRow. The web new-thread picker has a similar gate on a known scratch root, but the server it talks to is usually local and its config is ready at once. It is left out to keep this PR to the reported mobile problem.

Written by Claude Opus 5.5 in Claude Code.

[macroscopeapp]

Approvability

Verdict: Approved at 95d4c70

Macroscope's review found this PR approvable — The mobile “No project” row remains visible during environment synchronization and explains when it is waiting or unavailable. Task creation remains gated on a connected, configured environment and an explicit user action.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The scratch-option resolver now returns ready, pending, or unavailable status values after filtering environments. The new-task screen uses the status to gate task start and set the subtitle for both “No project” rows.

Changes: Scratch task availability

Layer / File(s)	Summary
Resolve scratch availability apps/mobile/src/features/threads/new-task-project-selection.ts, apps/mobile/src/features/threads/new-task-project-selection.test.ts	The resolver filters disabled and unsupported environments and returns a ready, pending, or unavailable status. Tests cover status outcomes and environment selection.
Use status in the new-task screen apps/mobile/src/features/threads/NewTaskRouteScreen.tsx	The screen allows scratch-task start only when the status is ready. Both “No project” rows display a subtitle based on the status.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Suggested reviewers: jdlar18, juliusmarminge

Merge Risk: Minimal · up to 94a5f

The change reserves the No project row in the mobile project picker while environments sync, which avoids the layout shift. No merge-blocking risk was identified.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title names the main change: the No project row keeps its position while environments sync, which matches the raw summary (the row is reserved while environments are pending) and the PR objectives…
Description check		The description follows the template. It has Problem, Change (Fix), Scope (a small fix of an obvious bug, with the issue #23391 referenced as the earlier attempt), and Verification with specific test …
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: the No project row keeps its position while environments sync, which matches the raw summary (the row is reserved while environments are pending) and the PR objectives. It is specific and concise, with no file lists or vague wording.

Full details: Description check

Explanation

The description follows the template. It has Problem, Change (Fix), Scope (a small fix of an obvious bug, with the issue #23391 referenced as the earlier attempt), and Verification with specific test commands, manual steps, observed before and after results, and images. It states what was not checked (Android, web picker). The Scope section does not link a new issue, but it explains why none is needed. The conventional commit title guidance is met by the title. The description is largely complete.

Finishing Touches

Generate unit tests (beta)

• Create a new PR

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

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: 5cff012
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: a5a104c7-8c2e-49ad-aa2d-882c3fbd24e9

Commits

Reviewing files that changed from the base of the PR and between 95d4c70 and 94a5f90.

Files selected for processing: 2

• apps/mobile/src/features/threads/NewTaskRouteScreen.tsx
• apps/mobile/src/features/threads/new-task-project-selection.test.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.