# \[ANN\] julia-client — persistent Julia sessions as CLI

**URL:** https://discourse.julialang.org/t/ann-julia-client-persistent-julia-sessions-as-cli/137330
**Category:** Package Announcements
**Tags:** ai
**Created:** [May 29, 2026, 1:12am UTC](https://discourse.julialang.org/t/ann-julia-client-persistent-julia-sessions-as-cli/137330 "2026-05-29T01:12:31Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)
#### Post date: [May 29, 2026, 1:35pm UTC](https://discourse.julialang.org/t/ann-julia-client-persistent-julia-sessions-as-cli/137330/6 "2026-05-29T13:35:53Z")

</div>

Nice to see this space explored! There are definitely pros/cons to both the [julia-mcp](https://discourse.julialang.org/t/ann-julia-mcp-persistent-julia-sessions-for-ai-assistants/135386) and this kind of standalone CLI tool approach. The main tradeoff is:

- MCP: **(+)** no lifecycle/lingering daemons to manage, julia sessions are scoped to AI sessions, naturally handles multiple independent sessions per julia env, works on all OS; **(-)** AI-specific, infeasible to use from outside.
- standalone CLI: **(+)** benefits all of AI / users / scripts equally, can be used anywhere; **(-)** necessary to have long-running background processes, need special plumbing to get multiple independent julia sessions for the same folder.

I don’t know if it’s possible to somehow get best of both worlds… 🙂

// also cc @tecosaur who worked on something similar recently

---

_[View the full topic](https://discourse.julialang.org/t/ann-julia-client-persistent-julia-sessions-as-cli/137330)._