Skip to main content
Most users only need to run mulerun login once. The CLI stores the resulting OAuth token in ~/.mulerun/ and every other command reuses it. The variables and flags below are available for non-interactive use (CI, agents, sandbox environments) and for advanced overrides.

Environment variables

A project-local .env file is auto-loaded when present — variables already set in the process environment are not overwritten.

Global flags

These flags are accepted by every subcommand. They take precedence over both environment variables and the OAuth cache.

Authentication

The standard flow uses OAuth in your browser:
For automation, pre-mint a token and inject it via MULERUN_TOKEN. The token is a JWT — mulerun internal-auth token-info decodes it locally without making a network call.

Proxy support

The h suffix on socks5h makes DNS resolution happen on the proxy side. The proxy applies to HTTPS API calls and to the WebSocket channels used by session, computer chat, and computer shell.

Output formats

Pass -o (or --output) on any command:
For agent integration use -o json plus --no-color.

Inspect the active configuration

Prints the resolved API base URL, login status, distribution profile, and a few environment-sanity checks. Run this before opening a support ticket.

Resolution order

  1. CLI flags (--token, --base-url, …)
  2. Process environment variables (MULERUN_*)
  3. OAuth cache written by mulerun login
  4. Built-in defaults