Install

Sirio ships a tagged release for all three platforms. macOS leads, Linux and Windows follow it.

One command

macOS and Linux

curl -fsSL https://dl.sirioai.app/install.sh | sh

Windows

powershell -ExecutionPolicy ByPass -c "irm https://dl.sirioai.app/install.ps1 | iex"

The script fetches the release for your platform and puts it where the operating system expects it: Sirio.app in /Applications (or ~/Applications when you cannot write to /Applications), the AppImage in ~/.local/bin as sirio, and on Windows Sirio itself under %LOCALAPPDATA%\Programs\Sirio, where the per-user installer puts it when the script runs it silently. Neither script asks for elevated access, and running one again upgrades the install in place.

Two variables change what the shell script does. SIRIO_VERSION=0.38.0 pins a version instead of taking the newest, and SIRIO_INSTALL_DIR picks the Linux directory. SIRIO_VERSION works on Windows too: set $env:SIRIO_VERSION = '0.36.0' before you run the command. Both scripts live in the repository, as install.sh and install.ps1, if you would rather read one before piping it.

What a release is

Every artifact is on the releases page if you prefer to download one yourself. On an Intel Mac or an ARM Linux machine the shell script stops and points you to building from source. On ARM Windows the x86_64 installer runs under emulation.

The Linux install script also registers Sirio with your desktop: it copies the AppImage’s desktop entry and icon into your user account, so launchers that list installed applications offer Sirio.

sirioctl

The Windows installer and the Linux AppImage carry both binaries, sirio (the app) and sirioctl (the control-socket CLI), side by side. The macOS app carries sirio alone, so on a Mac Sirio uses a sirioctl from your PATH, such as one you build from source.

When it starts, Sirio takes the first sirioctl it finds, next to itself or on your PATH, and places it at ~/.local/share/Sirio/bin/sirioctl (under $XDG_DATA_HOME when you set it), or at %LOCALAPPDATA%\Sirio\bin\sirioctl.exe on Windows. That gives agent hooks an absolute path, whatever the shell’s PATH says. Sirio refreshes that copy at every launch, so it matches the running Sirio.

Sirio also links the copy onto your PATH, so sirioctl works in any terminal. See On your PATH.

macOS permissions

Sirio asks macOS for nothing when it starts. A tool or an agent in one of its panes runs inside Sirio’s privacy envelope, so macOS asks on Sirio’s behalf the first time that tool needs, say, Screen Recording. Settings → Permissions shows the real state of each permission Sirio can use and lets you request one; see Permissions.

Tools some features use

Two features reach for tools of your own when you use them:

• Pull and merge requests sign in with a gh or glab you are already logged in with, or with a personal access token you paste in: read access to pull requests, checks and metadata on GitHub, the read_api scope on GitLab. Settings → Git Hosting manages each host; see Pull and merge requests.
• PlantUML diagrams in the Markdown preview need plantuml 1.2023.9 or newer on your PATH, or a PlantUML server you name in Settings → General. Mermaid diagrams need nothing; see Markdown preview.

Updates

Release builds read their channel’s manifest, download the artifact it names for your platform (Stable in the background, Nightly when you choose to update), check its SHA-256 hash and Ed25519 signature against the keys the app carries, and install it when you press the update button in Settings → General. On macOS and Linux the new version takes the installed one’s place while the running Sirio carries on until you next start it, and on Windows the installer closes Sirio and starts it again. A quiet indicator in the status bar says when a version is ready. See Updates and channels.

Build from source

With a stable Rust toolchain, Zig 0.15.2 and sccache you can build Sirio yourself. Windows also needs the MSVC toolchain, and Linux needs the GTK 3 and WebKitGTK 4.1 development packages. See Build from source.