Parse a cron expression (5 or 6 fields) and compute next runs in a time zone with DST, plus an Arabic and English description
openclaw.json Generator & Validator
Generate an openclaw.json from a form (workspace, model, channels, cron) or paste your file to validate it against the official OpenClaw schema: path-based errors, unknown keys the gateway refuses, and warnings for literal secrets.
Workspace
How the result is calculated
The official openclaw.schema.json (JSON Schema draft-07) is loaded on the first validation; it is the output of openclaw config schema for version 2026.10.4 with titles and descriptions stripped to cut the size. A local validation engine supports type, properties, additionalProperties, required, enum/const, pattern, anyOf/oneOf/allOf, $ref and numeric and length bounds, and errors show the key path. Because OpenClaw refuses to start with an unknown key, every unknown key is highlighted. Note: the schema printed by openclaw config schema is output-shaped (every key with a default value is listed in required), so here every key with a default is treated as optional, otherwise even the minimal example in the docs would fail. The form produces JSON with schema keys only (secrets are written as ${ENV} references).
Limits:
The schema is from OpenClaw 2026.10.4; your version may differ, so it may accept a newer key or reject an old one (check
openclaw config schema on your machine). Field descriptions are not shown (stripped for size; see the OpenClaw docs). Semantic validation (does the model exist? is the token valid?) is outside the schema. The output is strict JSON although OpenClaw accepts JSON5. The form covers the most common options only; edit the JSON directly for the rest. The tool sends your file nowhere.FAQ
Why does the gateway refuse to start?
OpenClaw accepts only a file that fully matches the schema; an unknown key stops the gateway. Run openclaw doctor --fix.
Should I put secret tokens in the file?
Prefer ${ENV} references or a SecretRef rather than literal values.
