feat(mobile): add Codex task parity

[richardsolomou]

Problem

Mobile task creation hardcoded Claude, and retry/resume flows could lose or combine runtime choices from different adapters.

Depends on #3642
Refs PostHog/posthog#76229

Changes

Phase 3 product change: I added Claude and Codex controls across task creation, retry, and resume. Core owns adapter transitions and resume-option resolution, including legacy mobile state that predates persisted adapter selection.

How did you test this?

• Full monorepo typecheck
• 2,614 core tests
• 453 mobile tests
• Host-boundary check

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:137 Event logic handled in an effect no-event-handler

_{Reviewed by React Doctor for commit c58a11d.}

[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]

• feat(mobile): add Codex task parity #3654 👈 (View in Graphite)
• refactor(mobile): finalize portability boundary #3642
• refactor(mobile): adopt shared interaction semantics #3641
• refactor(mobile): finish shared task and inbox adoption #3640
• refactor(mobile): adopt shared task runtime #3637
• refactor(core): extract shared presentation semantics #3635
• refactor(core): extract permission and composer semantics #3634
• refactor(core): extract repository integration semantics #3633
• refactor(core): extract portable cloud task engine #3608
• refactor(core): rename cloud task service as engine #3624
• refactor(core): extract cloud task policies #3623
• refactor(api-client): extract cloud task transport #3622
• refactor(shared): extract task contracts and model policy #3616
• main

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

[trunk-io]

😎 Merged successfully - details.

[veria-ai]

Low: Resume discards the previous permission mode

For an existing Codex task without a saved mobile composer selection, this falls back to auto instead of the latest run's initial_permission_mode. Both resume and retry subsequently send this value explicitly, so repository-controlled instructions can edit the workspace after the user retries a task that was originally Plan or Read only. Preserve and validate the previous run's mode when the adapter matches, falling back to the adapter default only when no valid prior mode exists.

[veria-ai]

PR overview

This pull request adds Codex task parity to the mobile app, including support for resuming and retrying existing tasks with composer permission settings.

One issue remains open in the resume and retry flow: tasks previously run in Plan or Read-only mode can fall back to Auto mode when no mobile selection is saved. This could allow repository-provided instructions to modify the workspace after a user retries the task, though exploitation requires that specific task state and user action. No issues have yet been addressed.

Open issues (1)

• Low: Resume discards the previous permission mode — apps/mobile/src/app/task/[id].tsx:189

Fixed/addressed: 0 · PR risk: 4/10