[Desktop 26.721.11231.0] successful edit/retry flow calls deprecated thread/rollback

Environment

• Codex Desktop: 26.721.11231.0
• Platform: Windows
• Observed: 2026-07-31

Summary

During a normal edit/retry flow, Desktop emitted:

thread/rollback is deprecated and will be removed soon

The same operation then completed successfully:

• method=thread/rollback, errorCode=null
• followed by method=turn/start, errorCode=null

Expected behavior

Desktop should use a supported current primitive and produce no deprecation warning during a successful user flow.

Actual impact

The operation succeeds, but the error-style warning makes a successful action look unsupported or unstable.

Suggested correction

Replace the Desktop call with the supported current method, or migrate the edit/retry flow before removing the deprecated endpoint. Add a regression test asserting that a successful retry emits no deprecated-method warning.

Version scope

This report is confirmed for Desktop 26.721.11231.0. I did not re-exercise a state-changing retry solely to reproduce the warning on the current build, so I am not claiming that newer versions are affected.

No account identifiers, task IDs, private content, local paths, or raw unrelated logs are included. No configuration or binary workaround was applied.