titleConvo fails to load Custom Endpoint Config, causing timeout with OpenRouter #8139
Replies: 2 comments 1 reply
-
The Custom Endpoint Config loading does need to be fixed, but it fails anyway with gemma since it doesn't support structured output (which is what we use by default for titling). We will implement a "chat/completions" method, as well as giving more ability to customize here, soon. |
Beta Was this translation helpful? Give feedback.
-
I'm also facing the same issue. Is there a model that currently works for titling with OpenRouter? I tried a few, both with The titling works despite this error, though, but it defaults to using the same model used for the chat itself (which of course is not always optimal). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What happened?
When using a OpenRouter custom endpoint with titleConvo: true, the title generation process often fails with a "Title generation timeout" error. The root cause appears to be a failure to load the custom endpoint configuration, as indicated by the warning [api/server/controllers/agents/client.js #titleConvo] Error getting endpoint config in the logs.
Chats titles remain "New Chat"
Version Information
Steps to Reproduce
Config for test:
Start a new conversation with the model from OpenRouter
Observe the "Title generation timeout" error and the "Error getting endpoint config" warning in the logs.
What browsers are you seeing the problem on?
Chrome
Relevant log output
Screenshots
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions