Skip to content

Add ccg-router to Model Providers & Proxies#49

Open
linny006 wants to merge 1 commit into
RoggeOhta:mainfrom
linny006:add-ccg-router
Open

Add ccg-router to Model Providers & Proxies#49
linny006 wants to merge 1 commit into
RoggeOhta:mainfrom
linny006:add-ccg-router

Conversation

@linny006
Copy link
Copy Markdown

Adds ccg-router under the Model Providers & Proxies section.

It's a local Go daemon that serves OpenAI-compatible /v1/chat/completions (for Codex CLI) and Anthropic-compatible /v1/messages (for Claude Code) on one port, so both CLIs can share one routing config and one local SQLite usage ledger. Apache-2.0, single static binary.

Why I think it fits this list:

  • Direct Codex CLI integration via OPENAI_BASE_URL=http://127.0.0.1:17180.
  • Sits in the same lane as existing entries like router-for-me/CLIProxyAPI, lich0821/ccNexus, and icebear0828/codex-proxy, but with an explicit dual-CLI focus and a per-request local ledger.
  • Actively maintained (released this month, repo public and accepting issues).

Format follows the section's existing convention (entry name, dash separator, value-led description, shields.io stars badge).

Checked:

  • Entry placed in the most appropriate section.
  • Description is one sentence describing value, not promo copy.
  • Star badge included.
  • Direct Codex CLI relevance.
  • No duplicate entry already in the list.

Local Go daemon serving Codex CLI and Claude Code on one port, with
a SQLite usage ledger per request. Apache-2.0.
@linny006
Copy link
Copy Markdown
Author

Quick update: just shipped v0.2.0 with streaming passthrough for both protocols (released today, https://github.com/XZXY-AI/ccg-router/releases/tag/v0.2.0). The "v0.1 = non-streaming" caveat in the entry text is no longer accurate — happy to edit the PR if helpful, or leave as-is since the entry description doesn't mention streaming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant