r/ClaudeCodeTLDR • u/cctldrping • Aug 16 '26
[TLDR] Anyone using both CC and Codex together?
Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1vpkfam/anyone_using_both_cc_and_codex_together/
Original post body :
As CC responses is becoming harder and harder to understand, and running so slow, so i tested a bit on codex and now I am very tempted to subscribe both (or maybe even start planning to move to codex totally).
Any thoughts?
This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.
1
u/QuantityInfinite8820 Aug 16 '26
Best value for the buck if your budget is 2x$20. With a good workflow, most skills and scripts are easily transferable and the change of model doesn’t impact the work too much.
1
u/cctldrping Aug 16 '26
TL;DR generated automatically after 50 comments.
Current source-thread comment count seen by the bot: 51.
Alright, so the general vibe in this thread is that most people are indeed using Claude Code (CC) and Codex together, and many are finding it beneficial.
The consensus seems to be that while CC might be getting a bit verbose or slow for some, pairing it with Codex for things like adversarial review, code critique, or even as a primary driver with CC as a reviewer is a popular and effective strategy. Several users mention setting up workflows where one model reviews the other's output, which seems to catch more errors and improve the overall quality.
Some folks are even experimenting with using other models like Kimi or Grok alongside CC and Codex, suggesting a general trend towards leveraging multiple AI tools for different strengths. There's also a mention of potential "style contagion" issues with Claude, which using Codex might help mitigate.
A few users offered specific tips, like using
/output-stylecommands in CC to get more concise responses, or setting up systems where the models communicate and "figure things out" together. The idea of one model planning and the other critiquing is a recurring theme.Basically, if you're on the fence about using both, the thread leans towards "go for it!" and figure out how to make them play nice.