Skip to content

Prompt textarea becomes disabled after several prompts on macOS, requiring app restart #30263

Open

Description

@mediarl

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

Version 26.623.31921 • Released Jun 25, 2026

What subscription do you have?

ChatGPT Pro 100$

What platform is your computer?

25.5.0 arm64 arm

What issue are you seeing?

Summary

After using Codex App for several prompts in the same session, the prompt textarea/input becomes disabled. The rest of the app still appears functional, but I can no longer type a new prompt or submit anything.

Restarting Codex fixes the issue temporarily, but it comes back after more prompts.

Steps to reproduce

  1. Open Codex App on macOS.
  2. Use it normally in a repository/session.
  3. Send several prompts one after another.
  4. After some time, the prompt textarea becomes disabled / non-editable.

Expected behavior

The prompt textarea should remain enabled when Codex is idle, so I can continue entering prompts without restarting the app.

Actual behavior

The textarea becomes disabled even though the app otherwise looks functional. I cannot type a prompt or continue the conversation. The only workaround I found is to quit and restart Codex App.

Frequency

This happens repeatedly and has been occurring for several weeks. It does not seem tied to one specific prompt; it usually happens after several prompts in the same session.

Workaround

Quit and restart Codex App.

Notes

No visible error message is shown. I can attach a screenshot showing the disabled prompt textarea. I can provide logs if you can tell me where to find them.

What steps can reproduce the bug?

Use Codex for 30 min or more with the pet opened. And it finishes by freezing. Really boring

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    appIssues related to the Codex desktop app
    on Jun 26, 2026
  2. github-actions commented on Jun 26, 2026

    @github-actions
    Contributor
  3. prashantabisht-alt commented on Jun 27, 2026

    @prashantabisht-alt

    I am seeing the same issue on macOS.

    My duplicate issue: #30324
    Feedback ID: 019f06d2-2f51-7033-b048-7b5fbf2c57b1

    Codex app: 26.623.41415 build 4505
    macOS: 26.5.1 build 25F80
    Platform: Darwin 25.5.0 arm64 arm

    For me, clicking the composer does not recover input. Cmd+J, Cmd+K, and Cmd+Shift+P also do not recover it. Quitting and reopening Codex restores typing temporarily.

  4. prashantabisht-alt commented on Jun 27, 2026

    @prashantabisht-alt

    One extra detail: I also had the Codex pet open when this happened. The issue may be related to the pet overlay/floating UI.

    In my case the composer stopped accepting keyboard input after Codex had been running for a while. Clicking the composer did not recover it, and Cmd+J, Cmd+K, and Cmd+Shift+P also did not help. Restarting Codex restored typing temporarily.

    My duplicate issue: #30324
    Feedback ID: 019f06d2-2f51-7033-b048-7b5fbf2c57b1
    Codex app: 26.623.41415 build 4505
    macOS: 26.5.1 build 25F80

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 appbugSomething isn't workingpets

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions