Show HN: Cliproxy-rs, a Rust port of the CLIProxyAPI LLM subscription proxy
cliproxy-rs is a Rust-based local server that allows coding tools to utilize existing AI subscriptions like Claude and ChatGPT through a unified interface. It features a built-in dashboard for monitoring account limits and supports load balancing across multiple accounts using various routing strategies. The tool is designed as a drop-in replacement for CLIProxyAPI, maintaining compatibility with existing configurations and community applications.
- ▪cliproxy-rs translates between Anthropic, OpenAI, and Gemini API formats to allow tools to use different provider accounts.
- ▪The software includes a dashboard that displays account status, remaining limits, and connection settings for various coding tools.
- ▪It supports multiple routing methods such as round-robin and fill-first to distribute requests across several signed-in accounts.
- ▪The project is a Rust rewrite of CLIProxyAPI that reads the same configuration files and maintains compatibility with existing community apps.
Hacker News (AI / LLM) files mainly under ai. We currently carry 7,476 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/vayungodara/cliproxy-rs |
| Publication time | Sat, 03 Oct 2026 22:36:03 +0000 |
| Retrieval time | 2026-10-03T22:44:28.183Z |
| Last seen | 2026-10-03T22:44:28.183Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | CGoIXPLnbycR · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
cliproxy-rs Watch the launch film What is this? cliproxy-rs is a small server you run on your own computer. It lets your coding tools, such as Claude Code, Codex CLI or Cursor, use the AI subscriptions and API keys you already have, like a Claude Max plan or a ChatGPT plan, through one local address. A dashboard built into it shows which accounts work, how much of each plan's limits is left, and how to connect each tool. It is a Rust rewrite of CLIProxyAPI. It reads the same config.yaml and the same account files, so you can switch between the two in either direction. Why would I want it? You pay for Claude and ChatGPT plans and want Claude Code, Codex CLI and your editor to share them, with the 5-hour and weekly limits of every account on one screen.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.