mirror of
https://github.com/openai/codex.git
synced 2026-11-19 23:05:23 +00:00
Keep TUI prompt history tied to local settings (#42791)
## Why Prompt history is client-owned state, but app-server thread lifecycle responses derived its metadata from the active server configuration. When server and local settings differ, the TUI can advertise metadata for the wrong history log. ## What changed - Pass `LocalSettings` through thread start, resume, and fork response handling. - Build message-history metadata from the local Codex home and history preferences while continuing to use the thread configuration for server-owned session fields. ## Testing - Cover local history metadata across embedded and remote start, resume, and fork flows with deliberately different server settings. - Verify single-entry and batched history lookups return entries from the local prompt history. GitOrigin-RevId: 8b47230a4e9f2d342b8d79fd575d474c9062b05e
This commit is contained in:
1 parent
b3f5e45cc1
commit
a07158c784
11 files changed
+211
-38
No files matched your search
@@ -483,6 +483,7 @@ impl App {
|
||||
Ok(_) => {
|
||||
app_server
|
||||
.start_thread_with_session_start_source(
|
||||
&self.local_settings,
|
||||
&config, /*session_start_source*/ None,
|
||||
/*remote_cwd_override*/ None,
|
||||
)
|
||||
|
||||
Reference in new issue
Block a user