Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[macOS] Escape no longer returns from Settings to the previous chat

Open Beginner friendly
#58,073 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust
Domain
desktop

Research direction

Start by tracing Settings navigation and Escape key handling in the macOS desktop app; the issue does not name specific files or tests. Compare the Escape behavior with the working back button and check nearby navigation tests. Done when Escape returns to the previous chat and a regression test covers that behavior.

Written by the indexing model from the issue text.

Description

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

26.1023.51421

What subscription do you have?

Not provided

What platform is your computer?

macOS

What issue are you seeing?

After a recent desktop app update, pressing Escape on the Settings page no longer returns to the previous chat. In earlier versions, Escape worked for this and was part of my regular workflow. Clicking the back button still works.

What steps can reproduce the bug?
  1. Open the Codex desktop app on macOS and open a chat.
  2. Open Settings.
  3. Press Escape.
  4. Observe that Settings remains open.
  5. Click the back button and observe that navigation back works.
What is the expected behavior?

Pressing Escape should return from Settings to the previous chat, as it did in the older version.

Additional information

No response

Dominant language
Rust
Stars
131k
Forks
20.7k
Avg merge
1m
Merged PRs (30d)
997

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.