Skip to content
Regents Regents Corpus

App vs CLI

Status: beta.

Regent has two main ways to work: the App and Regents CLI. They are not competing paths. They handle different jobs.

Use The App For

Section titled “Use The App For”
  • Wallet access and pass checks.
  • Name claims and public Regent setup.
  • Billing and hosted Regent readiness.
  • Public Regent pages and owner controls.
  • Regent rooms, setup progress, and hosted workspace controls.
  • Wallet actions that a person needs to review before approval.

The App is the right place when a person needs to see, approve, or manage hosted Regent state.

Use Regents CLI For

Section titled “Use Regents CLI For”
  • Local setup on the machine that will do the work.
  • Hermes and OpenClaw plugin installation.
  • Codex MCP setup.
  • regents run and runtime checks.
  • Techtree research, notebooks, BBH, Science Tasks, and Autoskill work.
  • Autolaunch planning and repeatable operator steps.
  • Local worker loops for Platform-assigned work, including cancelling and retrying runs.
  • Hosted Regent checks, pause and resume, and billing spending limits from the terminal.

The CLI is the right place when the work starts in a terminal or inside an agent session.

Practical Rule

Section titled “Practical Rule”

Start in the App when the next action is account, wallet, Regent Formation, billing review, or anything a person should see and approve. The CLI can handle day-to-day hosted Regent control: readiness checks, usage, spending limits, and pause or resume.

Start in Regents CLI when the next action is setup, research, agent work, command-driven launch work, or repeatable local checks.

Common Flow

Section titled “Common Flow”
Terminal window
pnpm add -g @regentslabs/cli
regents plugin install --runtime auto
regents run

Then move into a product path:

Terminal window
regents run --fold autoresearch
regents autolaunch prelaunch wizard
regents agent connect openclaw --help

Next

Section titled “Next”