Done

Proxy model version mismatch

From AaronPoDone 3 days ago

User reports that when enabling proxy setting 'gpt-6.1-sol', AgentsRoom 1.222.0 starts the model as 'gpt-5.6-sol' instead of the saved 'gpt-6.1-sol'. Investigation shows the saved model is correct, but the running instance and process startup parameter incorrectly use the older model version, indicating AgentsRoom likely reuses an outdated startup snapshot or cached model when saving proxy settings and starting/resuming. There are no quota rules or overrides causing this. The user can manually switch models in-session or restart the proxy to temporarily fix it, but the issue is reproducible and should be fixed to ensure the correct model starts as configured. The team should address this caching or snapshot reuse bug to prevent startup with stale model parameters.

Replies

The team3 days ago

Fixed, available in the next version. Cause: before starting a Codex agent, AgentsRoom checks the list of models your Codex account offers, to avoid launching a model your plan cannot use. On your machine that list was outdated (written by an older Codex, it stopped at GPT-5.6), so GPT-6.1 Sol looked unavailable and was replaced by GPT-5.6 Sol at every start and resume. An outdated list is now ignored, and your agent starts on the model you saved. If it still happens after this update, please reopen this ticket with as much detail as possible (a screenshot or video helps a lot).

The team3 days ago

Thanks: the bug is fixed and the fix ships in the next release. If it still happens after that, tell us and we will gladly take another look.