VS Code extension and Codex CLI cannot be used simultaneously due to session conflict

What happened?

When using the Codex VS Code extension and Codex CLI at the same time, they cannot run concurrently. One side reports a session-related error/conflict instead of allowing independent use.

This feels like a bug because the VS Code extension session and a separate Codex CLI session should either:

• be able to run independently at the same time, or
• show a clear, actionable message explaining that a shared session lock is intentional and how to avoid it.

Expected behavior

I should be able to keep Codex open in VS Code and also run codex / Codex CLI in a terminal without one interface breaking the other because of session state.

Actual behavior

Using VS Code Codex and Codex CLI side by side causes a session-related failure. The tools appear to conflict over session state, so only one can be used reliably at a time.

Environment

• OS: Windows
• Codex CLI: codex-cli 0.129.0
• VS Code extension: openai.chatgpt@26.513.21555
• Repo/workspace path type: local Windows workspace

Notes

The exact error text was not captured yet, but the failure is session-related and appears specifically when both the VS Code extension and CLI are active. If needed, I can add the exact error message after reproducing it again.