Feature · Getting started
Device sign-in
The runner is a small program on your own computer. It starts your own Claude Code or Codex, under your own sign-in, for work that you asked for.
How it works
What it does
The runner starts the official claude or codex CLI that is already installed and signed in on your computer. It runs only work that you own, in your organization. No one else's work runs on it, and the platform never bills it.
Before you install
An owner or admin must allow runners for the organization and accept the vendor terms. See Subscriptions and vendor terms.
Install
Run the install command from setup or from Runners. It needs Node.js 22 or newer, on macOS or Linux. On Windows, use WSL. The installer:
- downloads the runner from your Agent server and checks it;
- puts it in
~/.agent-runnerand tells you how to add it to your PATH. It never edits your shell profile; - offers to install and sign in to Claude Code and Codex, on the vendors' own pages;
- signs the runner in to Agent. A browser page opens; check the code and select Approve. Approve a runner only when you just started it yourself;
- on macOS, starts the runner now and at every login. On Linux, run the
startcommand it prints.
Run the install command again to update.
Commands
agent-runner login: sign the runner in with a code in your browser.agent-runner start: start taking work.agent-runner doctor: show each CLI, its sign-in state and its sandbox.agent-runner repo connectandrepo list: see Local repositories.agent-runner atlas scan: profile repositories for the Repository Atlas.agent-runner audit: a local look at where your own agent time and tokens go. It sends nothing.
Statuses
Online, Offline, and Approved, not started. A runner can show Takes platform work or Your own tasks only.
Stop a runner
Select Revoke on Runners. Its token stops working at once, and a task it runs is asked to stop.
Limits
Each person can have 5 runners and 50 queued tasks. One runner per computer.
From the help article The local runner, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
MemberNo API tokensrunner/deviceLookupRunner: device lookup.
Types:
RunnerDeviceLookupRequestreturnsRunnerDeviceDto
MemberNo API tokensrunner/deviceApproveRunner: device approve.
Types:
RunnerDeviceApproveRequestreturnsRunnerDeviceApproveResult
ViewergetLocalRunnerSettingsGets local runner settings.
Types:
EmptyRequestreturnsLocalRunnerSettingsDto
AdminNo API tokensupdateLocalRunnerSettingsUpdates local runner settings.
Types:
UpdateLocalRunnerSettingsRequestreturnsLocalRunnerSettingsDto
ViewerlistMembersLists members.
Types:
EmptyRequestreturnsListMembersResponse
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Local runner created
- Local runner delegates changed
- Local runner device approved
- Local runner device denied
- Local runner device token issued
- Local runner registered
- Local runner revoked
- Local runner task ended
- Local runner task queued
- Policy changed