Description
Admin commands like /model, /loop, /policy update the runtime config in memory but don't write changes to config.yaml. This means:
- Changes are lost on restart
- WebUI shows stale values until page refresh (and even then shows old values since it reads from disk)
- No sync between Telegram admin commands and WebUI config
Steps to reproduce
- Set model via
/model deepseek/deepseek-r1 in Telegram
- Open WebUI → LLM tab → Model still shows the previous value
- Restart the agent → model reverts to whatever is in config.yaml
Expected behavior
Admin command changes should persist to config.yaml so they survive restarts and stay in sync with WebUI.
Possible approach
Use readRawConfig → setNestedValue → writeRawConfig pattern (already used in WebUI config routes and owner detection in index.ts).
Affected commands
Description
Admin commands like
/model,/loop,/policyupdate the runtime config in memory but don't write changes toconfig.yaml. This means:Steps to reproduce
/model deepseek/deepseek-r1in TelegramExpected behavior
Admin command changes should persist to
config.yamlso they survive restarts and stay in sync with WebUI.Possible approach
Use
readRawConfig→setNestedValue→writeRawConfigpattern (already used in WebUI config routes and owner detection inindex.ts).Affected commands
/model(admin.ts:handleModelCommand)/loop(admin.ts:handleLoopCommand)/policy(admin.ts:handlePolicyCommand)/reasoning(if feat: configurable reasoning effort for thinking models #13 is merged)