Prompt history should be scoped per thread

Resolved 💬 2 comments Opened Feb 24, 2026 by kyu-suke Closed Feb 24, 2026

What variant of Codex are you using?

App

What feature would you like to see?

Description

Currently, pressing the ↑ / ↓ keys in the prompt input field allows users to navigate through previous prompts. However, this prompt history is shared globally across all threads.

As a result, prompts entered in Thread A also appear in the history of Thread B.

When working with multiple threads in parallel, there are situations where it is useful to review recently entered prompts or recent work within a specific thread. However, because prompts from different threads are mixed together in the history, it can be difficult to locate the relevant entries.

Current Behavior

  • Pressing ↑ / ↓ in the prompt input field shows prompt history
  • Prompt history is shared across all threads
  • Prompts from Thread A appear in Thread B

Example:

  • Thread A: A1, A2, A3
  • Thread B: B1, B2

Pressing ↑ in Thread B shows:

B2 → B1 → A3 → A2 → A1

Problem

When trying to review recent prompts or previously executed tasks within a thread, the mixed history from other threads makes it harder to find the relevant entries.

This becomes particularly noticeable when frequently switching between multiple threads, and can reduce overall usability.

Feature Request

It would be very helpful if prompt history could be maintained separately for each thread.

Expected Behavior

  • Thread A shows only prompts entered in Thread A
  • Thread B shows only prompts entered in Thread B
  • ↑ / ↓ history navigation works independently per thread

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗