TERMINAL
A real shell, ⌘J away
Sheru — シェル, Japanese for shell — is built around the one thing Finder never gave you: a real command line, one keystroke away. Press ⌘J and a genuine zsh slides up, already sitting in the folder you're looking at. Browse, and the shell follows; cd, and the browser follows. On an SSH connector the same keystroke opens a shell on the remote machine.
THEMES
Wear any decade
The interface is a contract — tokens and parts — and themes fill it in. Aqua, Windows 98, XP, 7, and XFCE ship built in; fully custom themes go as far as you care to take them. Native mode is pure macOS controls; web mode repaints everything. Watch the laptop above re-skin itself.
STORAGE
Remote filesystems, nothing mounted
Connect S3-compatible object storage (R2 included), WebDAV, SFTP, FTP, and SMB, and browse them like plain folders. Nothing is mounted into macOS — no kernel extensions, no system changes, credentials stay on your Mac. Copy-paste to upload. SSH goes all the way: rename, move, and edit in place, like local disk.
SERVICES
Services as file trees
Service connectors project GitHub, Linear, and Notion as read-only file trees — repositories, issues, PR threads, pages, databases. Read issue.md, scroll the comments folder, then run real actions: comment, close. GitHub rides your existing gh login, so Sheru stores no tokens of its own.
FILES
Everything is a file
The oldest idea in Unix, carried all the way. A GitHub issue is a markdown file in a folder. Your inbox is a directory. A dev box over SSH browses like a local drive. One browser, one set of habits, for everything you touch.
github/octocat/hello-world/Issues/42/issue.mdEXTENSIONS
Built to be extended
Two independent axes: extensions add function — new connectors, new commands — and themes add presentation. They never touch, so any theme renders any extension. Author either against the SDK and the token/part contract.