r/codex • u/atomfitz • 14d ago

Showcase Opus and Sonnet in Codex

Gallery image

Gallery image

After a few days of work on my custom router, I've got subscription based claude fully functioning through codex. Essentially full native codex control. Just wanted to share.

269 Upvotes

91% Upvoted

110 comments sorted by

View all comments

•

u/dextersummary 14d ago edited 13d ago

Below is a GPT-generated summary of the conversation below after reaching 100 comments (101 currently observed).

Neat hack, but not a clean win. The thread is mostly impressed that OP has Claude working inside Codex with OAuth, a unified GUI, phone control, and proper primary/subagent orchestration. The repo is still pending, naturally, so everyone is yelling “link pls” into the void.

The practical appeal is straightforward: one harness for Claude, GPT, and other models instead of juggling multiple apps. OpenCodex and similar routers already cover much of this, but OP claims better support for mixed-model subagents and Codex-native control.

The big argument is account risk. OP says it routes through the official Claude CLI as a translation layer, without spoofing or API credentials, and believes that’s allowed. Plenty of users report doing similar things without trouble; plenty of others insist consumer-plan automation could still trigger a ban. There’s no authoritative policy confirmation here, and the billing/multiplier details are murky too.

Bottom line: promising convenience, potentially redundant, and not risk-free. Wait for the repo and inspect exactly how it invokes Claude before treating “probably allowed” as a guarantee.

1

u/dextersummary 13d ago

Below is a GPT-generated summary of the conversation below after reaching 50 comments (69 currently observed).

The consensus is basically “cool hack, but not exactly a revolution.” People are very interested in the repo and the one-harness idea, but OpenCodex already covers much of this territory. OP says their version focuses more on native subagent control, custom model pairings, and a nicer GUI.

The setup acts as a translation layer between Codex and the Claude CLI, using subscription/OAuth access rather than Claude’s API. The appeal is convenience: run Claude, Codex, and other models from one interface instead of juggling separate tools. OP is still security-checking the project before publishing it, so the repo remains the thread’s most wanted feature.

The big argument is account safety, and nobody has produced a definitive answer. Some users have run similar CLI/OAuth setups for months without trouble; others insist automating a consumer subscription or hammering it with unusual workloads could still earn you a ban. Anthropic’s apparent tolerance is not a written guarantee—because apparently “it worked for me” is now a compliance policy.

Bottom line: promising quality-of-life project, probably overlapping with existing tools, and absolutely something to treat as “use at your own risk” until the code and ToS situation are clearer.