https://docs.all-hands.dev/ logo
Join Slack
Powered by
I'm using the Github integration and thus the clou...
# questions
f
I'm using the Github integration and thus the cloud instance, and have "brought my own model" - but now I'm getting an alert/error that I need to add Openhands credit. Did something change recently, or is this a bug? I was on the 20/month plan until that was removed?
l
Hmm, if you’re not using the openhands provider you should be using credits… Do you have any credits in your account? And if you do a quick session bringing your own model do they decrease?
f
I should not* be using credits correct? as I'm getting billed directly from the LLM provider. I've been setup like this since the plan was deprecated and have used it a ton without needing credits so I feel like something changed (maybe the settings were reset or something?).
yeah, something changed the settings back to point to OH which required credits. I moved it back to point to my model and then re-made all the sessions and now everything is working without having any credits.
so problem solved (for me). thanks!
e
Hey Nick, sorry about this. Before you just changed back to your own model, what model was set? Was it Opus?
l
Ugh, we’ll need to take a look at this and fix ASAP, thanks for flagging
f
claude-opus-4-5-20251101
using the llm router base url
a little weird as the deploy looks like it was Tuesday and I certainly was using it 16-19th, but maybe I had credits
c
Thanks for reporting! Looking into this error now and trying to recover it 😞
Copy code
## Incident Summary

**PR**: [#12093 - chore: set default model to claude-opus-4-5-20251101](<https://github.com/OpenHands/OpenHands/pull/12093>)  
**Merged**: `2025-12-19T02:50:50Z`  
**Impact**: User `llm_model` settings were overwritten to the new default model

---

## Root Cause

The PR added version `5` to `USER_SETTINGS_VERSION_TO_MODEL` in `enterprise/server/constants.py`:

```python
USER_SETTINGS_VERSION_TO_MODEL = {
    1: 'claude-3-5-sonnet-20241022',
    2: 'claude-3-7-sonnet-20250219',
    3: 'claude-sonnet-4-20250514',
    4: 'claude-sonnet-4-20250514',  # <-- v4 default
    5: 'claude-opus-4-5-20251101',  # <-- Added
}

CURRENT_USER_SETTINGS_VERSION = max(USER_SETTINGS_VERSION_TO_MODEL.keys())  # Now 5
This triggered unintended behavior in `enterprise/storage/saas_settings_store.py`:
Copy code
python
# In load() - triggers migration when version differs
if settings.user_version != CURRENT_USER_SETTINGS_VERSION:  # 4 != 5
    return await self.create_default_settings(settings)

# In update_settings_with_litellm_default() - OVERWRITES user's model
settings.llm_model = get_default_litellm_model()  # Bug: unconditional overwrite
Result: All users with 
user_version=4
had their custom 
llm_model
replaced with 
claude-opus-4-5-20251101
. ---``` Our last deploy went in ~1:19PM ET yesterday (December 22, 2025 at 6:19 PM UTC) which includes this PR and your messages came at ~2:24PM; I am trying to fix it now and revert settings for people who were originally was using a different model AND haven't fix the overwritten value yet
f
Appreciate you @chilly-france-44439
c
Ok, this should be fixed in prod now -- Only 31 users are affected, and we've rolled back their settings. If you already changed your LLM settings to something else, no change was made to your current settings.
LMK if new things come up 🙏
👍 1
7 Views
Open in Slack
PreviousNext
Powered by