# Broken communication between VSCode Julia terminal and code editor

**URL:** <https://discourse.julialang.org/t/broken-communication-between-vscode-julia-terminal-and-code-editor/122454>\
**Category:** Tooling\
**Tags:** vscode\
**Created:** [November 9, 2024, 6:01pm UTC](https://discourse.julialang.org/t/broken-communication-between-vscode-julia-terminal-and-code-editor/122454 "2024-11-09T18:01:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JMLuther](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmluther/32/22832_2.png) [@JMLuther](https://discourse.julialang.org/u/JMLuther)\
**Post date:** [November 9, 2024, 6:01pm UTC](https://discourse.julialang.org/t/broken-communication-between-vscode-julia-terminal-and-code-editor/122454/1 "2024-11-09T18:01:05Z")

</div>

My Julia installation and VScode were working fine, but has stopped communicating between the code editor and Julia Terminal within VSCOde.  
On initial code execution (Shift-Enter) the Julia terminal opens within VSCode and gives an error message which I have not been able to troubleshoot and fix:

 ![image](https://global.discourse-cdn.com/julialang/original/3X/8/7/87375fe7942627251cb1bc818869ed1f36698cc0.png)

After this message, code does not execute in the terminal from the code editor.

However, if copy-pasted into the same terminal it runs without issues. It doesn’t seem to be communicating/connecting to VSCode however- plots pop up in a separate pane, not within VSCode.

Any help is appreciated.  
Running VSCode 1.9.52 on Windows\_NT x64.  
Julia 1.10.6 (the current LTS installed via `juliaup`, set as default in Powershell)

The most relevant issue I’ve found is [here as github issue](https://github.com/julia-vscode/julia-vscode/issues/3145) but have not been able to resolve the issue by setting `terminal.integrated.enablePersistentSessions` to `false` .

also possibly related report [on github](https://github.com/julia-vscode/julia-vscode/issues/2977)

---

<div class="post-metadata">

**Author:** ![JMLuther](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmluther/32/22832_2.png) [@JMLuther](https://discourse.julialang.org/u/JMLuther)\
**Post date:** [November 9, 2024, 11:17pm UTC](https://discourse.julialang.org/t/broken-communication-between-vscode-julia-terminal-and-code-editor/122454/2 "2024-11-09T23:17:47Z")

</div>

I haven’t fixed the issue but found a useful workaround. adding here if others find useful:

Initiate Julia in the VSCode terminal  
Open command panel - Cntrl+Shift+P (windows)  
find the command Julia: Connect external REPL  
copy the clipboard command into the external REPL

once connected, the code execution works as expected.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [November 10, 2024, 6:58pm UTC](https://discourse.julialang.org/t/broken-communication-between-vscode-julia-terminal-and-code-editor/122454/3 "2024-11-10T18:58:06Z")

</div>

Can you show a bit more of the filename in the screen shot? Maybe just blur our your name, but leave the rest intact? Hard to judge what is going on otherwise.

---

<div class="post-metadata">

**Author:** ![JMLuther](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmluther/32/22832_2.png) [@JMLuther](https://discourse.julialang.org/u/JMLuther)\
**Post date:** [November 12, 2024, 10:32pm UTC](https://discourse.julialang.org/t/broken-communication-between-vscode-julia-terminal-and-code-editor/122454/4 "2024-11-12T22:32:27Z")

</div>

The project folder is in a OneDrive folder. It was previously working fine, but possibly my institution has added some firewalls or other security measures.

I’ve found that the workaround of connecting to an external REPL works really well. I plan to use that method and not worry about this further, although if it’s a bug then hopefully it will be fixed for other reasons.

 ![image](https://global.discourse-cdn.com/julialang/original/3X/4/c/4cd615af19e49625fbcec68f6a045fbc1b427a1c.png)