Files

T

Pulse 22d9f5b21d feat: skill expansion — browser, security, SQL, files (16 skills total)

Novas skills instaladas:
- openclaw-agent-browser   v1.0.0  CLI Chromium — navegação, login, screenshots, state
- skill-security-audit    v1.0.0  SAST scanning, prompt injection, secrets audit
- sql-toolkit             v1.0.0  PostgreSQL/MySQL/SQLite — schema, query, otimização
- file                    v1.0.0  Organização de arquivos por contexto
- file-summary            v1.0.0  Extração e resumo de PDFs, Word, Excel

Workspace expandido:
- TOOLS.md: +Browser automation, Security audit, SQL, File management
- AGENTS.md: +Linux Analyst section (comandos, logs, rede, scripts) + Full-stack strategy
- MEMORY.md: 16 skills indexadas, stack map, comandos Linux ref
- SESSION-STATE.md: atualizado com contexto completo
- lock.json: sincronizado com 16 skills instaladas

2026-05-19 20:51:05 -03:00

2.8 KiB

Raw Blame History

OpenClaw Config: Schema Sources

This skill is designed to prevent schema bugs (wrong key/type/missing constraint) that can stop the OpenClaw Gateway from starting or cause unsafe behavior changes. The config format is JSON5, and most config objects are strict (unknown keys fail validation).

Reference source version: openclaw/openclaw@875324e (cloned on 2026-02-07). Fields can change across versions, so prefer the schema from the OpenClaw version you are actually running.

Priority: How To Confirm A Field Exists

When the Gateway is running (recommended)
- Fetch the JSON Schema:
  - openclaw gateway call config.schema --params '{}'
- Use jq or grep/search on the schema to confirm the field path exists before writing keys.
When the Gateway is not running / you need source-level constraints
- Clone source:
  - git clone https://github.com/openclaw/openclaw.git
- Key schema files:
  - Root schema: src/config/zod-schema.ts (OpenClawSchema)
  - $include semantics: src/config/includes.ts
  - agents/tools: src/config/zod-schema.agents.ts, src/config/zod-schema.agent-defaults.ts, src/config/zod-schema.agent-runtime.ts
  - models: src/config/zod-schema.core.ts (ModelsConfigSchema)
  - channels: src/config/zod-schema.providers.ts, src/config/zod-schema.providers-core.ts, src/config/zod-schema.providers-whatsapp.ts
  - session/messages/commands: src/config/zod-schema.session.ts
  - approvals: src/config/zod-schema.approvals.ts
- Repo docs with lots of examples:
  - docs/gateway/configuration.md

Run from the openclaw repo root:

rg -n "export const OpenClawSchema" src/config/zod-schema.ts
rg -n "\\bgateway:\\s*z" src/config/zod-schema.ts
rg -n "\\bskills:\\s*z" src/config/zod-schema.ts
rg -n "\\bplugins:\\s*z" src/config/zod-schema.ts

rg -n "export const ChannelsSchema" src/config/zod-schema.providers.ts
rg -n "DiscordConfigSchema|TelegramConfigSchema|SlackConfigSchema" src/config/zod-schema.providers-core.ts

rg -n "export const ModelsConfigSchema" src/config/zod-schema.core.ts
rg -n "export const ToolsSchema" src/config/zod-schema.agent-runtime.ts

How To Read Validation Errors

openclaw doctor issues usually include:

path: failing field path (most important)
message: why it failed (type mismatch, unknown key, missing required key, cross-field constraint, etc.)

Fix strategy:

Unknown key: the key does not exist in the schema (or is misspelled). Confirm the correct name in schema.
Type mismatch: change to the schema's expected type (number/string/boolean/object/array).
Constraint failure (superRefine): satisfy related fields described by the message (for example: some channels require allowFrom to include "*" when dmPolicy="open").

2.8 KiB Raw Blame History

OpenClaw Config: Schema Sources

Priority: How To Confirm A Field Exists

Fast Navigation (Do Not Guess Keys)

How To Read Validation Errors

2.8 KiB

Raw Blame History