Local-only tool · Independent guidance

OpenClaw configuration studio

OpenClaw configuration is schema-driven and can vary with installed plugins. This studio creates a conservative starter config, explains high-impact fields, detects common secret patterns, and can validate JSON locally. Always finish with the live CLI schema and `openclaw config validate` on the target installation.

Current snapshotBrowser-only toolUpdated 2026-08-24Official docs main snapshot · OpenClaw 2026.8.1

Local parser + builder

Configuration studio

Input never leaves this browser
Do not paste real keys or tokens.Common secret patterns are masked again before copy or download.
PREVIEW

Conservative starter

Bundled checks
{
  gateway: {
    mode: 'local',
    bind: 'loopback',
    auth: {
      mode: 'token',
      token: '${OPENCLAW_GATEWAY_TOKEN}',
    },
  },
  agents: {
    defaults: {
      model: {
        primary: 'openai/gpt-5.4',
      },
      sandbox: {
        mode: 'non-main',
        scope: 'agent',
      },
    },
  },
}
No blocking issue in bundled checks

This is not exact validation. Run `openclaw config validate --json` against the live installation.

01

Bundled guidance is not your live schema

Plugin-owned and newly released fields can differ from this reviewed snapshot. An unknown field is therefore reported as “needs live validation,” not deleted. Use `openclaw config schema` or the Control UI schema for the exact installation, and back up the config before applying changes.

02

Safe CLI handoff

  1. 1

    Locate the active file

    Resolve the actual config path instead of assuming a home directory.

    openclaw config file
  2. 2

    Validate without mutation

    Check syntax, schema, and supported surfaces.

    openclaw config validate --json
  3. 3

    Inspect effective values

    Read the exact path before changing it.

    openclaw config get gateway.mode

Common questions

Before you act

Is pasted configuration uploaded?

No. Parsing, redaction, previews, and downloads happen in the browser. The site has no endpoint for tool input.

Can it validate every plugin field?

No bundled snapshot can. Use the live schema from your installation for exact validation.

Primary sources

Verify against the owner.

Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.