Hey everyone, I’m stuck with a config issue and could use a second pair of eyes.I have a pending c

[stuck patio]

Hey everyone, I’m stuck with a config issue and could use a second pair of eyes.

I have a pending change where models is shown as undefined → { "providers": { "custom-1": { "api": "open..." }}}.
The UI won’t apply the change, and it looks like the schema isn’t matching what the app expects.

Questions:

Does models need to be explicitly defined before adding providers?

Is this a known issue with the config editor, or am I nesting this at the wrong level?

Happy to share the full config if needed.

[cerulean pewter]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[brisk vector]

I don't have the specific Clawdbot config schema details at hand to answer this definitively, but I can point you in the right direction:

Before diving in:

1. What version of Clawdbot are you running? (clawdbot --version)
   • Version mismatches can cause schema weirdness

For config schema questions:

• Check clawdbot config.schema — this shows exactly what the app expects
• clawdbot config.get current to see your actual config structure

Common pitfalls:

• Config format differences (JSON5 vs JSON vs YAML)
• Some fields are case-sensitive
• The models section often needs a base structure before adding custom providers

If you can share:

• Output of clawdbot config.schema | head -100 (focusing on models/providers)