# Letting AI agents use the VSCode Julia REPL
**URL:** https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805
**Category:** General Usage
**Created:** [April 20, 2026, 7:25pm UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805 "2026-04-20T19:25:54Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@marius311](https://discourse.julialang.org/u/marius311)
#### Post date: [April 20, 2026, 7:25pm UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/1 "2026-04-20T19:25:54Z")
Hi all, recently the julia-vscode devs added the ability for VSCode Copilot to run code in the integrated Julia REPL. I made a small addon extension which also lets all the other agentic tools like the native Claude/Codex VSCode extensions (or their TUI / desktop counterparts entirely outside of VSCode for that matter) drive your integrated Julia REPL via MCP.
Check it out here: [Julia VSCode MCP (unofficial) - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=MariusMillea.julia-vscode-unofficial-mcp)
I’ve found the whole integrated terminal thing pretty awesome, since the agent can just iterate in the running terminal, inspecting variables, tweaking code, etc… its so much faster than it only being able to run one-off Julia commands via bash like it currently does. If you do agentic coding, I highly recommend trying this out (with this extension if you need it, or just the Copilot support already built into the official extension / Kaimon / julia-mcp, etc…).
---
### Author:  [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)
#### Post date: [April 20, 2026, 8:49pm UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/2 "2026-04-20T20:49:23Z")
Hello, have you discussed integrating this into the main vscode Julia extension?
---
### Author:  [@marius311](https://discourse.julialang.org/u/marius311)
#### Post date: [April 20, 2026, 9:12pm UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/3 "2026-04-20T21:12:57Z")
Yea, see the discussion starting [here](https://github.com/julia-vscode/julia-vscode/pull/4044#issuecomment-4230157650), basically we just don’t know yet from upstream what the “right way” to do this is (and may not for a while), until then this extension is a stopgap, ideally it won’t be needed in the future.
---
### Author:  [@aplavin](https://discourse.julialang.org/u/aplavin)
#### Post date: [April 21, 2026, 1:56am UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/4 "2026-04-21T01:56:18Z")
Nice – I like that you can also see and interact with the same session!
Note that for persistent agent-only session, to solve these:
> [@marius311](#):
>
> the agent can just iterate in the running terminal, inspecting variables, tweaking code, etc… its so much faster than it only being able to run one-off Julia commands via bash like it currently does
one doesn’t need VSCode, there’s a lightweight [[ANN] julia-mcp — persistent Julia sessions for AI assistants](https://discourse.julialang.org/t/ann-julia-mcp-persistent-julia-sessions-for-ai-assistants/135386/1).
I actually wonder if there’s a way to get best of both worlds? Ie, when in vscode → AI uses VSCode REPL, like this extension does; when standalone → AI uses julia-mcp.
---
### Author:  [@marius311](https://discourse.julialang.org/u/marius311)
#### Post date: [April 21, 2026, 5:07am UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/5 "2026-04-21T05:07:35Z")
Its def doable in practice, basically the lock-file architecture of my package and when the right VSCode window isn’t found it calls out to your package, it might be worth thinking about. My guess is there exists some user that would want pretty much all possible combinations though. Like I myself at least once did VSCode REPL driven by a terminal Codex in another window on the side, sometimes I’m in the mood for a TUI. I suppose keeping them separate MCPs allows users to optionally install one or the other in a given project. But there’d definitely be value in the predictability of single set of tools and instructions. Not sure the right direction, but that’s what comes to mind.
---
### Author:  [@aplavin](https://discourse.julialang.org/u/aplavin)
#### Post date: [April 21, 2026, 10:33am UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/6 "2026-04-21T10:33:24Z")
> [@marius311](#):
>
> I suppose keeping them separate MCPs allows users to optionally install one or the other in a given project.
That’s not always convenient – eg, I sometimes run AI in vscode window, sometimes standalone, in the same project. I don’t know what a good solution for this is, but would be great to have one 🙂
* * *
Also, a question about your mcp server: how does it handle two+ claude/codex sessions in the same vscode window?
---
### Author:  [@langestefan](https://discourse.julialang.org/u/langestefan)
#### Post date: [April 21, 2026, 10:44am UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/7 "2026-04-21T10:44:19Z")
Kaimon.jl can also do this, did you try that?
---
### Author:  [@marius311](https://discourse.julialang.org/u/marius311)
#### Post date: [April 21, 2026, 9:31pm UTC](https://discourse.julialang.org/t/letting-ai-agents-use-the-vscode-julia-repl/136805/8 "2026-04-21T21:31:54Z")
> [@aplavin](#):
>
> Also, a question about your mcp server: how does it handle two+ claude/codex sessions in the same vscode window?
They share the single integrated REPL within a given window.
> [@langestefan](#):
>
> [Kaimon.jl](https://juliaregistries.github.io/General/packages/redirect_to_repo/Kaimon) can also do this, did you try that?
I’ve seen it, looks very powerful! The approach here is the other end of the spectrum, simplest possible setup and only focused on the VSCode integrated Julia REPL and the AI tools it comes with.