Description:
Currently, running /model changes the model globally for all bots in a multi-bot server. Users who run multiple isolated agents (bots) want the ability to change the model for just one specific bot without affecting others.
Proposed Solution:
Extend the /model command to accept an optional agent/bot identifier:
/model <agentId> <provider/model> Example: /model bot1 anthropic/claude-opus-4-5
Or scoped to current context:
/model --agent bot1 /model bot1
Why this matters:
-
Multi-bot servers often need different models for different use cases (e.g., fast GPT-4o-mini for one bot, Opus for another)
-
Currently requires config edits + gateway restart to change per-agent models
-
Users want on-the-fly model switching per-bot without affecting others
Implementation hints:
-
Per-agent model preferences could be stored in agents//agent/session.json
-
Should persist across sessions (not just the current session)
-
Should not override the agent's default config permanently—just an override
Description:
Currently, running /model changes the model globally for all bots in a multi-bot server. Users who run multiple isolated agents (bots) want the ability to change the model for just one specific bot without affecting others.
Proposed Solution:
Extend the /model command to accept an optional agent/bot identifier:
/model <agentId> <provider/model> Example: /model bot1 anthropic/claude-opus-4-5Or scoped to current context:
/model --agent bot1 /model bot1Why this matters:
Multi-bot servers often need different models for different use cases (e.g., fast GPT-4o-mini for one bot, Opus for another)
Currently requires config edits + gateway restart to change per-agent models
Users want on-the-fly model switching per-bot without affecting others
Implementation hints:
Per-agent model preferences could be stored in agents//agent/session.json
Should persist across sessions (not just the current session)
Should not override the agent's default config permanently—just an override