many empty terminal window pops up.
Resolved 💬 7 comments Opened Dec 13, 2025 by cheezmil Closed Dec 15, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of the VS Code extension are you using?
0.5.51
What subscription do you have?
business
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What issue are you seeing?
<img width="1328" height="1393" alt="Image" src="https://github.com/user-attachments/assets/c11c24dd-12a0-40e2-a319-2a611f6d2b64" />
When opening VSCode, an empty terminal window pops up. During development, it's common to open many VSCode windows, which causes numerous empty terminal windows to appear, which is very annoying.Although it will disappear after a while, it's still very annoying.
What steps can reproduce the bug?
Open vscode
What is the expected behavior?
_No response_
Additional information
_No response_
7 Comments
You said that this occurs when opening VS Code. Is there a reason you believe this is related to (or caused by) the Codex extension? Other than opening VS Code, are there any additional actions you need to take to repro the problem. Does the problem go away if you uninstall or disable the Codex extension?
You said, "Will the problem disappear if you uninstall or disable the Codex extension?" Yes.
Visual Studio Code
Version: 1.105.1 (system setup)
Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
Date: 2025-10-14T22:33:36.618Z (2 mos ago)
Electron: 37.6.0
ElectronBuildld: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631
Do you have any non-default configuration settings in your codex
config.tomlfile? For example, do you have any mcp servers configured?[shell_environment_policy]
inherit = "all"
exclude = ["ELECTRON_RUN_AS_NODE"]
[notice]
"hide_gpt-5.1-codex-max_migration_prompt" = true
[mcp_servers.mcphub]
url = "http://127.0.0.1:1035/mcp"
If you use default configs (e.g. comment out those parts of the config file or temporarily rename config.toml), does that affect the behavior you're seeing?
I tried it and using the default config.toml still has the problem I described
Sorry, it was an issue with another extension, it has been resolved.