Show HN: Run Claude Code Through Codex, Kimi, Grok, or Cursor

A Show HN submission titled "Run Claude Code Through Codex, Kimi, Grok, or Cursor" points to the open-source project claude-code-proxy at github.com/raine/claude-code-proxy. On Hacker News the thread (item id 49027640) sits at 3 points with 1 comment. The pitch is narrow: keep using Claude Code as the client, but route its traffic so the work can run against Codex, Kimi, Grok, or Cursor instead of Anthropic only.

Mechanically, the name and framing imply a proxy in front of Claude Code: the familiar Claude Code interface stays put while requests are redirected to one of the listed alternative providers. That keeps the local workflow and tooling habits intact and swaps only the backend model path. Builders who already live in Claude Code can try another stack without rewriting prompts, scripts, or agent loops around a new CLI.

For engineers this is about lock-in and cost of switching, not novelty. Claude Code is an opinionated agentic coding surface; if the only path out is a full client change, teams stay glued to one vendor. A proxy that preserves that surface while allowing Codex, Kimi, Grok, or Cursor as backends lowers the cost of A/B testing models on real tasks—refactors, test generation, multi-file edits—without discarding existing Claude Code setup.

The competitive backdrop is a crowded field of coding agents and model APIs. Anthropic’s Claude Code, OpenAI’s Codex line, Cursor’s product surface, Grok, and Kimi all compete for the same developer time. Interop layers like this appear when users want model choice without fragmenting their daily driver. Early HN traction is thin (3 points, 1 comment), so this is still an early signal, not a mainstream tool yet.

What to watch next is practical: whether the proxy stays reliable under real Claude Code sessions, how cleanly it maps features across Codex, Kimi, Grok, and Cursor, and whether maintainers keep pace as those products change. If it holds up, the useful pattern is clear—treat the coding agent UI as stable and the model backend as swappable, and evaluate providers on task quality and price rather than on who owns the CLI.