fix(mobile): server model, worktree, and origin preferences now apply to new tasks

[t3dotgg]

New tasks on mobile ignored the preferences configured on the server. Setting the default thread mode to "New worktree" did nothing (mobile hardcoded local), a project's default model kept being used even after its provider was disabled or signed out on the server, and one explicit branch/origin pick was silently pinned for that project forever, overriding server defaults for every task after it.

Now mobile resolves these the same way web does:

• Workspace mode falls back to the server's defaultThreadEnvMode instead of "local", in both the composer display and the queued-task (offline outbox) path.
• Stored model selections (draft or project default) only apply while their provider instance is enabled, installed, and authenticated; otherwise the server's default model wins. The gate applies at display and at send, so what you see is what dispatches. Offline environments can't be validated, so stored selections pass through untouched there.
• After a task is sent or queued, the draft's workspace selection is dropped so the next task re-resolves mode/branch/origin from server settings (matches web's Stop new threads inheriting checkout/branch from viewed thread #4411 decision that workspace context never carries implicitly). Model, runtime, and interaction-mode stickiness are unchanged, as is the regular thread composer.

Verified with mobile typecheck, lint, and the full mobile test suite (98 files / 589 tests), plus new unit tests for the availability gate and the workspace-dropping clear.

---

🤖 Generated with Claude Code (Fable 5)

---

Note

Medium Risk
Changes what model and workspace settings mobile dispatches when starting or queueing new tasks, including offline outbox payloads; behavior is intentional parity with web and is covered by new tests, but incorrect resolution could mis-target providers or worktrees.

Overview
Mobile new-task flow now matches web for server-driven defaults and stops pinning workspace choices across tasks.

Workspace: Default mode uses the server’s defaultThreadEnvMode (not hardcoded local) in the composer and when building queued/offline outbox messages. After send or queue, clearComposerDraftContent can drop workspace selection so the next task re-resolves branch/mode/origin from server settings; model, runtime, and interaction mode stay on the draft.

Model: resolveSelectableModelSelection only honors draft or project-default models when the provider is enabled, installed, and authenticated; otherwise resolution falls through to the server default. The same gate runs in the flow provider, send path, and pending-task queue builder. With no server config (offline), stored selections are left unchanged.

Unit tests cover the availability gate and workspace clearing on new-task draft reset.

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

Note

Fix server model, worktree, and origin preferences applying to new tasks in mobile

• Adds resolveSelectableModelSelection in modelOptions.ts to validate stored model selections against server provider availability, returning null when the provider is disabled, not installed, or unauthenticated.
• Updates NewTaskFlowProvider and NewTaskDraftScreen to use this resolver so stale model selections targeting unavailable providers fall back to the server or flow default.
• Resolves workspace mode from the server's defaultThreadEnvMode setting instead of hardcoding 'local', so new tasks respect the server's configured default.
• Extends clearComposerDraftContent to accept a clearWorkspaceSelection option, used after task creation so the next task re-resolves workspace defaults rather than inheriting the previous selection.

^{Macroscope summarized 940f69d.}

[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: ff91995c-5a7c-4506-9d04-781167497f46

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: Approved 940f69d

Bug fix ensuring stored model selections are validated against server provider availability, with fallback to server defaults when providers are disabled. Changes are well-scoped with unit tests, and the author has recent history with these files.

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