feat(mobile): add Codex task parity

[richardsolomou]

Problem

Mobile task creation hardcoded Claude, and its new-task and conversation screens had drifted from desktop. Runtime choices could also be lost or mapped to Claude-specific configuration when retrying or resuming Codex tasks.

Changes

I added Claude and Codex controls across task creation, retry, and resume using the shared model and reasoning policies. Adapter-specific execution modes, defaults, and cloud reasoning keys now come from core, while unrestricted modes remain hidden pending an explicit mobile opt-in. Native rendering remains in mobile.

How did you test this?

• Ran all 449 mobile tests, including execution-mode filtering coverage.
• Ran the monorepo typecheck.
• Ran Biome on the affected mobile files.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[github-actions]

React Doctor found 2 issues in 2 files · 2 warnings.

2 warnings

src/app/task/index.tsx

• ⚠️ src/app/task/index.tsx:195 Event logic handled in an effect no-event-handler

src/features/tasks/composer/TaskChatComposer.tsx

• ⚠️ src/features/tasks/composer/TaskChatComposer.tsx:120 Event logic handled in an effect no-event-handler

_{Reviewed by React Doctor for commit 5e2a064.}

[greptile-apps]

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
packages/core/src/sessions/cloudTaskSessionService.ts:402
**Legacy Resume Drops Task Controls**

When both the legacy run and its persisted composer config lack an adapter, this remains `undefined`. The mobile API client then omits the resolved model, reasoning, and permission mode with the adapter, so retry can restart an older Claude task using server defaults instead of its previous controls.

```suggestion
    const adapter =
      composerConfig?.adapter ?? previousRun?.adapter ?? "claude";
```

### Issue 2 of 2
packages/core/src/sessions/cloudTaskSessionService.ts:425-428
**Invalid Run Reasoning Reused**

When the composer reasoning is unsupported and the adapter has not changed, this fallback reuses `previousRun.reasoningEffort` without validating it. If that stored value is also unsupported by the resolved model, the API client rejects the payload and sandbox-inactive retry fails instead of resuming.

_{Reviews (1): Last reviewed commit: "feat(mobile): add Codex task controls" | Re-trigger Greptile}

[richardsolomou]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(mobile): add Codex task parity #3654 👈 (View in Graphite)
• refactor(mobile): finalize portability boundary #3642
• refactor(mobile): reuse inbox semantics #3641
• refactor(mobile): reuse session display semantics #3640
• refactor(core): own composer model policy #3637
• refactor(mobile): reuse transport and permission policies #3635
• refactor(mobile): reuse inbox transport #3634
• refactor(mobile): reuse repository aggregation #3633
• refactor(mobile): finish shared cloud task adoption #3608
• refactor(mobile): reuse the cloud task engine #3624
• refactor(mobile): reuse core task policies #3623
• refactor(mobile): reuse the task API client #3622
• refactor(mobile): reuse task contracts and model policy #3616
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.