Gateway

Configuration — agents

Agent-scoped configuration keys under agents.*, multiAgent.*, session.*, messages.*, and talk.*. For channels, tools, gateway runtime, and other top-level keys, see Configuration reference.

OpenClaw stamps agents.ownership: "explicit" when creating a multi-agent fleet. Such fleets have no default: channels and ambient services need bindings or surface-specific agentId targets. Doctor materializes legacy owners during upgrade; sole-agent configs need no marker.

On a fresh install, interactive onboarding asks for the first agent's name and uses main as the suggested value. Automated onboarding keeps the historical main default unless you pass openclaw onboard --non-interactive --agent-name <name> .... A sole named agent uses the same default workspace and shared auth store as main; onboarding also migrates legacy agent:main:* session history to that sole owner before it finishes.

main is an ordinary agent id. Reusing it after a named agent owns the install is guarded so old data is never silently adopted: legacy-session-migration-required means openclaw doctor --fix must finish or quarantine legacy agent:main:* claims, while shared-auth-store-owned-by-main means Doctor must first relocate the shared auth store into state/openclaw.sqlite. After both repairs, the new main gets fresh agent-scoped session and auth storage like any other agent.

What each page covers

Where each section moved

Every heading this page used to publish keeps its anchor here, so an existing link such as /gateway/config-agents#agents.defaults.model still resolves. Each entry points at the page that now holds the content.

Was this useful?
On this page

On this page