I shipped BashISE (bise2) — a local-first GUI editor + Bash runner for Linux that’s built around one obsession:
Don’t lose work. Ever.
What it does
BashISE is a lightweight “ISE-style” workflow for Bash on Linux:
open/edit scripts
run with args
keep outputs visible
keep your work safe even when you’re moving fast
The doctrine (the whole point)
Every design choice follows these rules:
Atomic writes
Changes are written safely (temp → replace). No partial files.
Backup on every write
If you save, a backup is created. Always.
JSON receipts
Each action can emit a receipt so you can prove what happened: what/where/when.
Offline-first
No cloud dependency. This is a local tool for local work.
Quick proof / selftest
Run this and you’ll get a clean “OK” plus backup + receipt paths:
BISE2_ARMORY_SELFTEST=1 bise2
Repo
Feedback I’d love
UX: what feels clunky in the editor/run flow?
Packaging: what install method do you expect for a Linux GUI tool like this?
Repo + install instructions:
https://github.com/TrishulaSoftware/BashISE
Quick proof / selftest:
BISE2_ARMORY_SELFTEST=1 bise2
I’m mainly looking for feedback on UX + packaging expectations for CLI/GUI tools in this space.
Built by Trishula Software.
Support links are in the repo (Sponsors / Ko-fi / BuyMeACoffee / OpenCollective). Patreon exists but isn’t monetized yet.
Top comments (0)