Difference between current and active model in Telegram group
✅Solved
When I run /model in my telegram group I get this reponse.
Current: kimi-coding/k2p5 (selected)
Active: bailian/glm-4.7 (runtime)
Tap below to browse models, or use:
/model <provider/model> to switch
/model status for details
Why does it show a current and active model? Which one is actually being used?
Current: kimi-coding/k2p5 (selected)
Active: bailian/glm-4.7 (runtime)
Tap below to browse models, or use:
/model <provider/model> to switch
/model status for details
Why does it show a current and active model? Which one is actually being used?
Solution
/model- Current: … (selected) = what the session is configured/overridden to try next (your “intended” model).
- Active: … (runtime) = what the gateway actually ended up running for this session (what produced the last real reply), after things like failover/fallbacks.
So the model actually being used right now is the one on the
Active: … (runtime)Why can they differ?
1) You just switched models: the selection is stored immediately, but “active/runtime” only updates after the next normal message is processed with that model.
2) Failover/fallback happened: the selected model failed (auth/rate limit/timeout/tool incompat), so OpenClaw fell back to another model and that became “active”.
What to do to verify:
- Send a normal message after switching, then run
/model- If it keeps staying different, run
/model statusDocs:
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
