Get in touch
No public release yet. The links below point at a placeholder releases page, and the install scripts and installers will only work once the first release is published. The steps are accurate to the current build.
Install

Download & install

Two ways in, and either can come first. They know about each other and never install anything twice. Everything you download is checked against a published SHA-256 sum before it is installed.

Download

Sill for Windows

.exe · per-user

The desktop app. It bundles wros and sill-core and sets everything up on first start.

Open releases page

Sill for Debian / Ubuntu

.deb

The desktop app as a package. It puts wros in /usr/bin.

Open releases page
wros-setup-windows-x86_64.exe

The command line for Windows. No administrator rights; adds itself to your user PATH.

Open releases page
install.sh · install.ps1

One-line installers for Linux and Windows terminals. See below.

Jump to the commands

The releases page also lists SHA256SUMS. Sill for macOS is not available yet; wros itself does support macOS shells for PATH setup.

Requirements

  • Windows 10 or 11, or a Debian-family Linux (Debian, Ubuntu) for the Sill desktop app.
  • A terminal for wros. No administrator rights are needed on Windows; the Linux script installs into ~/.local/bin without sudo.
  • An internet connection for the first install, which fetches the cores you choose. After that Sill works against your local data.
  • For Sill on the web: a modern browser on the same computer. The web UI is served only to this machine.
Honest status. The Linux install has not yet been run on a real machine, and wros update self-replacement has only been exercised by tests and dry runs.

Install steps

Pick one way. If you are unsure, take the Sill app: it needs no terminal.

Way 1: the terminal first

Install wros

$ curl -fsSL https://github.com/TODO-releases-repo/releases/latest/download/install.sh | sh

Installs wros and sill in ~/.local/bin (change with WROS_INSTALL_DIR) and checks them against SHA256SUMS. Options: --modify-path, --version 0.2.0, --uninstall.

Choose what to install

This fetches the cores you pick (and the desktop app, if you want it), each file checked.

$ wros install -d            # recommended + the desktop app
$ wros install -m            # minimal: email only
$ wros install -c email,tasks # exactly these (plus what they need)

The recommended set is email, calendar, tasks, contacts, codes, media and PDF. Installing is additive: you can run it again to add more.

Start it

$ wros up           # start the core in the background
$ wros sill up      # open the Sill app

Way 2: the Sill app first

Run the Sill installer

Run the .exe on Windows, or install the .deb on Debian or Ubuntu. It installs the app per user and bundles wros and sill-core next to it.

# Debian / Ubuntu
$ sudo dpkg -i ./<downloaded-file>.deb

Start Sill

On its first start the app registers itself, starts the core it bundled, and shows a setup page: Minimal, Default or your own choice. It fetches the cores you pick, with progress, and opens the first section.

Use it from a terminal too (optional)

The installer does not edit your PATH without asking. Run this once, then open a new terminal. It is the same wros the app uses.

$ "<app folder>\wros.exe" path add   # Windows

On Debian and Ubuntu the .deb already puts wros in /usr/bin.

If you do both

Nothing is installed twice, and nothing conflicts.

You didWhat happens
Sill app, then the install scriptThe script finds the bundled wros, says where it is, and installs nothing. --force installs a second copy anyway.
Sill app, then wros install -dSays "Sill is already installed"; fetches the cores only. The app's setup page then has nothing left to ask.
wros, then wros install -dThe app installs with its own wros bundled and registers itself. Cores already fetched are reused. Either wros may be used.

There is always one background core (an instance lock), one start-at-login entry, one choice of components, and one database and key.

First run

Check that everything is up, then connect an account.

$ wros version
$ wros status
$ wros account connect gmail --email you@gmail.com   # opens your browser to sign in
$ wros email list --limit 5

Programs fetched by wros live in one folder, ~/.sill/bin (on Windows %USERPROFILE%\.sill\bin), never inside an app's folder. Your database lives in the data folder (on Windows %APPDATA%\Sill); logs, backups and run files live in ~/.sill.

Want it running whenever you sign in? wros autostart on.

PATH

wros path add changes only your own settings, needs no administrator rights, is safe to run twice, and wros path remove undoes exactly it.

  • Windows: your user Path in the registry (HKCU\Environment), written as Unicode so names with accents or Chinese characters are safe.
  • Linux and macOS: a marked block (# >>> wros >>>) in the files your shell reads: ~/.profile, plus ~/.bashrc, ~/.zshrc or ~/.config/fish/conf.d/wros.fish depending on your shell.

Open a new terminal afterwards; programs that were already running need a restart.

Update & remove

$ wros update --check       # see what is available
$ wros update               # core, cores, the app and wros itself
$ wros component remove tasks  # take a component out (its data stays)

A release that changes stored data in a way an older core cannot read asks for --allow-breaking and backs your data up first to ~/.sill/backups/. You can also run wros backup and wros restore <dir> yourself.

Your data is never deleted by an uninstall. Uninstalling the Sill app, the wros setup program, or install.sh --uninstall removes programs only. The database key is not part of a backup: keep it with your keychain or db.key.

Troubleshooting

"command not found: wros"

The install folder is not on your PATH. Run wros path add (using the full path if needed), then open a new terminal.

"the tasks component is not installed" (WROS-E317)

Run the fix it prints: wros install -c tasks.

Toasts do not appear on Windows

Run wros notify test, and check Focus assist / Do not disturb.

Anything else

wros doctor reports the data directory, the database and which mode a command would run in. wros logs -f follows the system log.