# \[ANN\] SpaceStation.jl: A workspace for Pluto notebooks (+ AI stuff)

**URL:** <https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017>\
**Category:** Package Announcements\
**Created:** [July 8, 2026, 11:52pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017 "2026-07-08T23:52:38Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [July 8, 2026, 11:52pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/1 "2026-07-08T23:52:38Z")

</div>

I am announcing this package for anyone to try out, but just copy-pasting the readme. It should be considered beta, but it works well so give it a go! I don’t touch windows much though so there might be more bugs on that side of things.

_TLDR: Similar to JupyterHub for Jupyter, but focused on Pluto. Fork of Pluto with terminal and file browser. The reactivity mode is changed just slightly, making it really seamless to work alongside agents on the same notebook without restarts_

# ![](https://global.discourse-cdn.com/julialang/original/3X/3/3/33691c47b70a66e7f1f4ea3f2daf7f9f69ee75b6.svg)&nbsp;SpaceStation.jl

### A workspace for Pluto notebooks — for humans and agents.

[Pluto.jl](https://github.com/fonsp/Pluto.jl) gives you a reactive notebook.  
**SpaceStation gives you the _space_ around it:** a folder workspace, tabbed notebooks and files,a real terminal, point-and-click SSH remotes, outputs that survive restarts, and first-class **human + agent collaboration** on one live session — all on the unmodified Pluto editor.

  

 ![SpaceStation: a PlutoUI slider driving a live WasmMakie plot (sin at the slider's frequency) rendered to a browser canvas, with the workspace file tree and table of contents](https://global.discourse-cdn.com/julialang/original/3X/4/0/40c9bc3559fc17d1cf5904a1643f29e8e2c6c69e.png)

## Install & run

SpaceStation installs as a **Julia [Pkg App](https://pkgdocs.julialang.org/dev/apps/)** — one command puts a real `spacestation` executable on your `PATH`, so it launches like any CLI tool (no `julia -e …`, no manual `import`):

```julia
julia> import Pkg; Pkg.Apps.add("SpaceStation.jl")

```

```sh
$ spacestation # workspace picker
$ spacestation ~/project # open a folder as a workspace
$ spacestation notebook.jl # open a single notebook
$ spacestation --help

```

Prefer it as a library? `import SpaceStation; SpaceStation.run()` works too (every `Pluto.run` keyword applies). Lazy/collab mode is the default; add `--autorun` for classic Pluto reactivity.

> Want to try everything below hands-on? There’s a ready-made demo workspace with a guided  
> shot list: **[spacestation-demo](https://github.com/GroupTherapyOrg/spacestation-demo)**.

* * *

# What SpaceStation adds to Pluto

Everything in this section is something **vanilla Pluto doesn’t have.** The notebook engine, editor, reactivity, `@bind`, packages, and the `.jl` file format are all Pluto’s — and notebooks stay **byte-for-byte compatible in both directions.** SpaceStation only adds the space around them.

| | |
| --- | --- |
| 📁 [Open a folder as a workspace](#-open-a-folder-as-a-workspace) | 🪟 [Notebooks & files are tabs](#-notebooks-and-files-are-tabs) |
| 💻 [A real, persistent terminal](#-a-real-persistent-terminal) | 🌐 [SSH remote workspaces](#-ssh-remote-workspaces) |
| 🤝 [Lazy mode — humans + agents, one session](#-lazy-mode-humans-and-agents-on-one-live-session) | 💾 [Two files; outputs survive restarts](#-two-files-and-outputs-that-survive-restarts) |

* * *

## 📁 Open a folder as a workspace

SpaceStation starts where an IDE does: a **VS Code-style “Open Folder”** hub with recent workspaces, a filesystem browser, and (if you have SSH hosts) one-click remotes. Pick a folder and its file tree becomes your sidebar — notebooks and files open as tabs beside it.

 ![The SpaceStation workspace opener (light theme): a folder browser to open any directory as a workspace, plus a list of SSH remote hosts below](https://global.discourse-cdn.com/julialang/original/3X/d/9/d99e79b7fe810b947be9c7a66b923ada0a461b40.png)

* * *

## 🪟 Notebooks and files are tabs

Notebooks open as tabs — each one the **unmodified Pluto editor** in its own session. Plain files open in tabs too, edited with the same CodeMirror — including the per-notebook `*.pluto-cache.toml` sidecar, which is just readable TOML. Add and delete files right from the tree.

 ![A notebook open as a tab in SpaceStation, with the file-tree sidebar, a WasmMakie plot rendered inline, and a table of contents](https://global.discourse-cdn.com/julialang/original/3X/2/a/2a5a86f9f7476e65cc0c3d75ef2287eb2fd5a405.png)

* * *

## 💻 A real, persistent terminal

An integrated **PTY shell** runs in the workspace folder. Dock it bottom, right, or as an editor tab; and — unlike a browser terminal — it’s a **persistent session** : refresh the page and the shell keeps running, replaying its scrollback on reconnect (tmux semantics, no tmux). It also exports `PLUTOSPACE_PORT`/`PLUTOSPACE_SECRET` and puts `pluto-collab` on `PATH`, so a coding agent launched here just works.

 ![The integrated terminal docked at the bottom of the editor, showing the SpaceStation live-session banner and a shell prompt in the workspace directory](https://global.discourse-cdn.com/julialang/original/3X/b/6/b6a1944d640a71748c317605612dd60bc4965157.png)

* * *

## 🌐 SSH remote workspaces

Click a host from your `~/.ssh/config` and the **entire workspace** — files, kernels, terminal, the agent API — runs on that machine over an SSH tunnel. First contact installs SpaceStation on the remote; after that it reconnects instantly. The VS Code Remote-SSH model, with zero config beyond your SSH setup.

 ![The SSH remotes list in the SpaceStation opener (light theme) — click a host to run the whole workspace (files, kernels, terminal) on that machine over an SSH tunnel](https://global.discourse-cdn.com/julialang/original/3X/8/9/89ec8268b081d44f3e159bc4716e72dc7e5056f1.png)

* * *

## 🤝 Lazy mode: humans and agents on one live session

SpaceStation’s default isn’t autorun. Editing a cell — **in the browser _or_ on disk** — marks it (and everything downstream) **stale** instead of running it, so a run executes only the stale closure. Because of that, a human in the browser and a coding agent in a terminal can work on the  
**same live notebook** at once — same kernel, same state. The agent edits the `.jl` with its normal file tools; the affected cells turn **amber within a second** in the browser, and a run applies them. No MCP, no plugins — just a small CLI, [`pluto-collab`](https://github.com/GroupTherapyOrg/SpaceStation.jl/blob/main/bin/pluto-collab).

 ![Lazy mode in SpaceStation: after an edit to the report cell, only it and its dependent turn amber (stale) while the expensive samples and smoothed cells stay green — two notebook tabs and the integrated terminal are open](https://global.discourse-cdn.com/julialang/original/3X/0/2/02b4efa45004d052a530e07f2dac0ec8b0d42bdd.png)

The agent surface is deliberately **two-tiered** — editing and executing are separate steps:

1. **Edit → _stage._** The agent edits the `.jl` with its normal file tools. That only marks the changed cells (and everything downstream) **stale** — _nothing runs_. The human watches them turn amber within a second.
2. **Run → _apply._** An explicit `run --stale` executes only the stale closure. Separating stage from apply is deliberate: you review what’s about to run, expensive cells don’t fire on every keystroke, and the session stays reproducible.

The mechanism is plain — no MCP, no plugins:

- a **connection file** at `~/.local/state/pluto/servers/<node>-<port>.json` (port + secret — the Jupyter idiom),
- a plain **HTTP API** at `/api/v1/…` (curl-able, authed with `?secret=…`),
- a tiny **CLI** , in two equivalent front-ends:

```sh
pluto-collab status nb.jl # Unix shorthand — a bash script (curl + sed)
spacestation collab status nb.jl # any platform incl. Windows PowerShell — built into the app, no deps

# the flow (either front-end — same commands, arguments, and exit codes):
… status nb.jl # REVIEW: per-cell STALE / COLD / ERRORED / output (reflects the file right now)
… run nb.jl --stale # APPLY: run exactly what's outdated (blocks; exit 1 on error)
… output nb.jl --cell <id> # read a cell's full, untruncated output
… figure nb.jl --cell <id> # save a cell's rendered plot to an image file

```

`pluto-collab` needs bash + curl (Unix); **`spacestation collab …` is the identical command set built  
into the app** with no external dependencies, so the surface works the same in a Windows terminal.  
Inside a SpaceStation terminal, `PLUTOSPACE_PORT` / `PLUTOSPACE_SECRET` point either one at the live  
session automatically.

Two guarantees make the loop reliable:

- **`status` always reflects the file.** It re-syncs from disk on every call, so _immediately_ after an edit it reports the true stale set — the review step never lags the ~½-second file watcher.
- **Runs share the browser’s execution queue.** HTTP runs go through the same path as browser clicks, so both sides see cells turn amber → running → green live. Staleness is verified against content-addressed **execution keys** , so reverting an edit un-stales a cell with no run at all.

See **[COLLAB.md](https://github.com/GroupTherapyOrg/SpaceStation.jl/blob/main/COLLAB.md)** for the full details and an `AGENTS.md` stanza you can drop into any repo.

* * *

## 💾 Two files, and outputs that survive restarts

Every notebook is **two files** : the `.jl` (your code — the source of truth, unchanged from vanilla Pluto) and a plain-TOML **`<notebook>.jl.pluto-cache.toml`** sidecar holding every cell’s output plus its execution key. Reopen a notebook and **every output is restored instantly** from that sidecar — no recompute. Vanilla Pluto has no output persistence; it either re-runs everything on open or shows nothing.

| ![A notebook reopened WITH its .pluto-cache.toml sidecar: every output restored instantly, no recompute](https://global.discourse-cdn.com/julialang/original/3X/3/8/380cfbf758eeb6dab2ee8c077197d58b1b55e564.png) | ![The same notebook reopened WITHOUT its sidecar: every cell shows 'Code not executed' — vanilla Pluto has no output persistence](https://global.discourse-cdn.com/julialang/original/3X/1/4/14ebb6b6e407d6d25e3be6d4e498205febf410b5.png) |
| _ **With** the sidecars → outputs restored on open_ | _ **Without** them → "Code not executed" (plain Pluto)_ |

_Same notebook, same fresh restart — the sidecar is the only difference. Restored cells are trusted **only when their execution keys match** the current code and upstream results; impure cells (`rand()`, the clock, I/O) opt out with `always_stale = true`._

* * *

## Relationship to Pluto.jl

SpaceStation is a friendly fork of [Pluto.jl](https://github.com/fonsp/Pluto.jl). The notebook engine, editor, file format, and reactivity are Pluto’s, and notebooks remain fully compatible in both directions. For everything about notebooks themselves (reactivity, `@bind`, packages, exporting), see the [Pluto documentation](https://plutojl.org/). 🎈

SpaceStation adds the _space around_ the notebooks: workspaces, tabs, terminal, remotes, persistence, and first-class human + agent collaboration. `--autorun` gives you classic Pluto reactivity whenever you want it, byte-for-byte.

**SpaceStation is developed and owned by Dale Black / [GroupTherapyOrg](https://github.com/GroupTherapyOrg). It is an independent fork and is NOT developed, maintained, or endorsed by the Pluto.jl team** — please direct SpaceStation questions, issues, and feedback to this repository, not to the Pluto developers.

## Status

⚠ **Early and experimental.** SpaceStation is under active development by a small team; expect rough edges and breaking changes. Issues and ideas are welcome on this repo.

## AI disclosure

Much of SpaceStation’s code is written with AI assistance (Claude). Commits are co-authored accordingly.

## License

MIT — see [LICENSE](https://github.com/GroupTherapyOrg/SpaceStation.jl/blob/main/LICENSE). SpaceStation is developed and owned by Dale Black / GroupTherapyOrg. It builds on **Pluto.jl** (© the Pluto.jl authors — Fons van der Plas and contributors, MIT), which retains its own copyright; the original Pluto license is preserved in [LICENSE](https://github.com/GroupTherapyOrg/SpaceStation.jl/blob/main/LICENSE).

---

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [August 11, 2026, 12:52pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/2 "2026-08-11T12:52:36Z")

</div>

@Dale_James_Black Is there something fundamental I’m missing?

I was trying this out, but the sidebar that according to your screenshot is supposed to show subfolders and notebooks is basically empty for me (it only shows _hidden_ folders):

 ![CleanShot 2026-08-11 at 08.50.12@2x](https://global.discourse-cdn.com/julialang/original/3X/1/3/139f92fe698fb77aeea2e978cec1642f28628c53.png)

So I don’t seem to be able to do anything.

As you can see from the terminal, there are subfolders and `.jl` files that are Pluto notebooks in the workspace folder.

Any hints?

---

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [August 11, 2026, 7:17pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/3 "2026-08-11T19:17:36Z")

</div>

I had Claude take a look at what’s going on.

Turns out, it was just a bug: the `.venv` folder contained a lot of files, and that choked the server.

Here’s a fix: [Fix the workspace sidebar hiding files behind one large folder - Pull Request #24 - GroupTherapyOrg/SpaceStation.jl - GitHub](https://github.com/GroupTherapyOrg/SpaceStation.jl/pull/24)

---

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [August 18, 2026, 6:24pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/4 "2026-08-18T18:24:30Z")

</div>

I’ve got to say, `SpaceStation` is an absolute game changer, and fixes pretty much everything that’s always made it difficult for me to work with Pluto. I’ve already heavily advertised it to the rest of my group and other colleagues. As far as I’m concerned, this is what Pluto should be out of the box.

With Fons [retiring from Pluto maintenance](https://discourse.julialang.org/t/im-quitting-as-pluto-jl-maintainer/138028) and

> [@I'm quitting as Pluto.jl maintainer waving\_hand](https://discourse.julialang.org/t/im-quitting-as-pluto-jl-maintainer/138028/1):
>
> from my side, Pluto is… [done](https://discourse.julialang.org/t/pluto-1-0-release/137296)

I might suggest that `SpaceStation` should be the evolution of a “retired” Pluto project, and where we continue that amazing lineage.

Apart from the bugfix you already merged, there have been a few “fixes” that I made on top `SpaceStation` to adapt to to my preferences:

 ![Modified SpaceStation UI](https://global.discourse-cdn.com/julialang/original/3X/5/a/5aa5a3d1e995b508077fea647edc57bd57297b70.webp)

1. Most importantly, I’ve fixed the terminal to not always be in dark mode. It _should_ adapt to the chose color scheme (and I’d say that’ the objectively correct behavior), but personally, I only care about light mode, so that might need further testing.
2. I tend to work on several projects at same time and may get lost between my browser windows (that was on of the _major_ issues I had with the original Pluto). I like to see the project (folder) name as part of the UI. I’ve added a feature to show the workspace folder under the SpaceStation wordmark in the top left corner, as you can see in the screenshot
3. I’ve made a fix to typeset math in Safe preview outputs. That’s actually an issue in the original Pluto and I could potentially contribute it there.
4. I’ve added a button to open a notebook’s package environment in a terminal from the editor. That’s the terminal button you see in the screenshot to the left of the export button. This one might be considered a bit gimmicky, but I occasionally use this feature, and I can never remember the invocation for “connect to the notebook’s automatic environment”
5. I’ve added support to switch notebook tabs with `cmd+shift+[` / `cmd+shift+]`. This one is mac-specific, and maybe a personal preference, but it’s part of my muscle memory.

Some of these I would consider bug fixes that I’d definitely want to contribute back, some are what I think would be genuine UI improvements (but a matter of opinion), and some might be questionable personal preferences. How do you feel about any of these modifications? Should I submit a chain of PRs for any or all of these?

Since this is a _fork_ of Pluto, do you intend to keep up with upstream bugfixes, or do you want the development of `SpaceStation` to continue completely independently?

---

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [August 18, 2026, 8:04pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/5 "2026-08-18T20:04:38Z")

</div>

Thank you so much for investing in this! I have plans to implement quite a few fixes regarding ssh flakiness. So when I do that, if you want to share issues, even if they are half baked into the github ([Issues · GroupTherapyOrg/SpaceStation.jl · GitHub](https://github.com/GroupTherapyOrg/SpaceStation.jl/issues)) please do! I will see which ones I can add properly right from the get go! Hopefully you will be pleased and will not need to use a fork of a fork once this is all implemented!

---

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [August 18, 2026, 8:05pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/6 "2026-08-18T20:05:45Z")

</div>

Also, I missed your last part. I am trying to keep up with upstream bugfixes. Right now its up to date!

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

---

<div class="post-metadata">

**Author:** ![langestefan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/langestefan/32/207923_2.png) [@langestefan](https://discourse.julialang.org/u/langestefan)\
**Post date:** [August 18, 2026, 8:44pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/7 "2026-08-18T20:44:25Z")

</div>

SpaceStation.jl is awesome! I’m definitely having fun with it. Maybe this will finally get me into Pluto.jl 🙂

Just wondering, what is the bus factor? If more people start using it, maybe the current Pluto maintainers would be open to hosting it in their org, to make maintenance more robust?

---

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [August 18, 2026, 8:46pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/8 "2026-08-18T20:46:55Z")

</div>

I would be happy to move anything to Pluto org. With Fons out of commission though I am not sure what to expect

---

<div class="post-metadata">

**Author:** ![langestefan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/langestefan/32/207923_2.png) [@langestefan](https://discourse.julialang.org/u/langestefan)\
**Post date:** [August 18, 2026, 8:51pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/9 "2026-08-18T20:51:31Z")

</div>

It’s not dead, just no longer maintained by Fons himself

> [@I'm quitting as Pluto.jl maintainer waving\_hand](https://discourse.julialang.org/t/im-quitting-as-pluto-jl-maintainer/138028/1):
>
> I will stop contributing to Pluto projects today. I will stay connected to the project until the end of 2026 to make sure that the transition goes well. But from my side, Pluto is… [done](https://discourse.julialang.org/t/pluto-1-0-release/137296)! It will need to be maintained for future Julia versions, and I hope that the community will contribute. **There are still [other core developers](https://plutojl.org/en/docs/governance/) available (notably @pankgeorg) to help with PRs and issues.**

---

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [August 18, 2026, 9:30pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/10 "2026-08-18T21:30:06Z")

</div>

Yup, not dead at all, just no Fons and so not sure what the future vision is beside maintenance

---

<div class="post-metadata">

**Author:** ![pitsianis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pitsianis/32/26588_2.png) [@pitsianis](https://discourse.julialang.org/u/pitsianis)\
**Post date:** [August 21, 2026, 5:52pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/11 "2026-08-21T17:52:44Z")

</div>

Can somebody provide a comparison between SpaceStation.jl and KaimonSlate.jl they seem to “occupy” a similar region?  
I am grateful that Julia has such productive developers.

---

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [August 21, 2026, 6:01pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/12 "2026-08-21T18:01:10Z")

</div>

SpaceStation.jl and KaimonSlate.jl are related but differ in two key ways as far as I see it:

- Instead of reinventing the wheel, SpaceStation.jl is essentially Pluto with a few tweaks. I actually tried building a platform from scratch months ago, similar in concept to KaimonSlate.jl ([Sessions.jl](https://github.com/GroupTherapyOrg/Sessions.jl)) before realizing Pluto already does most of what I need, and instead my time would be better served by just providing some infrastructure around Pluto.jl
- SpaceStation.jl is designed to be _human-driven and AI-assisted_. In contrast, KaimonSlate.jl feels more _AI-driven with human assistance_. This is my opinion though and might not reflect the author’s intention/opinion of KaimonSlate.jl

---

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [August 22, 2026, 6:05pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/13 "2026-08-22T18:05:41Z")

</div>

I just released v0.3.0 – this includes the dark/light toggle, your safe preview fix, and the project folder visual:

 ![image](https://global.discourse-cdn.com/julialang/original/3X/e/e/ee1d772afaf7f8976298df551bc84ee1aa0672bc.jpeg)  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/2/d/2d126dbdb272bdfe229df223d96767fef7868a21.jpeg)  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/2/7/27fd664bf2ed270c7678179543ff01b30b46ff8d.jpeg)

I also added an issue to track your #4 and #5 comments. I want to revisit those soon.

I also added some ssh fixes in this release. Let me know if you see any issues with this release!

---

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [August 22, 2026, 6:59pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/14 "2026-08-22T18:59:45Z")

</div>

Wow! Thanks! That’s pretty amazing… I was actually going to submit some PRs for these, but I didn’t have a chance yet to put any time into this (too much stuff going on). I don’t know if you used any of the code from [my fork](https://github.com/goerz/SpaceStation.jl), but, feel free to, obviously. It’s all implemented by Claude anyway, I was just iterating with it how I want things to look like and behave.

I’ll definitely look at the release and give you some feedback in the next week or sor.

---

<div class="post-metadata">

**Author:** ![Dale\_James\_Black](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dale_james_black/32/11595_2.png) [@Dale\_James\_Black](https://discourse.julialang.org/u/Dale_James_Black)\
**Post date:** [August 26, 2026, 4:26pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/15 "2026-08-26T16:26:14Z")

</div>

Please consider this super duper alpha version, but I have been playing around with a desktop app for SpaceStation.jl if anyone wants to give it a try. I only have a mac so windows/linux are likely super buggy, but if you are interested I would love to know what the bugs are:

> **[Release v0.4.5 · GroupTherapyOrg/SpaceStation.jl](https://github.com/GroupTherapyOrg/SpaceStation.jl/releases/tag/v0.4.5)**
>
> 0.4.5 (2026-08-25)
> Bug Fixes
> 
> window dragging via a native bridge, and recreate stale WKWebView scrollers (#49) (19ba976)
> 
> Install the desktop app
> No Julia needed — the app installs one for you (bu...

Should be easy enough to download and run (I hope)

 ![image](https://global.discourse-cdn.com/julialang/original/3X/6/1/616376b10965cd091f6825980dbb15a74b4fe26e.png)  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/6/e/6ef0a11614f73049c9890ce0be20d0d543c12e42.png)

---

<div class="post-metadata">

**Author:** ![Cato](https://avatars.discourse-cdn.com/v4/letter/c/9dc877/32.png) [@Cato](https://discourse.julialang.org/u/Cato)\
**Post date:** [August 29, 2026, 11:40am UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/16 "2026-08-29T11:40:25Z")

</div>

Hi, @Dale_James_Black I installed SpaceStation.jl on my Windows 11 machine and it looks just great! I tried it with a set of Pluto notebooks and managing them with your package is as smooth as it takes, and many times faster than the usual Pluto style. Congratulations.

I also tried to install the desktop version of your app on the same computer, but the desktop app is nowhere to be seen. Apparently, the installation was successful (no error was produced during the installation), but it disappeared somewhere on my computer.

---

<div class="post-metadata">

**Author:** ![Ay11](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Ay11](https://discourse.julialang.org/u/Ay11)\
**Post date:** [August 29, 2026, 5:46pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/17 "2026-08-29T17:46:41Z")

</div>

Does spacestations.jl support multiline cell without using begin … end.

---

<div class="post-metadata">

**Author:** ![Nathan\_Boyer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nathan_boyer/32/14825_2.png) [@Nathan\_Boyer](https://discourse.julialang.org/u/Nathan_Boyer)\
**Post date:** [August 31, 2026, 2:55pm UTC](https://discourse.julialang.org/t/ann-spacestation-jl-a-workspace-for-pluto-notebooks-ai-stuff/138017/18 "2026-08-31T14:55:47Z")

</div>

The desktop app works for me now on Windows after a patch last weekend.  
See [Desktop Application Does Nothing on Windows 11 · Issue #55](https://github.com/GroupTherapyOrg/SpaceStation.jl/issues/55#issuecomment-5479038111). You will need to fully uninstall and reinstall. Then search for “SpaceStation” in the start menu after installation to launch the application.

> [@Ay11](#):
>
> Does spacestations.jl support multiline cell without using begin … end.

No, the internal notebook is still using Pluto, so all Pluto’s rules still apply.