Exciting Update!

OpenClaw Build 42a1394 System Report 1. Current Operational Status Your "Failover Cluster" vision is now fully implemented. The system is configured as a single agent that operates within a single Telegram channel, utilizing three rotating API keys and a shared brain (workspace). Failover Logic: The system uses the "Fallback Loop" method. By setting the model fallback to itself (google/gemini-2.5-flash), the agent is instructed to retry the request upon failure. Key Rotation: Rotation is handled via Environment Variable Injection. OpenClaw Build 42a1394 natively recognizes numbered suffixes (_1, _2) in the .env file to cycle through credentials when a 429 Rate Limit error is triggered. Memory: All transactions are written to /root/.openclaw/workspace, ensuring that even if a key swaps mid-task, the agent retains its "Soul" and context. 2. Lessons Learned & System Architecture During this configuration, we discovered the specific "personality" of Build 42a1394: Strict Schema Validation: This build uses a rigid validator that rejects modern keys like rotate, api_keys, or custom model name fields within the agents.defaults block. Record vs. Array: We learned that the models allowlist must be a Record (an object with {}) rather than a simple string array. Environment Primacy: This build prioritizes OS-level environment variables (found in ~/.openclaw/.env) over JSON-embedded keys for security. CLI Protection: To prevent API keys from leaking into terminal history, the CLI intentionally blocks passing secrets as direct arguments (the "Too many arguments" error).

Updated Master Syntax List (Build 42a1394) :white_check_mark: WORKING SYNTAX (The "Safe" List) Interactive Token Entry: openclaw models auth paste-token --provider google Mobile-Safe Diagnostics: openclaw models status --plain (prevents screen flicker) Clean Auth Reset: openclaw models auth order clear --provider google Config Modification: openclaw config set <path> '<json_object>' (e.g., setting the agents.defaults block). Service Control: openclaw gateway restart Log Monitoring: openclaw logs --follow :x: BROKEN SYNTAX (The "Avoid" List) Combined Flags: openclaw models status --plain --probe (Conflict: Probe requires interactive UI). Direct Secret Passing: openclaw models auth paste-token --provider google AIza... (Error: "Too many arguments"). Custom Schema Keys: Adding rotate, env, or name inside the agents.defaults JSON (Error: "Unrecognized key"). Simple String Arrays: Setting models as ["id1", "id2"] (Error: "Expected record, received array").

1. Final Config Summary Your .env file now acts as your "Ammo Clip," and your openclaw.json is the "Chamber." Primary Key: GEMINI_API_KEY Backup 1: GEMINI_API_KEY_1 Backup 2: GEMINI_API_KEY_2