[Android][Mobile] Long session title makes Archive dialog exceed viewport, leaving Archive button unreachable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.901.41600
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
On Codex mobile, the Archive confirmation dialog becomes unusable when a session has a very long title.
The dialog appears to render the complete session title without constraining the height of the dialog. With a sufficiently long title, the dialog grows beyond the height of the phone's viewport. The controls at the bottom of the dialog, including the Archive button, end up below the visible screen and cannot be reached.
As a result, it is impossible to archive that session from mobile.
I've attached a screenshot showing the problem: the session title fills essentially the entire screen and continues beyond the bottom edge, with no accessible Archive button.
This is particularly easy to encounter because Codex sometimes gives sessions extremely long auto-generated titles, including what appears to be much of the original user prompt. That behavior is already reported in #24491:
https://github.com/openai/codex/issues/24491
However, I think this is a separate UI bug. The Archive dialog should remain usable regardless of the length of a session title, including a manually assigned long title.
What steps can reproduce the bug?
- Have a Codex session with a sufficiently long title.
- Open that session in the ChatGPT/Codex mobile interface on Android.
- Open the session menu.
- Choose Archive.
- Observe the Archive confirmation dialog.
The full title is rendered in the dialog, causing the dialog to become taller than the viewport.
The Archive button at the bottom is no longer reachable, so the session cannot be archived.
What is the expected behavior?
The Archive dialog should always remain usable within the mobile viewport regardless of title length.
For example, the UI could:
- truncate or line-clamp the session title;
- give the dialog a maximum height and make its content scrollable; and/or
- keep the Cancel / Archive actions in a fixed footer that always remains visible.
The Archive button should never be pushed outside the reachable viewport by user-controlled/title content.
Additional information
My current workaround is:
- Rename the session to a much shorter title.
- Open the menu again.
- Archive it.
Unfortunately, renaming is also cumbersome on Android. In the rename text field I cannot reliably move the start/end text-selection handles. To replace a long title, I generally have to delete the entire title and type a new one from scratch.
So archiving one affected session currently requires renaming it first, clearing/retyping its title, saving the rename, reopening the menu, and then archiving it.
The text-selection-handle problem may be a separate Android input bug, but I mention it here because it makes the only available workaround substantially more painful.
Related issues:
- #24491 — Codex mobile sometimes uses the raw user prompt as the session title
https://github.com/openai/codex/issues/24491 - #21211 — unbounded thread title/metadata handling
https://github.com/openai/codex/issues/21211
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Archive confirmation dialog on Android with a sufficiently long session title, then locate the mobile dialog implementation and its title and action layout. Done means the dialog remains within the viewport and the Cancel and Archive actions remain reachable regardless of title length.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100