fix(mobile): persist selected execution mode across prompts

[dmarticus]

Problem

In the mobile app, the execution mode reverts to plan after every subsequent prompt, even when the user changes it (e.g. to "accept edits") at task creation. The selected mode should persist for the duration of the session.

Root cause

The new-task screen (apps/mobile/src/app/task/index.tsx) let the user pick a mode and passed it as initialPermissionMode to the first cloud run — but never wrote that choice into taskStore.composerConfigByTaskId[task.id].

So on the task detail screen, composerConfig for that task was undefined and composerMode fell back to DEFAULT_EXECUTION_MODE = "plan". Since each agent turn completes its run on the cloud, every follow-up prompt goes through the resume-after-terminal path, which starts a fresh run with initialPermissionMode: composerMode — i.e. "plan". That's why it reverted on every subsequent prompt.

(The agent retains the mode correctly within a single run — the reversion was purely the mobile client sending "plan" to each new run.)

Fix

When a task is created, seed the per-task composer config with the mode/model/reasoning the user selected:

setComposerConfig(task.id, { mode, model, reasoning });

Now the detail screen reflects the chosen mode, and every subsequent resume run reuses it for the duration of the session. This also keeps model and reasoning selections consistent across follow-ups, which had the same gap.

Changing the mode mid-session via the detail-screen pill already persisted correctly (handleModeChange calls setComposerConfig), so that path is unaffected.

Notes

• Tasks created before this fix (no stored config) still default to "plan", which is the intended fallback.

🤖 Generated with Claude Code

[greptile-apps]

_{Reviews (1): Last reviewed commit: "fix(mobile): persist selected execution ..." | Re-trigger Greptile}

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit 2716f16.}