Codex client experience optimization

Resolved 💬 4 comments Opened May 1, 2026 by iambinlin Closed May 1, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

App

What feature would you like to see?

I have three UX suggestions for the Codex client:

1. Account switching

Please consider bringing the account-switching capability from the web version into the Codex client. Right now, switching accounts requires signing out and signing back in, which is inconvenient for users who move between personal accounts, work accounts, and different organizations.

It would be much smoother if the client supported quick account switching without a full logout/login flow.

2. Project grouping

Please consider adding project grouping or folders to the Projects section in the sidebar. As the number of projects grows, the current flat list becomes difficult to scan and manage.

It would be helpful to let users create groups, move projects into groups, and collapse or expand them. This would make the sidebar easier to organize by workspace, client, team, product area, or personal/work context.

3. Add quote-reply support for messages in a conversation

In longer Codex conversations, I often realize mid-thread that I want to respond based on a specific earlier message, tool result, decision, or assistant reply.

Currently, the closest related feature appears to be conversation forking from an earlier message. That is useful when I want to branch into a new thread, but it does not fully solve the case where I want to stay in the current conversation and explicitly reference one earlier message as context.

Expected behavior:
Codex should allow users to quote or reference a specific message inside the current conversation. For example, a user could click a “Quote” or “Reply with reference” action on any prior message. The composer would then include a compact quoted preview, and the next prompt would be anchored to that selected message while still continuing in the same thread.

Suggested interaction:

  • Hover over a previous user message, assistant response, tool result, or decision point.
  • Click “Quote” or “Reply with reference”.
  • Show a small quoted preview above the composer.
  • Let the user type a follow-up that clearly refers to that selected message.
  • Allow removing the quote before sending.

Impact:
This would make multi-turn Codex conversations easier to navigate and reduce ambiguity when users want to revisit a specific earlier point without manually copying text or creating a separate fork.

<img width="1599" height="984" alt="Image" src="https://github.com/user-attachments/assets/f95b38a4-1c88-433c-ad35-3c775b478143" />

<img width="1536" height="1024" alt="Image" src="https://github.com/user-attachments/assets/1f14abe1-5dc5-4c5c-9b41-60251f638e27" />

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 3 months ago

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

  • #19131

Powered by Codex Action

iambinlin · 3 months ago

cc @etraut-openai

etraut-openai contributor · 3 months ago

Thanks for the feedback, but I'm going to close this because we ask that each feature idea have its own feature request. We use community feedback (upvotes) to help inform feature prioritization, and when you combine multiple issues in the same ticket, that breaks down. Parts of your suggestions are already covered by existing feature requests (that already have upvotes), so feel free to upvote and post to those threads.

iambinlin · 3 months ago
Thanks for the feedback, but I'm going to close this because we ask that each feature idea have its own feature request. We use community feedback (upvotes) to help inform feature prioritization, and when you combine multiple issues in the same ticket, that breaks down. Parts of your suggestions are already covered by existing feature requests (that already have upvotes), so feel free to upvote and post to those threads.

Do I need to open separate issues for the others?