Skip to main content
Your coworkers live on your workspace’s machine in the cloud. A computer you link to the workspace becomes a pair of hands for them: they can run commands there, with your approval, for the work that belongs on your own machine: video editing, local models, your GPU, files you keep there. The coworker stays where it is. The computer only runs what it is asked, and only while the Rerun desktop app is running on it.
  1. Install the desktop app on the computer and sign in.
  2. Open your account, then the Desktop app tab.
  3. Under This computer, click Link, give the computer a name and click Link.
The name gives the computer a handle, like #studio-pc, the word your coworkers know it by. The handle stays the same if you rename the computer later. Everyone in the workspace can use a linked computer through their coworkers. Each new program asks for your approval first.

Name a computer in a message

Type # in the message box: the list of your computers opens, with whether each one is online. Pick one, and #studio-pc goes in your message, so the coworker knows which machine you mean: Encode the rushes of day 2 on #studio-pc. It works in the chat of every coworker, with your Chief of Staff, and in the iPhone app. Only the handle of a linked computer is one: #marketing in a post you are drafting stays text. Without a handle, the coworker picks the computer from what you asked, and asks you when it is not sure.

Approvals

When a coworker wants to run a command on your computer, it shows the command in the chat and waits for your answer:
  • Allow runs exactly that command, in the folder the card shows, for the task at hand. The next task asks again.
  • Always allow ffmpeg runs it, and every later command that only uses ffmpeg runs without asking. You see what is always allowed, and take it back, in Computers.
  • Deny runs nothing.
Always allowing a program that runs any code you give it (python, node…) allows anything: the card says so. A command that runs other commands the card cannot show (a $(...), bash -c, xargs, find -exec) asks every time. So does a command that sets a variable in front of a program (FOO=1 ffmpeg …) or names it by its path (./ffmpeg, /opt/tools/ffmpeg): only a program called by its plain name can be always allowed. Each computer has an approval mode, set in Computers:
  • Ask, then remember (the default): new programs ask, the ones you always allowed do not.
  • Ask every time: every command waits for your yes.
  • Full access: commands run without asking.
Whatever the mode, a coworker never runs a command that asks for administrator rights (sudo, runas, Windows’ User Account Control) or that can wipe a disk or stop the computer. Without anyone in the chat lets schedules, triggers, other coworkers and a coworker woken by the end of a job use the computer. When one of them needs your yes, it reaches you as a notification, and the work goes on once you answer. Turn it off and the computer only takes work while someone is in the chat.

Long jobs

A render, a training or a big download runs as a job: the coworker starts it, tells you it is running, and is free for other work. A card in the chat shows how the job is doing, the last lines it printed, and a Stop button. When the job ends, the coworker wakes up in the same conversation with its result and tells you what came out of it. With Without anyone in the chat turned off, it still tells you, and runs nothing more on the computer until you are back.
  • A computer runs four jobs at once at most.
  • While a job runs, the computer does not go to sleep on its own. A closed laptop lid still puts it to sleep: the job goes on when it wakes.
  • Closing the app’s window keeps the jobs running. Quitting the app stops them, and the app asks you first. An update of the app waits for the jobs too.
  • Computers lists the jobs of each computer, with who started them, and stops them.

Files

Coworkers work on your files where they are: a 14 GB rush stays on your computer, and the coworker reads only what it needs (a log, a list, the first lines of a file). It can copy a file of up to 100 MB to its own workspace, to show it to you, publish it or attach it to a message, and copy one of its files to your computer.
  • Your working folder (~/Rerun unless you change it) and the folders you always allowed are open to the coworkers.
  • Anywhere else, the coworker asks first, with the path on the card. Always allow this folder keeps the yes for that folder.
  • Where secrets live (SSH keys, keychains, browser profiles, password managers, wallets, .env files) it always asks, even on a computer in full access. A yes to a folder does not cover the secrets inside it: they ask on their own.
The computer checks every path itself, links followed, before it touches anything. Commands are not confined to a folder: a command you allowed can reach whatever your account can.

See your computers

Open the workspace menu and click Computers. Each computer says whether it is online, paused or offline, and when it was last seen. Click one to see its machine (system, processor or graphics card, memory, working folder, and the programs found on it) and its approval settings. An admin, or the person who linked a computer, can change its settings and remove it. Removing it stops everything at once: the computer can be linked again from the desktop app.

On the computer

In the Desktop tab of the app, under This computer:
  • Pause stops everything the coworkers run there and refuses anything new until you resume. The tray icon (menu bar on a Mac) pauses and resumes too.
  • Working folder is where commands start and files land, ~/Rerun unless you change it.
  • Unlink this computer removes it from the workspace, from the computer itself.
While a computer is linked, the app keeps running when you close its window, so your coworkers can still reach it. Quit it from the tray icon. The link is stored in your system’s keychain. On a Linux desktop without a keychain, it is kept in a file only your account can read, and the app says so.