Repository navigation
Proposal: Drop CliProxyApi from Quotio #424
nguyenphutrong
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Proposal: Drop
CliProxyApifrom QuotioI’d like to open a discussion about whether Quotio should gradually drop
CliProxyApias a core dependency.CliProxyApihelped Quotio move faster early on, but over time the dependency has created several maintenance, product, and UX issues.Why Consider Dropping It
1. Quotio is downstream of
CliProxyApiQuotio is currently tightly coupled to how
CliProxyApiimplements providers, configs, endpoints, and internal behavior.Even though Quotio has an update mechanism for the proxy, features can still become out of sync:
This makes Quotio dependent on
CliProxyApi’s roadmap instead of fully owning its own.2.
CliProxyApihas its own management layerCliProxyApiis not just a small proxy core. It has its own configuration and management model.That creates overlap with Quotio:
CliProxyApialso has its own config management.This goes against Quotio’s goal of providing a native, local-first, user-friendly management experience.
3. Upstream issues are difficult to resolve
There are visible issues in
CliProxyApi, but attempts to contribute fixes or open PRs may be closed upstream.That puts Quotio in a bad position:
This is not a stable foundation for a product that aims to provide a polished experience.
4.
CliProxyApiPlusdisappeared without clear reasoningThere was previously a
CliProxyApiPlusversion that supported GitHub Copilot and Kiro. That version was later dropped without a clear explanation.More concerningly, the repository was deleted instead of archived. That removes useful history and makes it impossible to inspect the technical reasoning, previous implementation, or migration path.
For a core dependency, that is a significant maintenance risk.
5. Quotio’s fallback feature requires a second proxy layer
Quotio’s fallback feature is developed separately from
CliProxyApi. Because fallback cannot be integrated naturally into the proxy core, Quotio has to run an additional proxy layer on top ofCliProxyApi.This adds several problems:
If Quotio owns the proxy logic directly, fallback can be implemented in a simpler, more predictable way.
Proposed Direction
I suggest we consider gradually dropping
CliProxyApiand replacing it with a Quotio-owned proxy implementation, or at least removingCliProxyApifrom the critical path.A possible migration path:
CliProxyApi.CliProxyApionly after the main flows are stable.Tradeoff
Dropping
CliProxyApiwill require upfront work, especially around provider compatibility and proxy behavior.However, the long-term benefits are significant:
Overall, I think this is worth discussing seriously if Quotio is intended to become an independent native product rather than a management layer on top of
CliProxyApi.All reactions