Re:Quick impressions: A week of using Codex more than Claude
by artdigital on Saturday August 22, 2026 @09:21PM
(#49405431)
I do the same with Gemini. I have a skill that teaches any AI to use the antigravity cli (agy) to communicate with Gemini and ask to review or check decisions
Re:Quick impressions: A week of using Codex more than Claude
by zatkin on Sunday August 23, 2026 @02:15AM
(#49406427)
There's some real research-backed evidence that this approach elevates output quality, and it was even discussed a few months back: https://news.ycombinator.com/item?id=47169627
Re:Quick impressions: A week of using Codex more than Claude
by smartbit on Sunday August 23, 2026 @02:48AM
(#49406565)
Anthropic confirmed it in their recent report https://news.ycombinator.com/item?id=49316271
> We expect that agents coordinating in the wild will act in higher variance ways than we see here, because they’ll have different backgrounds and therefore different contexts. They also, presumably, won’t all be Claudes.
Re:Quick impressions: A week of using Codex more than Claude
by johnyzee on Sunday August 23, 2026 @05:43AM
(#49407406)
I do use a second Claude (both Opus) to review the first one's output - it almost always finds worthwhile (often critical) observations. They have different 'perspectives', one wants the job done, one wants to find problems, is how I had it explained.
Claude chat itself called it 'Claude-on-Claude action', which I found cute.
Re:Quick impressions: A week of using Codex more than Claude
by piotraleksander on Sunday August 23, 2026 @02:37AM
(#49406521)
btw, there's a dedicated plugin for similar setup https://github.com/openai/codex-plugin-cc
Re:Quick impressions: A week of using Codex more than Claude
by jsmith99 on Sunday August 23, 2026 @03:41AM
(#49406812)
I do a similar thing manually and you have to watch it very carefully to avoid over engineering, ironically you need judgement here not vibe, otherwise (codex especially) will ratchet the project into some complicated enterprise grade over engineered monstrosity by eg coming up with minor visual-only concurrency bugs that would need you to be Facebook scale.
The agents then go for several rounds criticising each other plans and implementations, catching big and small issues on each other’s work. The end result is not perfect, but it is a lot better than what I can get from relying on only one model.