Install on Windows

Rinari Agent is distributed as a Windows x64 installer. It installs the desktop app together with a self-contained Rinari Engine, so you don’t need Python or a separate engine to use the app.

Download

Get the installer from the Download button on rinari.ai or from the Releases page on GitHub. Read the notes of the release you download: they say what that build includes.

The installer isn’t signed yet

The installer does not carry an Authenticode code signature yet, so Windows may show an unknown publisher warning or a SmartScreen prompt before it runs. Only run an installer you downloaded from the official Releases page.

Updates delivered by the app are checked against a SHA-512 hash, which detects a corrupted or altered download. A hash confirms integrity, not who published the file.

Choose your options

The first screen, Customize your installation, has these options:

Option	What it does
Rinari Agent + Engine	Required. The desktop application and its self-contained engine.
Start menu shortcut / Desktop shortcut	Optional shortcuts that point to this installation.
Add Rinari CLI to PATH	Off by default. Lets you run rinari from any terminal.
Only for me / All users	Installation scope. All users requires administrator permission.
Installation folder	Where the program files go. The screen shows the required and available space.

The default folder is %LOCALAPPDATA%\Programs\Rinari Agent for Only for me and %ProgramFiles%\Rinari Agent for All users.

The installer follows your Windows language (Spanish for Spanish locales, English otherwise), and an ES/EN button switches it.

Add Rinari CLI to PATH

Tick this box if you want to use Rinari from a terminal. The installer adds its own cli folder to your PATH, with a rinari command that runs the bundled engine and already knows where the desktop app is. That’s what makes this work right after installing:

rinari desktop .

Open a new terminal after installing so it picks up the updated PATH. If the installer warns that another rinari command already resolves in PATH, a different rinari (for example, one installed from source) comes first; see Troubleshooting.

Install

Choose Install Rinari Agent. The installer verifies every file before it activates the installation, and Cancel is safe until that point. When it finishes, You’re ready. offers Run Rinari Agent, Open folder and View log.

On first launch the app asks you to set up a model provider. Continue with Connect a provider.

Update, repair or change the installation

When a new version is available, the notification bell tells you; open it to see the version and update when you want. You can also check from Settings → About (Check for updates). A downloaded update is applied with Install and restart: Rinari closes and reopens with the new version, and running turns and processes are interrupted. It runs the same installer and keeps your scope, shortcuts and PATH choice.

Update from the terminal

rinari update updates the desktop app and the CLI to the latest published release:

rinari update                 # shows what's pending and asks before applying
rinari update --check         # only reports; exits with 1 when something is pending
rinari update --desktop-only  # only the desktop app
rinari update --cli-only      # only this CLI

--yes applies without asking. If Rinari Agent is open, the update is handed to the app: confirm Restart and update in its window.

Running the installer again on a machine where Rinari Agent is installed opens Welcome back. with:

• Update — only when a newer verified version is available.
• Repair — verifies file hashes and restores damaged or missing files.
• Modify installation — change shortcuts, the CLI option and the scope.
• Uninstall — removes Rinari Agent from this computer.

Update, repair and uninstall need Rinari Agent to be closed.

Uninstall

Uninstalling removes the app, the bundled engine, the uninstall entry, the PATH entry the installer added and its own shortcuts. By default it keeps:

• your sessions, providers, credentials and preferences;
• your projects and workspaces, which are never part of the installation.

Delete temporary cache is a separate option, and it does not remove sessions, providers or credentials.

Coming from 0.2.x

Before updating: the first time 0.3 opens, Rinari’s database is migrated to the new schema. After that you can’t go back to 0.2.x with the same data — the older version refuses to open it. Your conversations, projects and providers are kept.

Everything you had in 0.2 shows up in the Default profile.

Coming from Rinari Code

If the older Rinari Code is installed, the installer detects it, keeps its location, migrates only its own shortcuts and replaces its program files in one transaction. The rinari code command keeps working as an alias of rinari desktop.