Runi is a desktop app for Windows and macOS. You make the account on the website, then install the app. Five minutes, most of which is the download.
Before you start#
- An account. Starting a team? Create one at tryruni.com/start: email, a password, and a six-digit code from the confirmation mail. The 14-day trial starts there and takes no card.
- Invited by a colleague? Use the link in the invitation instead. You are joining their workspace, so you do not need your own trial. See Invites and roles.
- At least one coding agent already installed and working. Runi watches agents; it does not ship one.
Install it#
-
Go to tryruni.com/download#
It picks the build for the machine you are on and tells you the version and size before you commit. Signing up sends you here too, so you may already have it open.
-
Run it#
Windows
Double-click the installer. It installs for you alone, needs no admin rights, and opens Runi when it finishes.
Windows will probably warn you about an unknown publisher first time. That is our signing certificate, not your machine, and the fix is here.
macOS
Open the disk image and drag Runi to Applications. Launch it from Applications, not from the mounted image.
macOS may refuse the first launch for the same reason. Control-click → Open gets past it.
The download page offers Apple silicon and Intel side by side, because a browser cannot reliably tell which Mac you are on. Apple menu → About This Mac, and read the Chip line.
-
Sign in#
Use the address and password from the website. This signs the app in. Runi signs your machine in separately when you connect an agent, so publishing from a machine can never sign you out of the app.
-
Create a workspace, or accept an invitation#
The workspace is the team boundary. Records are readable inside it and nowhere else. If you started the trial you create the workspace here and the trial comes with you. If you were invited, you join theirs.
-
Add the repositories you want watched#
Runi publishes nothing from a folder your workspace does not track. People skip this, and it is the most common reason a new install looks dead. See Choose the repositories Runi watches.
-
Connect an agent#
Settings → Agents, then Connect beside the agent you use. One click each. See Connect your first agent.
Updates#
Runi updates itself. It checks for a new release, downloads it in the background, and applies it when you next restart the app. You never need to come back to the download page.
Note
Restart your agent sessions after an update, not just the app. Hooks
pick up a new version straight away. The MCP server does not: an agent
session that was open across the update keeps running the old one.
runi doctor names any session that needs restarting.
If you need a different build#
The download page has an Other builds section for two cases. An offline installer, if the machine has restricted network access or you need to choose the install folder. A portable build, if you want a look without installing anything.
Careful
The portable build cannot connect your agents. It unpacks itself to a temporary folder that disappears when you quit, so any agent Runi registered would end up pointing at a file that is not there. Runi refuses to register from it rather than leave you a setup that silently stops working. Use it to look around, then install properly.
Uninstalling#
Disconnect your agents in Settings → Agents first, so Runi removes what it added to each agent's config. Then uninstall the app the way you uninstall anything else. Skipping the first step leaves each agent complaining about a missing server on every launch.
Uninstalling does not remove what you have already shared with your team. For that, see Deleting your data.