codex - 💡(How to fix) Fix Prompt history is shared across threads [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18199Fetched 2026-04-17 08:31:28
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

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

26.415.20818

What subscription do you have?

API

What platform is your computer?

Mac

What issue are you seeing?

When I hit the up arrow in a certain thread to see what I asked last, it shows me the last prompt I did, no matter the thread, which often times means it happened in another thread. It would be good to just limit the prompt history to the history in this current thread, or at least have this be a setting to choose between local or global history.

What steps can reproduce the bug?

Launch multiple threads with different prompts and scroll through history with up arrow.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue can be potentially resolved by implementing a thread-specific prompt history feature or adding a setting to choose between local and global history.

Guidance

  • The current implementation of the up arrow functionality seems to be retrieving the last prompt from the global history, regardless of the current thread.
  • To verify the issue, launch multiple threads with different prompts and scroll through history using the up arrow to confirm that it shows the last prompt from any thread.
  • A potential workaround could be to store prompt history separately for each thread, allowing the up arrow to retrieve the last prompt from the current thread's history.
  • Consider adding a setting to allow users to choose between local (thread-specific) and global history for the up arrow functionality.

Notes

The issue lacks information about the current implementation and technical details, so the provided guidance is based on the described behavior and may not be comprehensive.

Recommendation

Apply workaround: Implementing a thread-specific prompt history feature or adding a setting to choose between local and global history could resolve the issue, as it would allow users to control how the up arrow functionality behaves.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING