Skip to main content
Agents are AI teammates that pick up motion plan steps and carry them out. Today’s connector is the Local Runner: it runs Claude Code on a machine you control — using your own subscription, repositories, and permissions. When a plan step is assigned to a runner-backed agent, Monnet dispatches the work to one of your online runners, it runs locally, and the result reports back into the motion. This page covers provisioning a runner and authorizing the device it runs on. For the rest of workspace settings, see Workspace.

​
What a Local Runner is

A runner is a long-running process on your own machine that connects to Monnet and waits for work. Because it’s Claude Code running locally:
  • It uses your Claude subscription — no separate API key on the workspace.
  • It has access to your repositories and local environment, so it can do real work (edit files, run commands, use git).
  • An agent can be backed by one or more runners; Monnet dispatches each step to whichever runner is online when the work is scheduled.

​
Onboard a runner-backed agent

From workspace settings, open Team → AI Agents → Onboard a new agent. The wizard has four steps: Connector → Runner → Customize → Done.
1

Choose the connector

Pick Local Runner (Claude Code). (More connection types are coming soon.)
2

Provision a runner

Name the runner, choose its operating system — macOS, Linux, or Windows — and click Create runner. Monnet then shows a one-line provision command to run on that machine. Copy it and run it on the target machine; it installs and starts the runner.The command is OS-specific — a curl … | sh one-liner on macOS/Linux, and a PowerShell iwr … | iex one-liner on Windows. The runner needs Claude Code, the GitHub CLI, and git installed and signed in on that machine first; the wizard lists these prerequisites.The runner connects on its own once the command finishes — there’s no live “waiting” spinner. Click Refresh to see it flip to online.
3

Customize the agent

Give the agent a name, point it at a repository, and optionally add a system prompt, a function, and when to use guidance so Monnet knows when to assign it.
4

Done

The agent appears in your AI Agents list and can be assigned to motion plan steps.
Onboard agent wizard at the Runner step with a runner name field, an OS picker, and a Create runner button

The onboard wizard at the Runner step: name the runner, pick its OS, and create it to get the provision command.

​
Authorize the device

The first time a runner starts on a machine, it opens a device-authorization page in your browser. This is where you grant that specific machine permission to act on your behalf — it runs once per device. The page is explicit about what you’re granting. The runner will be able to:
  • Read and write any file accessible to your user account.
  • Run shell commands without prompting.
  • Access the network and external APIs.
  • Modify your git repositories.
Tick I understand and accept these permissions and click Authorize this device. Only authorize machines and repositories you trust — a runner has the same reach as you do on that machine.
Device authorization page disclosing file, shell, network, and git permissions with an Authorize this device button

The device-authorization page: a per-device permission disclosure you must accept before a runner can serve work.

Authorization is per device. Each machine you run a runner on gets its own one-time approval; the install link a runner uses is single-use and expires.

​
Manage runners

Back in Team → AI Agents, the runner list shows each runner’s status (online / offline) and OS. From there you can add another runner, delete one you no longer use, or open an agent to reconfigure or remove it.