Omniscio

OmniscioGuidesStill open somewhere else

Claude Code: This conversation is still open somewhere else

Last checked against Anthropic's documentation on November 18, 2026. By the Omniscio team. Updated .

What is the exact message?

This conversation is still open somewhere else. Using it in two places at once can mix up its messages. If the extension restarted recently, a Claude process from before the restart may still be finishing. It usually ends on its own within about 10 minutes. This notice stays until you choose Open here anyway.

It appears in place of the prompt box, so the panel cannot be typed into while it is there.

What does it mean?

The Claude Code panel in VS Code is telling you that a second Claude Code process still holds this conversation open. It will not open the same conversation twice on its own, because two live copies of one conversation can write over each other's messages.

The notice is not an error report. It is asking you to choose: let the other process finish, or take the conversation here anyway.

What causes it

  • The extension restarted. A Claude process started before the restart can still be finishing, and it keeps the conversation open while it does. Anthropic puts its usual end at about 10 minutes.
  • The conversation is open in a terminal. A claude session sitting in another window holds the same conversation and triggers the same notice.
  • The conversation is open in another VS Code window. The same conversation can be resumed into a tab in a second window, which is not the tab you are looking at.

How do I fix it?

  1. Work out which case you are in. If you have the conversation open anywhere else — a terminal, another VS Code window — that is the holder. If you have nothing else open, it is the leftover process from a restart.
  2. If something else has it open, close it there first. Exit claude in that terminal, or close the conversation's tab in the other window.
  3. If nothing else has it open, wait about 10 minutes. The leftover process usually ends on its own within that time. Clicking before it ends leaves the conversation open in two places until it does, which is the state the notice exists to prevent.
  4. Click Open here anyway. The notice stays until you use it, and the panel then opens the conversation in this window.
  5. If it comes back every time, look at how the panel is started. With claudeCode.claudeProcessWrapper set, the extension skips this check and opens the conversation directly.

How do I know it is fixed?

  • The notice is gone and the prompt box is back, so you can type into it.
  • The conversation's earlier messages are in the panel, not a blank page.
  • Session history shows that conversation once, without a second copy in another window.

Where these answers come from

Common questions

What does the notice mean?

Another Claude Code process still has this conversation open, so the extension will not open it again until you choose Open here anyway. Anthropic's own wording for the risk is that using it in two places at once can mix up its messages.

Should I wait ten minutes or click straight away?

If you have nothing else open, wait. A Claude process from before the extension restarted may still be finishing, and it usually ends on its own within about 10 minutes. Clicking before it ends leaves the conversation open in two places until it does.

How do I close it in the other place?

If a terminal has the conversation, exit claude there. If another VS Code window has it open in a tab, close that tab. Then click Open here anyway.

Why does claudeProcessWrapper hide the notice?

Anthropic documents only this: with claudeProcessWrapper set, the extension skips the check and opens the conversation directly. The page cannot say more than that about how the check works.