SeaShell 0.1.2
SeaShell 0.1.2
Terminal window manager for running several long-lived sessions — agents, dev
servers, plain shells — side by side, with a file explorer that knows what your
panes are talking about.
Downloads
| File | Platform | Notes |
|---|---|---|
SeaShell-0.1.2-universal.dmg |
macOS 11+ (Intel & Apple Silicon) | unsigned — see below |
SeaShell-0.1.2-windows-x64.zip |
Windows 10/11 x64 | experimental — see below |
SeaShell-0.1.2-linux-x86_64.AppImage |
Linux x64 | experimental — built in CI, not yet run on real hardware |
Installing on macOS
The app is not yet signed with an Apple Developer ID, so Gatekeeper refuses a plain
double-click the first time.
- Open the
.dmg, drag SeaShell to Applications. - Right-click → Open → Open once (or System Settings → Privacy & Security →
"Open Anyway").
Installing on Linux (experimental)
chmod +x SeaShell-*.AppImage && ./SeaShell-*.AppImage
Panes root at your $SHELL, falling back to bash. Live working-directory tracking
(and double-click path reveal for relative paths) needs zsh. Unit-tested in CI;
reports from real machines welcome.
Installing on Windows (experimental)
Unzip anywhere, run SeaShell.exe. SmartScreen warns on unsigned apps — "More
info → Run anyway".
Honest status: panes spawn PowerShell via ConPTY and terminal I/O works, but
process cleanup is weaker than on macOS (a detached process can outlive its pane,
uncounted), and there are no per-pane metrics or cwd tracking yet.
What's new since 0.1.1
- First Linux build — new platform layer rooting panes at the user's own shell
- CI on every push across macOS, Linux and Windows; Linux and Windows release
artifacts now built natively on runners instead of cross-built from a Mac - Windows zip is now built and unit-tested on an actual Windows host
Known limitations
- All builds unsigned — expect the OS warnings above
- No session persistence across restarts (saved Projects are layouts, by design)
- Linux and Windows are experimental; macOS is the reference platform