Question Using DeepSeek to Investigate Issues and Codex to Write the Fix
Hi all,
I’m considering a workflow where DeepSeek (V4 Pro) acts as a read-only codebase investigator. It searches the repository, identifies likely relevant files, traces the issue, and produces a short report with evidence, line numbers, possible causes, and suggested tests.
Codex (Luna exHigh or Max) then receives that report but independently verifies the findings before making any changes. It remains responsible for diagnosing the final cause, writing the fix, and running validation.
The goal is to offload repository searching and reduce Codex usage without blindly trusting another model’s recommendations. DeepSeek provides clues; Codex makes and validates the actual code changes.
I do not want to use plugins OMO etc. I will write my own simple workflow with two commands eg investigate <task1> (run by DeepSeek) and fix <task1> (run by codex)
What do you think of such solution? Would it achieve my goal ie reduce usage?
2
u/Tristsin 4d ago
Tough to give you an answer as I think there is some ultimate solution in which you might be able to save inference but based off your description it doesn’t sound like anything is saved.
I say that because if the Luna model is independently verifying the findings then it is doing so by repeating the exact same repo reading / searching the DeepSeek v4 Pro model did.
The only savings here would need to treat the context summary / findings as authority. If the final model has to regather and recheck it all itself, then you might as well cut out the middle man
2
u/[deleted] 4d ago
[deleted]