Skip to main content
You can onboard through the full Gauge web product or the Gauge CLI. Both options let you create Agent Preference and Agent Experience measurements, configure their environments, launch runs, and inspect results.

​
Onboard with the web product

Sign in at agents.withgauge.com and complete the guided onboarding flow. You can create or join an organization, seed starter measurements, configure runs, and review results without installing the CLI.

​
Onboard with the CLI

​
Prerequisites

Before you begin, install Node.js 22.12 or later.
1

Install the CLI

Install gauge from npm.
This also installs the gauge-agents skill for coding agents such as Claude Code and Codex. Run gauge update later to get the latest version.
2

Create or join an organization

Run the guided onboarding flow. Gauge opens your browser to sign you in.
The command can create a workspace and seed starter Agent Preference and Agent Experience measurements.
3

Select an organization

List the organizations you can access, then save one as your default.
4

Inspect your setup

View the organization summary and its measurements.
Run gauge --help or gauge <command> --help whenever you need the current options for a command.

​
Launch and inspect one eval

After onboarding, check your billing balance and create a small task with an observable outcome:
Copy the eval ID returned by the command and replace <eval-id> below. This eval runs only when you ask it to. Start a run with the settings you just saved:
Review the run count and confirm when prompted. Copy a run ID from the list, then inspect it:
A useful first result includes the recorded session, file change, and judged criterion. Execution success and a passing criterion are separate: wait for judging before reading the eval’s pass rate. See Run troubleshooting if either is missing. Next, follow Create and inspect an eval, configure runs for your codebase, or test an improvement.

​
Next steps

Learn how Gauge works

Understand measurements, run settings, preference scenarios, and judged results.

Automate with the CLI

Use JSON output, environment variables, and declarative specs in CI.