fix: Preserve cloud reasoning level after initial prompt

[charlesvien]

Problem

Cloud task reasoning level dropdown resets from the user's chosen value (e.g. "max") to "high" after the initial prompt, so follow-up resumed runs use the wrong effort.

Closes #2167

Changes

1. Read task.latest_run.reasoning_effort in useSessionConnection and thread it into watchCloudTask
2. Add initialReasoningEffort param to watchCloudTask and fetchAndApplyCloudPreviewOptions
3. Override the server's hardcoded "high" default with the run's actual value when merging preview config into the session, mirroring the existing initialModel pattern
4. Extend the preview-options merge test to assert the effort override is honored

How did you test this?

Manually

Publish to changelog?

no

[charlesvien]

• fix: Preserve cloud reasoning level after initial prompt #2272 👈 (View in Graphite)
• fix: Unblock cloud branch picker during slow remote load #2269
• fix: Make file references in agent messages clickable in command center #2271
• fix: Render at-mentioned chips as @labels in task titles #2270
• fix: Buffer feature-flag subscribers registered before init #2267 : 1 other dependent PR (#2268 )
• feat: Add nightly cleanup of stale draft releases #2239
• main

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

[greptile-apps]

Prompt To Fix All With AI

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

---

### Issue 1 of 1
apps/code/src/renderer/features/sessions/service/service.test.ts:3482
**Prefer parameterised tests for the two `sendPrompt` effort cases**

The two new tests ("preserves prior reasoning effort…" and "uses newRun.reasoning_effort over prior effort…") are structurally identical — they share all mock setup and only differ in `priorEffort`, `newRun.reasoning_effort`, and the expected `initialReasoningEffort`. The team rule is to prefer parameterised tests; an `it.each` table over `[priorEffort, newRunEffort, expected]` rows would express both cases with no duplication and make future variants (e.g. `undefined` vs `null` inputs) trivial to add.

_{Reviews (1): Last reviewed commit: "refactor watchCloudTask to options bag" | Re-trigger Greptile}

[graphite-app]

Merge activity

• May 21, 7:16 PM UTC: This pull request can not be added to the Graphite merge queue. Please try rebasing and resubmitting to merge when ready.
• May 21, 7:16 PM UTC: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..