Anthropic contacted despite model override

[dcdpr]

JP version

jp v0.1.0-43d34410 (2026-08-08)

What happened?

api.anthropic.com is down, and returning:

Stream error

 error  api error: overloaded_error: Overloaded: api error: overloaded_error: Overloaded
  kind  Transient

One would expect -m non-anthropic-favorite to not error out, but it does.
Changing the model in toml files - to prevent requiring -m at all - solves it.

[dcdpr]

BTW, that error message is not as kind to the user as it could be.

[JeanMertz]

BTW, that error message is not as kind to the user as it could be.

Agreed. Error messages haven't had much love yet, but they need polish before 1.0

One would expect -m non-anthropic-favorite to not error out, but it does.

--model/-m only affects the main model, not the inquiry/title-generate model, that was a deliberate decision, sometimes you want to quickly switch your conversation to use e.g. GPT instead of Opus for some specific task, but you don't suddenly want your Haiku title model to also use the more expensive GPT model.

Having said that, I suspect at some point we'll want to move towards some kind of high/medium/low built-in tiers, so that you can e.g. do --model-high=sol --model-low=luna or something to set the relevant model levels.

So, if you wanted to change all models from the CLI, you could do one of two things:

1. If you want to change what the aliases point to in the current conversation, you can do:

   $ jp q --cfg=providers.llm.aliases.opus=sol \
          --cfg=providers.llm.aliases.sonnet=terra \
          --cfg=providers.llm.aliases.haiku=luna \
          <query here>

2. If you do not want to change the aliases, you can directly reroute the model choices:

   jp q --model=sol \
        --cfg=conversation.title.generate.model.id=luna \
        --cfg=conversation.inquiry.assistant.model.id=terra \
        <query here>

of course, --model=T is also just an alias for --cfg=assistant.model.id=T.