Remove/Update stale provider "glhf"#756
Conversation
typo?
|
I think it's better to just remove GLHF as a whole. Seems like the website is never up. |
It's because they rebranded to synthetic.new Initially, they did have the glhf.chat domain redirecting to synthetic.new, but now that's gone too. It may be worthy to note that OpenClaw also supports Synthetic as a provider. 
Also, any glhf.chat accounts that received the $10.00 promotional credit (it was maybe a year ago) still have the credit when logging in to synthetic.new Perhaps we could turn glhf.js into synthetic.js, or just drop support for it entirely. |
Up to you. Either approve and merge the current changes or add support for synthetic. We could also do a separate PR for that. |
I only made this pull request because I noticed that the letter/s were mixed up, but if you guys wish to take over this pull request to completely remove this provider, go ahead. |
|
Would it also be a good idea to check if there are any other stale/non existent model providers? |
Merge PR 756 directly so its stale-provider removal commits remain visible before the branch continues with provider registry cleanup. Constraint: Preserve visible PR merge history for PR 756 Confidence: high Scope-risk: narrow Related: #756 Tested: GLHF deletion conflict resolved by accepting the PR deletion Not-tested: Synthetic provider replacement Co-authored-by: OmX <omx@oh-my-codex.dev>
For reference: mindcraft-bots#756 Co-Authored-By: A guy working with a decade old computer. <236301863+masterpatrickpl-coder@users.noreply.github.com>
6 participants
typo?