Three-model coding pipeline gives Gemini 4 Argon the repo context job
A video proposes a split coding workflow in which Gemini 4 Argon handles repo context, GPT-6.1 Sol writes patches and Claude Opus 5.5 does adversarial review.
holy sh*t... GPT-6.1 Sol, Claude Opus 5.5 and Gemini 4 Argon in one coding stack sounds ridiculous until you give each one a different job most people still use agents like overpriced interns dump the whole repo into a chat ask for a fix watch it retry the same broken approach get a confident “done” while the tests are still red then blame the model and buy more tokens the architecture in this breakdown takes a different approach: > repo state: track file changes and cache tool results so agents don’t keep rereading unchanged code > parallel execution: split genuinely independent tasks across specialist agents, then join their outputs before integration > isolated patches: let the coding worker explore changes in separate sandboxes without trashing the working branch > verification loop: run tests and linters after each candidate patch. a failed check sends it back with the actual error, not another vague prompt > adversarial review: give a separate reviewer the diff and make it look for bad assumptions, missing edge cases and tests that pass for the wrong reason the proposed model split: Gemini 4 Argon handles repo context GPT-6.1 Sol writes candidate patches Claude Opus 5.5 challenges the result but the useful part isn’t collecting three expensive model names it’s keeping implementation and verification separate a worker saying “fixed” is a claim a diff shows what changed a test run shows what was actually checked and even green tests don’t prove the feature works if nobody tested the thing that broke the original post throws around huge benchmark numbers. without the underlying evaluation, i wouldn’t build a budget around them the workflow is still worth stealing: scope -> split -> patch -> test -> review -> integrate parallelize independent work keep shared-file edits coordinated cache unchanged results make failures visible stop letting the agent grade its own homework otherwise you’ve just built a faster way to generate broken PRs save this before your next “the agent said it was done” moment
This post quotes another post: x.com/sector_sol/status/2093769463065702779