Codex Desktop should allow terminal-launched context to reuse the active thread

Summary

When Codex Desktop is already open on a thread, launching or handing context from a terminal with environment-variable scoped setup opens a new chat/thread instead of reusing the currently open conversation.

This is disruptive when the terminal setup is meant to apply to the active conversation.

Environment

• OS: Windows
• Surface: Codex Desktop app
• Trigger: terminal-launched Codex / app deep-link style flow with environment variables or command context
• Codex version: 26.611.61753 (released 17 Jun 2026)

Current behavior

• A thread is already open in Codex Desktop.
• I open/use a terminal and pass environment variables or related launch context.
• Codex Desktop starts a new chat/thread instead of applying the context to the currently open thread.

Expected behavior

Codex Desktop should provide one of these:

• a setting to reuse the currently active/open thread for terminal-launched submissions, or
• a documented CLI/deep-link/API path to target the currently active thread, or
• a clear prompt asking whether to use the active thread or create a new one.

Notes

The documented deep links cover codex://threads/new / codex://new?... for new threads and codex://threads/<thread-id> for opening an existing thread, but I could not find a documented setting that prevents this flow from creating a new thread or sends the terminal-provided context to the active Desktop thread.