---
title: RunPane authentication
description: How agents access the public RunPane website API and a user's local Pane daemon.
canonical: https://runpane.com/auth.md
last-updated: 2026-11-15
---

# RunPane authentication

RunPane's documented public website API is read-only and needs no account, API key, OAuth token, or other credential. Local Pane actions stay on your machine. They use the installed `runpane` CLI and the Pane daemon that you control.

## Discover

1. Read the [OpenAPI document](https://runpane.com/openapi.json) for public website endpoints.
2. Read the [local CLI contract](https://runpane.com/runpane-cli-contract.json) for commands that work with repos, panes, and terminals.
3. Run `runpane doctor --json` before a local action. It tells you whether Pane is installed and whether the daemon is reachable.

## Pick a method

Use the public API without credentials for product questions and public docs. Use the local CLI for workspace actions. Phones pair with a computer by scanning a QR code; see [Pair your phone](https://runpane.com/docs/phone). With Tailscale, desktop clients on your Tailscale login can connect without a code. The host checks visibility and an optional password on port 8443. Headless hosts, browsers and other accounts can use a code from the remote daemon on port 443.

## Register

There is no hosted `agent_auth` registration flow. RunPane doesn't publish a `register_uri` because the website doesn't issue agent credentials. Install Pane on the machine that owns the repos, then use `runpane doctor --json` to find the local daemon.

## Claim

RunPane doesn't ask an agent for an `identity_assertion` or an ID-JAG token. The website has nothing to claim. A Remote Pane QR code or connection code is created by the user's computer and must be handled like a password. A QR code holds a random 256-bit secret, works once and expires after 10 minutes.

## Use the credential

Public API calls send no authorization header. Local CLI calls use the current OS user and the daemon endpoint found by Pane. A QR-paired device trades the one-time secret for its own per-device token; the computer keeps only a hash. The Pane apps pin each computer's key. Codeless Tailscale clients use Tailscale identity and the host password when enabled. Code-based remote clients use the paired connection created during Remote Pane setup. See [Remote security](https://runpane.com/docs/remote-security).

## Errors

Public endpoints can return 400 for a bad query, 404 for a missing route, or 429 when a caller exceeds the published limit. They don't return `WWW-Authenticate` because they don't require bearer credentials. A local CLI connection error means you should run `runpane doctor --json` and follow its next step.

## Revocation

There is no website token to revoke. To remove local access, stop or uninstall Pane. For a paired phone, open Settings → Remote Access → Phones and glasses and choose Remove: Remove from this computer, or Remove from all your computers. Removing a phone also undoes the links it made. For a linked computer, choose Unlink. For codeless Tailscale access, change Who can connect or the password at the host under Settings → Remote Access → Tailscale. For code-based access, revoke the paired client under Connection codes.
