Repository navigation
[Bug]: Continue threads after restarts does not preserve Codex reasoning effort #10928
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
- Enable "Continue threads after restarts".
- Open a Codex thread and explicitly select a non-medium reasoning effort, such as High.
- Start a task and restart T3 Code while the turn is still running, without manually stopping the thread first.
- Let the thread continue automatically. Do not change the model or reasoning settings, and do not send a manual follow-up.
- Compare the reasoning effort of the automatic continuation with the setting used before the restart.
Expected behavior
The automatically continued turn should preserve the reasoning effort used before the restart. Restarting T3 Code should not change this setting.
Actual behavior
The thread continues automatically, but the reasoning effort differs from the setting used before the restart, without any manual change.
Source inspection of v0.0.40 suggests a possible cause:
- In apps/server/src/serverRuntimeStartup.ts, restart reconciliation calls providerService.sendTurn without modelSelection.
- CodexAdapter reads reasoningEffort from the current turn's modelSelection.
- In apps/server/src/provider/Layers/CodexSessionRuntime.ts, buildCodexCollaborationMode falls back to medium when effort is missing.
Impact
Minor bug or occasional failure
Version or commit
v0.0.40
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Activity
juliusmarminge commentedon Sep 9, 2026
Triage
Confirmed on current
main(not only v0.0.40). Automatic continue-after-restart still drops Codex reasoning effort.What happens
reconcileProviderSessionsresumes opted-in threads withproviderService.sendTurn, but only sendsthreadId,continuation(Codex) or the fixed continue prompt, andinteractionMode. It never forwardsmodelSelection, even though the thread shell has it.ProviderService.sendTurndoes not backfill model/effort. Session recovery does pass the persisted selection intostartSession, but CodexstartSessiononly applies model and service tier — notreasoningEffort.CodexAdapter.sendTurnthen reads effort only from the sendTurnmodelSelection. Restart always includesinteractionMode, sobuildCodexCollaborationModeruns and falls back toeffort ?? "medium". Collaboration settings and developer instructions both become medium.Reconcile tests currently assert that Codex continuation payload (
continuation: true,interactionMode: "default", nomodelSelection).Not a duplicate
Suggested fix
Pass
thread.modelSelection(or the session-directory persisted selection) on the restartsendTurn. Add a reconcile test that a non-mediumreasoningEffortis forwarded, plus coverage thatbuildTurnStartParamsdoes not write medium when High/xhigh is supplied.Claude/Grok apply effort at session start from the recovered selection, so they are less exposed. The omitted
modelSelectionis still a general gap.Severity
Minor. Opt-in setting; the thread does resume; effort can change without a user action.
Labels:
bug,accepted,via-triage(removeneeds-triage)