-
|
This is kind of a dumb question to ask since we know Claude Flow is overdependent on Anthropic's Claude Code, and that everyone is copying them. Qwen-code, Gemini CLI, etc... But at the same time, there are unified providers for LLMs like OpenRouter, ready to hot-swap models while everyone uses OpenAI-compatible API (instead of whatever GPT-OSS is doing with Harmony, OR Anthropic's API format needing Claude-Code-Router). https://github.com/musistudio/claude-code-router |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
|
My guess to the solution https://github.com/RoderickGrc/gemini-cli-proxy-for-ollama https://github.com/csyangwen/OpenAI-to-Gemini-API-Proxy |
Beta Was this translation helpful? Give feedback.
-
|
A potential solution https://github.com/acoliver/llxprt-code/ - a fork of gemini-cli that supports nearly every provider and model including local as well as auth to Qwen, Gemini and Claude Max/Pro -- and cerebras's new Cerebras Code system. It also has claude style todo lists. |
Beta Was this translation helpful? Give feedback.
-
|
This is an interesting question! So natively, the purpose of this was to really harness and hone in on Google's native ecosystem as much as possible. Part of why I wanted to submit this project under an MIT license is that if someone wants to try to tie my tool to OpenRouter and the like, they're more than free to do so. What I will try to do is a meeting in the middle; there may be some sort of way I can try to work in a layer whereby there's an "interrupt" in the workflow where a workflow split branches off, and calls to something like OpenRouter, Together.ai, Groq, Samba, etc. that may allow for some limited customization, but tbh, this won't be something I prioritize (there's too many kinks that need to be worked out and way too much core development to do at this time...), but it is something I'll take into consideration as I develop along the project! |
Beta Was this translation helpful? Give feedback.
This is an interesting question!
So natively, the purpose of this was to really harness and hone in on Google's native ecosystem as much as possible. Part of why I wanted to submit this project under an MIT license is that if someone wants to try to tie my tool to OpenRouter and the like, they're more than free to do so.
What I will try to do is a meeting in the middle; there may be some sort of way I can try to work in a layer whereby there's an "interrupt" in the workflow where a workflow split branches off, and calls to something like OpenRouter, Together.ai, Groq, Samba, etc. that may allow for some limited customization, but tbh, this won't be something I prioritize (there's too many…