the session happened on rebase don't have a branch name
Resolved 💬 2 comments Opened Feb 26, 2026 by asukaminato0721 Closed Feb 27, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.104.0
What subscription do you have?
pro
Which model were you using?
gpt-5.2-codex high
What platform is your computer?
Linux 6.12.73-1-lts x86_64 unknown
What terminal emulator and version are you using (if applicable)?
Konsole
What issue are you seeing?
I use codex to resolve rebase conflict, but it can't show branch name afterwards, so I lost where the branch is.
Resume a previous session Sort: Created at
Type to search
Created at Updated at Branch Conversation
> 2 minutes ago 23 seconds ago - resolve the conflict
10 minutes ago 3 minutes ago 1138 fix failures
19 minutes ago 11 minutes ago - resolve the conflict
30 minutes ago 24 minutes ago 1689 fix test..
44 minutes ago 40 minutes ago - resolve the conflict
1 hour ago 45 minutes ago - resolve the conflict
1 hour ago 1 hour ago - resolve the conflict
2 hours ago 1 hour ago - resolve the conflict<img width="1125" height="272" alt="Image" src="https://github.com/user-attachments/assets/28522387-01fd-4afc-9fbc-5c7cd10b88e3" />
What steps can reproduce the bug?
make a merge conflict, rebase, let codex to fix it. Then resume, check the list.
What is the expected behavior?
it can at least show the branch.
Additional information
_No response_
2 Comments
Thanks for the bug report, but there's not enough details for me to investigate. If something like this occurs in the future, please use the
/feedbackcommand to upload the session details and include the thread ID in your bug report.thread id 019c9c30-0dab-7183-abeb-8578429d2279