# How do set Julia version in VSCode when using juliaup
**URL:** https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619
**Category:** VS Code
**Tags:** vscode, versioning, juliaup
**Created:** [October 31, 2023, 2:45pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619 "2023-10-31T14:45:35Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Torkel](https://discourse.julialang.org/u/Torkel)
#### Post date: [October 31, 2023, 2:45pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/1 "2023-10-31T14:45:35Z")
I am using Juliaup to manage my Julai version. It is now using the 1.10 beta by default. However, for one application, I need to quickly run something in 1.9. I almost exclusively use VSCode.
Is there a way, when using Juliaup, to start a VSCode session using a specific Julai version? I guess I could reconfigure Juliaup to change its default, but I am also running other julia sessions, so it would be neat if there is a way to simply tell VSCode “use this version” (like I can do with e.g. a Jupyter notebook in VSCode).
---
### Author:  [@Bruno\_Amorim](https://discourse.julialang.org/u/Bruno_Amorim)
#### Post date: [October 31, 2023, 2:56pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/2 "2023-10-31T14:56:04Z")
Not exactly what you want, but running:
```julia
juliaup default 1.9
```
in the command line before opening VS Code should do the trick.
UPDATE: this doesn’t work, see: [How do set Julia version in VSCode when using juliaup - #8 by davidanthoff](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/8)
---
### Author:  [@oheil](https://discourse.julialang.org/u/oheil)
#### Post date: [October 31, 2023, 3:06pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/3 "2023-10-31T15:06:30Z")
> [@Torkel](#):
>
> it would be neat if there is a way to simply tell VSCode “use this version”
There is
```julia
julia.executablePath
```
in the settings of the VSCode Julia extension.
You can set it, e.g. to:
```julia
c:\Users\oheil\.julia\juliaup\julia-1.10.0-beta2+0.x64.w64.mingw32\bin\julia.exe
```
Choose your path to your desired Julia executable. My example is for Windows.
---
### Author:  [@Torkel](https://discourse.julialang.org/u/Torkel)
#### Post date: [October 31, 2023, 3:23pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/4 "2023-10-31T15:23:12Z")
Does this work for JuliaUp though? EIther case, it seems like I would have to go in, change the executive file, and then start VSCode, and then change it again?
---
### Author:  [@Torkel](https://discourse.julialang.org/u/Torkel)
#### Post date: [October 31, 2023, 3:23pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/5 "2023-10-31T15:23:47Z")
Yeah, this would work, but feels like there might be something more convenient (just like juliaup lets you star ta Julia session without changing the default).
---
### Author:  [@oheil](https://discourse.julialang.org/u/oheil)
#### Post date: [October 31, 2023, 3:44pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/6 "2023-10-31T15:44:45Z")
> [@Torkel](#):
>
> Does this work for JuliaUp though?
In my example I choose a specific juliaup installed executable.
You can start a specific version also with, e.g.
```julia
julia +1.10
```
but I don’t know if this is somehow configurable in VSCode in a convenient way.
---
### Author:  [@Torkel](https://discourse.julialang.org/u/Torkel)
#### Post date: [October 31, 2023, 3:53pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/7 "2023-10-31T15:53:48Z")
Ok, yeah, that make sense now, sorry for the confusion!
---
### Author:  [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [October 31, 2023, 4:06pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/8 "2023-10-31T16:06:40Z")
So, I think setting `julia.executablePath` to something like `julia +1.9` should work.
What does _not_ work (but really should) is that the VS Code extension picks up Juliaup directory overrides or the env var. That is a bit of a shame, and I hope to fix that sometime soon.
---
### Author:  [@Torkel](https://discourse.julialang.org/u/Torkel)
#### Post date: [October 31, 2023, 4:23pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/9 "2023-10-31T16:23:48Z")
Ok, at least good to know. Hopefully some neater interface for these appear some time down the line 🙂
---
### Author:  [@gdalle](https://discourse.julialang.org/u/gdalle)
#### Post date: [October 31, 2023, 8:22pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/10 "2023-10-31T20:22:04Z")
> [@Bruno\_Amorim](#):
>
> Not exactly what you want, but running:
>
> ```julia
> juliaup default 1.9
>
> ```
>
> in the command line before opening VS Code should do the trick.
Slight improvement: I update `juliaup default` and then I reload the VSCode window from the command palette
---
### Author:  [@Torkel](https://discourse.julialang.org/u/Torkel)
#### Post date: [October 31, 2023, 8:46pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/11 "2023-10-31T20:46:11Z")
Yeah, that’s what I have been doing as well. However, that requires me to then reset the default for when I need to restart my other julia sessions (which I run in my standard environment). And then when I need to restart this julai session I have to run through it all as well.
It works, but it is a bit of a mess to keep track of.
---
### Author:  [@Jex248](https://discourse.julialang.org/u/Jex248)
#### Post date: [May 22, 2024, 1:37pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/12 "2024-05-22T13:37:08Z")
What worked for me is using the shell to enter the correct version, and installing any package. This creates an environment which vscode should be able to detect once you reload.
---
### Author:  [@fredcallaway](https://discourse.julialang.org/u/fredcallaway)
#### Post date: [December 16, 2024, 5:26pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/13 "2024-12-16T17:26:58Z")
EDIT: You also need to set the executablePath setting to explicitly point to juliaup, e.g. `"julia.executablePath": "/Users/fred/.juliaup/bin/julia",`
As of Dec 2024, there’s a much easier way to do this. Simply run `juliaup override set 1.9` in your directory and then the `julia` command will use version 1.9 when run from that directory, regardless of how you start julia.
[docs](https://github.com/JuliaLang/juliaup#:~:text=configured%20directory%20overrides.-,juliaup%20override%20set,-lts%20sets%20a)
---
### Author:  [@JBH\_84](https://discourse.julialang.org/u/JBH_84)
#### Post date: [December 16, 2024, 7:38pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/14 "2024-12-16T19:38:58Z")
thanks for sharing this. I executed the following command in my project directory folder and get:
PS C:\Users\james\documents\sienna\fpa\_sienna\nve\_env\> juliaup override set 1.10.4
Override set to ‘1.10.4’ for ‘\?\C:\Users\james\Documents\Sienna\FPA\_Sienna\nve\_env’.
however, when i call up my julia REPL in VSC via the alt + j + o cmd it still pulls up julia 1.11.2.
i have a blank entry for my julia executable file path location in vsc.
I also tried putting in a .julia-version file in the same folder location of my .toml files but thats not getting recognized by vsc either
---
### Author:  [@fredcallaway](https://discourse.julialang.org/u/fredcallaway)
#### Post date: [December 16, 2024, 8:46pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/15 "2024-12-16T20:46:56Z")
Sorry; I forgot I had set up some hacky stuff to manage my own julia sessions, so my solution won’t work for others (I edited my post)
---
### Author:  [@fredcallaway](https://discourse.julialang.org/u/fredcallaway)
#### Post date: [December 16, 2024, 8:57pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/16 "2024-12-16T20:57:50Z")
Sorry again; turns out the fix does work in general (I think) as long as you set the executablePath to point to juliaup—see edited post.
---
### Author:  [@JBH\_84](https://discourse.julialang.org/u/JBH_84)
#### Post date: [December 16, 2024, 10:44pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/17 "2024-12-16T22:44:43Z")
> [@fredcallaway](#):
>
> “julia.executablePath”: “/Users/fred/.juliaup/bin/julia”,
Thanks! I tried implementing this but wasnt successful. It doesnt look like i have the same juliaup installation setup as you because i have the following files stored at C:\Users\james.julia\juliaup
I belive this is because I dont have juliaup directly on my path but is directly callable from windows powershell command due to “aliases”
I execute: (Get-Command juliaup).Source to get the location of my juliaup.exe file.
i set my julia executable path in vsc:
“julia.executablePath”: “C:\Users\james\AppData\Local\Microsoft\WindowsApps\juliaup.exe”,
however, unfortunately that still doesnt work (i.e. its calling the release version of julia instead of the older one that i want). note i confirmed that juliaup override is working properly via “juliaup override status”. the right version of julia comes up when i activate a repl outside of vsc. it’s just not working when i am trying to run code through vsc. pretty frustrating.
if anyone has an answer to this, i greatly appreciate input. but otherwise i give up and will just manually change the path whenever i work on this specific project requiring an older version of julia
---
### Author:  [@pitipatw](https://discourse.julialang.org/u/pitipatw)
#### Post date: [May 21, 2025, 7:14pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/18 "2025-05-21T19:14:11Z")
> [@gdalle](#):
>
> > [@Bruno\_Amorim](#):
> >
> > Not exactly what you want, but running:
> >
> > ```julia
> > juliaup default 1.9
> >
> > ```
> >
> > in the command line before opening VS Code should do the trick.
>
> Slight improvement: I update `juliaup default` and then I reload the VSCode window from the command palette
This works!
As of 21st May.
This is on MacOS M2 chip.
I updated Julia through `juliaup update` from 1.11.3 to 1.11.5
Then go to VScode: `command + shift + p` to open the pallete.
FInd : Reload Window.
And my Julia is updated to the latest version.
Note: I only have 1 version of Julia installed in the default channel.
Hope this helps for some of you
---
### Author:  [@bieniekmat](https://discourse.julialang.org/u/bieniekmat)
#### Post date: [January 15, 2026, 1:40pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/20 "2026-01-15T13:40:15Z")
You can also configure the Julia plugin (Marketplace, click right on Julia plugin and go to Settings). There is the `Executable Path` which you can replace with `julia +1.11.7~x64` to specify the version you want, assuming you have it installed. I had to restart VSCode to make it work.
I am not sure how to make this project-specific.
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [January 15, 2026, 3:29pm UTC](https://discourse.julialang.org/t/how-do-set-julia-version-in-vscode-when-using-juliaup/105619/21 "2026-01-15T15:29:43Z")
Just click on “Workspace” instead of “User” to set a project-specific path:
