SpudSuiteHelp Open SpudSuite

Agents

Personal runner

A personal runner is the SpudSuite Runner on your own computer, switched into personal mode. Factory threads and Agents workflows can then work on your files, but only inside folders you grant, in a sandbox your operating system enforces. They never get administrator rights unless you say yes, twice: once in SpudSuite or the runner app, and once at your computer's own prompt.

Turn it on

  1. Install the runner and pair it (see Install a runner).
  2. In the runner app, under Personal mode, tick Let Factory and Agents work on this computer. From a terminal: spud personal on.
  3. Grant the folders you want it to use, read only or read and write, for an hour, a day or until you remove them.

Factory projects live in SpudSuite Factory in your home folder, which is always read and write.

The runner won't start as an administrator (or root) at all. Run it as your normal user.

In the sandbox, Claude Code keeps its own settings and sign-in, apart from yours, so nothing a thread writes there runs when you use Claude Code yourself. It starts from your settings, and on Linux and Windows from your sign-in. On macOS, sign it in once from the runner app.

For a stronger wall, especially on macOS and Windows, run the runner in Docker instead.

Asking for more

When a Factory thread needs something outside its folders, it asks:

  • A folder: approve it for a time or until removed. The thread restarts in a sandbox that includes it and carries on.
  • One command outside the sandbox: runs as you, never as administrator.
  • One command as administrator: after you approve, Windows (UAC), macOS (your password) or Linux (polkit) asks too, so someone has to be at the computer.

Requests show on the runner's page in Agents β€Ί Runners, in the runner app, and as a notification from the tray icon. Only the person who added the runner can approve from SpudSuite; workspace admins can decline. In the runner app you can tick Only approve requests on this computer.

What the sandbox stops

Windows macOS Linux
Administrator rights Stopped Stopped Stopped
Writing outside granted folders Stopped Stopped Stopped
Reading outside granted folders Not stopped (the runner's own folder stays hidden) Stopped in your home folder Stopped in your home folder
Turning the network off Not available Available Available

On Linux it uses bubblewrap (install it with your package manager) or Landlock; on macOS, sandbox-exec; on Windows, a low-integrity restricted process in a job object. The runner's page shows which one your computer uses. Threads never get your ssh agent or secrets from your computer's environment, with or without personal mode.

Commands

spud personal on                                # turn it on
spud personal grant ~/Projects/site --write --minutes 120
spud personal status                            # the sandbox and your folders
spud personal revoke fg_…                       # remove a folder
spud personal audit                             # everything it did, and who approved what
spud personal off
spud tray                                       # the tray icon

The audit log

Every sandboxed start, every request and answer, every folder added, removed or expired, and every command run outside the sandbox or as administrator is kept on your computer and on the runner's page under Audit log.

Something unclear, or out of date? Spud wants to know: tell us from SpudSuite and we'll fix the page.