Skip to content

Still reproducible on Windows Desktop 26.908.40834 — first turn completes, but follow-up message does not create a new turn/start #45315

Open
Open
Still reproducible on Windows Desktop 26.908.40834 — first turn completes, but follow-up message does not create a new turn/start#45315
Labels
appIssues related to the Codex desktop appapp-serverIssues involving app server protocol or interfacesbugSomething isn't workingwindows-osIssues related to Codex on Windows systems

Description

@Dongpeng2
Dongpeng2
opened on Sep 14, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

26.908.40834

What subscription do you have?

ChatGPT Pro 5x

What platform is your computer?

Windows 11, x64

What issue are you seeing?

On Codex Desktop 26.908.40834 for Windows, the first message in a conversation works normally, but after the first response completes, I cannot send a follow-up message in the same conversation.

The follow-up message does not start a new turn and the conversation becomes effectively unusable for multi-turn interaction.

What steps can reproduce the bug?

  1. Open Codex Desktop on Windows.
  2. Open a local project/repository.
  3. Start a new conversation.
  4. Send a simple prompt such as: "Reply with only 1".
  5. Wait for Codex to complete the response.
  6. In the same conversation, send another prompt such as: "Reply with only 2".
  7. The second message does not start normally and no new response is generated.

This is reproducible consistently after the first completed turn.

What is the expected behavior?

After the first response completes, I should be able to continue sending additional messages in the same conversation normally.

Each follow-up message should start a new turn while preserving the existing conversation context.

Additional information

Codex Desktop version: 26.908.4834.0

The first turn reaches the local app-server successfully with method=turn/start and errorCode=null.

However, after attempting to send the second message, no second turn/start is observed in the logs.

The logs also repeatedly contain messages such as:

Received turn/started for unknown conversation

Received turn/completed for unknown conversation

and:

Received broadcast but no handler is configured method=thread-stream-following-changed

The local app-server remains running, and the first request completes successfully, so this appears to be a Codex Desktop renderer/conversation-state issue rather than an authentication, network, or model API failure.

I also observed a separate Git checkpoint warning involving refs/codex/turn-diffs/checkpoints/... with exitCode=128, although this may be unrelated to the follow-up-message issue.

Activity

  1. Dongpeng2
    added
    appIssues related to the Codex desktop app
    on Sep 14, 2026
  2. github-actions
    added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    app-serverIssues involving app server protocol or interfaces
    on Sep 14, 2026

  3. github-actions commented on Sep 14, 2026

    @github-actions
    github-actionsBot
    on Sep 14, 2026 – with GitHub Actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  4. VenimirPetkov commented on Sep 14, 2026

    @VenimirPetkov
    VenimirPetkov
    on Sep 14, 2026 – with ChatGPT Codex Connector

    Independent reproduction on Windows 11 x64 (OS build 26200) with MSIX package OpenAI.Codex_26.908.4834.0.

    The failure was consistent in newly created local threads:

    1. The first turn completed successfully on the local app-server.
    2. The durable turn record was completed with a finite duration and no error.
    3. The desktop UI nevertheless remained in a streaming/sending state and would not accept a second message.

    Sanitized desktop log signatures included:

    Received turn/started for unknown conversation
Received turn/completed for unknown conversation
Received broadcast but no handler is configured method=thread-stream-following-changed
Received broadcast but no handler is configured method=thread-stream-following-status-requested

    On resume, the state was contradictory: the latest turn was reported as completed while the renderer still treated the thread as streaming/owner.

    Additional checks:

    • State and queue SQLite integrity checks passed.
    • There was no relevant pending queue item.
    • Resetting route bindings did not help.
    • A full desktop UI-state reset did not help; the issue reproduced immediately in three fresh threads.
    • The same account worked on other computers and mobile, so this did not appear account- or service-wide.

    Workaround/result: uninstalling 26.908 and installing the official Store-signed 26.903.8094.0 MSIX resolved the issue immediately; multi-turn interaction in the desktop app works again.

    This strongly suggests a 26.908 desktop renderer / conversation-stream state regression rather than a backend turn failure.

    Submitted by Codex at the user's explicit request. Personal paths, account details, thread IDs, and raw logs were intentionally omitted.

  5. shanshan1231 commented on Sep 16, 2026

    @shanshan1231
    shanshan1231
    on Sep 16, 2026

    I finally found a fix for this issue.

    In my case, Codex Desktop could send the first message normally, but the second message would get stuck and never send.

    The cause turned out to be an authentication problem. My Google account password had been changed, but Codex still showed me as logged in, so I didn’t realize the login session had become invalid.

    What fixed it for me was:

    Change/reset the password of the Google account linked to ChatGPT.
    Sign out of Codex completely.
    Sign back in to Codex with the same Google/ChatGPT account.

    After logging in again, multi-turn conversations started working normally and the second-message issue disappeared.

    So if Codex can send the first message but gets stuck on the second one, I recommend trying a full re-login, especially if your Google account password has changed recently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appapp-serverIssues involving app server protocol or interfacesbugSomething isn't workingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions