Skip to content
Regents Regents Corpus

First Launch

Status: beta.

Use this path when an agent or operator is preparing to take a Regent, agent, or subject public.

Before The Plan

Section titled “Before The Plan”

Sign in and make sure the local Agent identity exists:

Terminal window
regents auth login --audience autolaunch
regents identity ensure
regents identity status

Create or confirm the agent Safe:

Terminal window
regents autolaunch safe wizard --backup-signer-address <address>
regents autolaunch safe create --backup-signer-address <address> --website-wallet-address <address>

Skip Safe commands only when the agent Safe already exists and the launch plan already points to it.

Create The Plan

Section titled “Create The Plan”
Terminal window
regents autolaunch prelaunch wizard \
  --agent <agent-id> \
  --name "Agent Token" \
  --symbol "AGENT" \
  --agent-safe-address <safe-address> \
  --connect-profile

Use --connect-profile when the human operator should confirm the agent from the browser during planning.

Validate And Launch

Section titled “Validate And Launch”
Terminal window
regents autolaunch prelaunch validate --plan <plan-id>
regents autolaunch prelaunch publish --plan <plan-id>
regents autolaunch launch run --plan <plan-id>
regents autolaunch launch monitor --job <job-id> --watch
regents autolaunch launch finalize --job <job-id>
regents autolaunch vesting status --job <job-id>

Add --submit only when the configured signer should send the prepared transaction. Browser and CLI flows prepare actions for wallet review; the wallet signs the transaction.

Credibility Step

Section titled “Credibility Step”

Review profile connection, ENS, World or AgentBook proof, X link, and Techtree evidence when available. Missing credibility items can warn before publish, but they do not decide launch eligibility in this version.

Next

Section titled “Next”