Rinari
ESDownload

Rinari docsWorking with Rinari

CLI ↔ desktop

Open the current folder or a specific session in Rinari Agent with rinari desktop, and how the command finds the app.

You are here

The CLI and the desktop app are two clients of the same engine. Sessions, providers and project state live in the engine, so you can start in the terminal and continue on the desktop without losing history.

Open the desktop app from a terminal

From the folder you’re working in:

rinari desktop .

It opens Rinari Agent on that project. To continue a specific session:

rinari desktop . --session <session-id>

If the app is already open, the request goes to the running window instead of starting a second one.

  • rinari code is a compatibility alias of rinari desktop.
  • rinari agent is a different command: it runs a task in the terminal and doesn’t open the desktop app.

How rinari desktop finds the app

The command looks for the desktop executable in this order, and never guesses install locations:

  1. The --binary <path> option.
  2. The RINARI_AGENT_BIN environment variable.
  3. RINARI_CODE_BIN, the older name.
  4. rinari-agent on PATH.
  5. rinari-code on PATH, the older name.

If --binary or one of the variables points to a file that doesn’t exist, the command fails instead of launching something else.

With the installer

If you ticked Add Rinari CLI to PATH when installing, the rinari command it installed already sets RINARI_AGENT_BIN to your installation. rinari desktop . works with no extra setup.

With a CLI installed separately

If you run the CLI from source or installed it with uv tool install, point it at the app. In PowerShell, for an installation Only for me in the default folder:

$env:RINARI_AGENT_BIN = "$env:LOCALAPPDATA\Programs\Rinari Agent\rinari-agent.exe"
rinari desktop .

To keep the variable across terminals, set it as a user environment variable in Windows.

Back to the terminal

Resume the most recent compatible session of the current project, or a specific one:

rinari resume
rinari resume <session-id>

When resuming, the engine re-checks durable facts — project, branch, uncommitted changes, provider, trust, working directory — and reports what changed as warnings instead of correcting it silently.

Where the state lives

The engine keeps its state in ~/.rinari by default, or in the folder set by RINARI_HOME. Both clients read the same state. Don’t move or replace that folder to “reset” Rinari: doing so loses sessions and configuration. Export what you need first:

rinari export session
rinari export config     # secrets are never exported