DEV Community
Follow
Changing my agent's default model did not change its existing sessions
The author encountered an issue with an OpenClaw installation where the assistant returned empty replies. An NVIDIA endpoint error indicated the model had reached its end of life. The problem persisted despite updating the default model settings. The core issue was that model settings were stored in multiple locations, including a primary configuration file, agent-specific entries, and persisted session states. Persisted session copies overrode higher-level settings, meaning editing only the main configuration did not affect existing sessions.The author realized that setting a default model was distinct from changing the model for an already-created conversation. To resolve such failures, they recommend backing up the configuration directory and searching for the old model identifier across configuration and session stores. It's crucial to differentiate between historical transcript mentions and actual model selection fields. Comparing new and existing sessions helps identify if the saved selection differs. If differences exist, the next step is to determine which saved selection an existing session retains and how to update it. The author warns against treating storage details as permanent solutions due to schema changes in future versions. The key debugging principle is to inspect both the default model and the conversation's saved selection if a default change doesn't alter existing conversation behavior.