Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix VS Code extension and Codex CLI cannot be used simultaneously due to session conflict

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…

Error Message

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. 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.

Root Cause

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

RAW_BUFFERClick to expand / collapse

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: [email protected]
  • 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.

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…

FAQ

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.

#runtime error#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING