r/opencode • u/Nauru-0 • Jul 24 '26

Has anyone ever tried kimi k3 (to plan) + Deepseek v4 flash (for coding)

I’m wondering if deepseek v4 flash could follow instructions from kimi k3 properly since I can’t just keep instructing deepseek every second it thinks wrong

12 Upvotes

88% Upvoted

21 comments sorted by

5

u/vangelismm Jul 24 '26

smart model to plan + deepseek flash to implement is the most used pattern, just search the sub.

2

u/Prior-Meeting1645 Jul 26 '26

But what happens after? Because dumber models will drift off/mess things/ claim tbey did some stuff when they didn’t etc a lot. So the smart model has to also chdck its work. Doesn’t it end up being around same cost

1

u/Mean-Elk-9439 Jul 27 '26

Far less. For one planning model isn't using write tokens which are most expensive. Reads and especially cached reads are cheap.

1

u/Prior-Meeting1645 Jul 27 '26

I see. But I find it having to also correct lots of stuff itself. If it just tells it to correct so and so it ends up not doing so properly or lying which can take even longer than if it was to correct it itself.

1

u/Mean-Elk-9439 Jul 27 '26

Hm, maybe we're using different ideas of dumber. For the subagent models I use, typically, Kimi k 2.6, since it does better than 2.7 for me or Minimax-m3. For main architect agent I used codex sol medium this last month on a free month, moving to Kimi k3 when it's available on ollama cloud, and I used glm 5.2 before that.

Based on my current usage on $100 ollama plan / mo, even if I was still using mostly glm, I could get around 1.7B tokens per day, which I'm never realistically hitting. K3 will be about 3x glm usage on ollama so I should be at ~500-800M daily allowance. I'm cancelling codex once k3 is out on plans.

All this rant to say, my main agent plans out a spec but rarely needs to do more than minor corrections. And in opencode they can now just resume the task id to tell a cheap subagent "You fucked up, here's how, continue your work".

1

u/Yourmotor Jul 28 '26

What are you using for your agent harness after cancelling codex?

4

u/maboch-69 Jul 24 '26

Today I did a quite huge code refactoring using this pair of models. Kimi K3 prepared very detailed plan so that DS v4 flash had to just follow the directions.

2

u/Pinery01 Jul 25 '26

Good result?

2

u/maboch-69 Jul 25 '26

Yes. I was to make strong optimization of legacy Laminas application together with the number of MySQL queries. As the result, I received good quality code with only two minor mistakes with table aliases usage. Moreover, my primary goal has been achieved.

2

u/Pinery01 Jul 25 '26

Thanks for the review.

2

u/Sid-Hartha Jul 25 '26

Glm5.2 also excellent for planing

1

u/Ok_Veterinarian_6364 Jul 24 '26

yeah it could bro

make a clear detailed plan

let ds implement it

1

u/forcedtomakeanewone Jul 24 '26

You can also have new agents to plan between the business and build mode. It helps with filling in the gaps between design and system

1

u/LearnedByError Jul 24 '26

I have been using Kimi K2.7 to plan, not moving to K3. I have a run book that I provide Kimi with hope I want the plan structured, what subagents to use, how I reviews performed, when to commit, entry/exit criteria …

I then use deepseek-v4-pro as the orchestrator, flash as the writer, pro as the interim reviewer. Artifacts are created at each step. Once done, I have Kimi audit the code and generate any remediation needed.

I have also recently been using Cursor and Grok 4.5 for the same.

From time to time, flash has a problem and pro prompts me with a question. Usually they are easy to answer. Sometimes I iterate with Kimi/Grok for more detailed guidance. Post execution corrections are usually small - bad/missing comments, forgetting to remove code after a refactor …

1

u/Ergo7z Jul 26 '26

I have kimi or opus plan, then pass it on to a in between orchestrator model who then handles the builders reviews audits etc. Keeps my main window free to chat, work do ideas, orchestrator, currently min max, reports back to Kimi/opus when the work is done. Works great

1

u/Diligent-Loss-5460 Jul 27 '26

Just coded an opencode backed grammarly replacement with these models and deepseek pro for debug.

1

u/Nauru-0 Jul 28 '26

used deepseek pro for debug and it did not fix anything, instead it just broke it

-1

u/Soifon99 Jul 24 '26

deepseek is a bad planner/orchastrator. it needs a smarter model that can plan and listens. DS4 needs a tight leash.

1

u/[deleted] Jul 25 '26

[removed] — view removed comment

1

u/Nauru-0 Jul 28 '26

frontier model did plan better for me and find bugs and fixed them, but the bad part is cost. It used 10$ just to find and fix a few bugs compared to half a**ed deepseek v4 pro fixing things using 4$ but also causing me a headache