Runi Help
Email us Start trial

Runi help centre

Find the answer,
then get back to it.

Thirty pages on setting Runi up, every agent it speaks to, exactly what it can see, and why a workspace has gone quiet. All of it written from the code that runs on your machine.

Popular: Nothing is appearing in RuniClaude CodeCodexWhat Runi seesTrial, seats and billing

Which agent are you running?

All seven, including anything with no adapter
Claude Code Codex Cursor OpenCode Gemini CLI OpenClaw

Something is wrong

Start from what you are seeing

The app is empty. Nothing I do shows up. My agent starts and knows nothing about the team. I connected an agent and no sessions appear. It works on my laptop but not my desktop. Windows or macOS refuses to open the installer. I need to know exactly what my team can see.

One command, run in the repository you expected work to appear in. It reads every signal on the machine and prints a line per subsystem. Every line it can print.

Setting it up for the first time

The whole section
  1. Install Runi Download it, run it, sign in, and land in a workspace with your repositories in it.
  2. Connect your first agent One click per agent, how to prove it worked, and what Runi added to your machine.
  3. Choose the repositories Runi watches Runi publishes nothing outside the repositories your workspace tracks. Here is how tracking is decided and how to add one.
  4. What Runi does, in one page The whole product in one read: what gets observed, what crosses to your team, and what arrives in the next session.
  5. What to expect in the first hour The order things appear in, what a healthy first day looks like, and the two moments where new teams think it is broken.

Everything, by subject

Start here What Runi is doing on your machine, how to install it, and how to get the first brief to land. 5 articles Connect your agent One page per agent: what Runi installs, how the briefing reaches that agent, and the limits worth knowing before you rely on it. 7 articles Using Runi The brief, task cards, memory, shared work and the tools your agent can call. What each one is for, and how to make it better. 6 articles Privacy and control Exactly what leaves your machine, the two switches that decide it, and how to remove anything you have shared. 4 articles Team and billing Invitations, roles, seats, the trial clock, and what happens when it runs out. 2 articles Troubleshooting Symptom, cause, fix. Start with the doctor: one command that reads every signal on the machine and tells you which part has gone quiet. 5 articles

Most read this month

Nothing is appearing in Runi The seven reasons a workspace stays empty, in the order worth checking, each with the line that proves it. Connect your first agent One click per agent, how to prove it worked, and what Runi added to your machine. My sessions start without a brief Emission, ingestion and relevance are three different failures with three different fixes. What Runi sees, and what it never sees The boundary, stated plainly: no repository scan, no git history, no file your agent did not edit. The brief: what is in it and why How the packet is chosen under a token budget, what the receipt tells you afterwards, and how to make briefs land better. The two sharing switches What I ask, and what my agent changed. What each switch turns off, and what it turns off downstream.

Or ask a person.

Two founders read this address and there is no queue in front of them. Send what you tried and what happened. Paste the output of runi doctor and you will usually get an answer in one reply instead of three.

founders@tryruni.com Product FAQ