Summary
Please consider adding Cline as a supported service in VibeProxy, alongside the services/providers that are already documented today, such as Claude Code, ChatGPT/Codex, Gemini via Antigravity or Google Cloud, Kimi, Qwen, Z.AI GLM, and GitHub Copilot.
Why this seems relevant
From the public Cline documentation, Cline now exposes a programmatic API with an OpenAI-compatible Chat Completions API.
VibeProxy already positions itself as a local proxy / OpenAI-compatible bridge for subscription-backed AI services, so Cline appears conceptually aligned with the current scope of the project.
What I checked
- I searched existing VibeProxy issues for
cline and found no matches:
- I also could not find any existing mention of Cline support in the repository documentation/settings surfaces that describe supported services.
Request
Please evaluate adding Cline as another supported service/provider in VibeProxy.
I am not proposing a specific implementation or auth flow here, only requesting support if it fits the project direction and if Cline's public integration contract is sufficient for VibeProxy.
Public references
Additional context
The reason this request may be a good fit is that Cline publicly documents:
- an API intended for programmatic access
- an OpenAI-compatible chat completions interface
- documented authentication methods
If maintainers think this belongs in scope, Cline would be a useful addition next to the other services VibeProxy already supports.
Summary
Please consider adding Cline as a supported service in VibeProxy, alongside the services/providers that are already documented today, such as Claude Code, ChatGPT/Codex, Gemini via Antigravity or Google Cloud, Kimi, Qwen, Z.AI GLM, and GitHub Copilot.
Why this seems relevant
From the public Cline documentation, Cline now exposes a programmatic API with an OpenAI-compatible Chat Completions API.
VibeProxy already positions itself as a local proxy / OpenAI-compatible bridge for subscription-backed AI services, so Cline appears conceptually aligned with the current scope of the project.
What I checked
clineand found no matches:Request
Please evaluate adding Cline as another supported service/provider in VibeProxy.
I am not proposing a specific implementation or auth flow here, only requesting support if it fits the project direction and if Cline's public integration contract is sufficient for VibeProxy.
Public references
Additional context
The reason this request may be a good fit is that Cline publicly documents:
If maintainers think this belongs in scope, Cline would be a useful addition next to the other services VibeProxy already supports.