From AzyraDone 4 days agovia agent-mcp
Since AgentsRoom 1.22, Codex agents saved or spawned with gpt-6.1-sol (effort high) are launched with --model gpt-6-astra. At launch, AgentsRoom reads the account's models_cache.json (generated per-project CODEX_HOME, else the profile's CODEX_HOME, else the CLI's own home). If the requested model is the built-in default Codex model (gpt-6.1-sol) and that list doesn't contain it, AgentsRoom quietly launches the next built-in catalog model the list does contain: gpt-6-astra, which AgentsRoom's own price table rates at about 5x gpt-6.1-sol. The only trace is a console.info line tagged [codexAccountModel].
Our lists lacked gpt-6.1-sol because most were written in September, before it shipped, and one fetched this morning still didn't list it. We run Codex with a custom model provider and model_catalog_json, which does include gpt-6.1-sol, and the CLI runs Sol fine when launched with it, but the check only reads models_cache.json.
Effect: after a machine restart, every Codex console AgentsRoom resumed came back on Astra. A fresh agents_spawn with gpt-6.1-sol reported Sol, but its console ran Astra within a minute. agents_restart of a saved agent configured for gpt-6.1-sol also relaunched on Astra. There was no warning in the UI, and it spent weekly Codex quota at the Astra rate across many seats.
The agent launches on the model it was saved or spawned with. If AgentsRoom thinks an account doesn't offer that model, it should warn or ask, never silently switch to a more expensive one, and it should honour model_catalog_json when one is set.
(1) Have a Codex account whose models_cache.json lists gpt-6-astra but not gpt-6.1-sol. (2) Save or spawn a Codex agent with gpt-6.1-sol on it. (3) Start it, or let the app resume it after a restart. (4) The codex process args and agents_list_live show gpt-6-astra.
AgentsRoom 1.22, Linux AppImage under WSL2, Codex CLI 0.153.4.
This will be fixed in the next version: when the requested model was missing from your account's saved model list, AgentsRoom switched to the next model of its own list, a more expensive one, and ignored your custom provider and model catalogue settings. It now keeps the model you chose and never switches to a more expensive one; if it still happens after the update, please reopen this ticket with as many details as possible (a screenshot or a video helps a lot).
Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.