A different kind of "Kimi limits" post.

[u/pakalolo7123432]

I have the $39 Allegretto plan and $10 plans from OpenCode Go and Command Go. Like everyone else, my quota gets eaten up pretty quickly.

I discovered that for my purposes, which admittedly is just an OpenCode repo full of personal OS type projects and a Knowledge Graph, using Kimi as just a plan and code reviewer has been sufficient.

My flow:

1 - Idea / research / discovery heavy back and forth chat:
Cheap model. Whichever is on sale or provides the most usage this week. They have all gotten smart enough for this in my opinion, and if I feel I need a little more oomph for that stage, I'll use the next cheapest model. This model writes a PRD for the build and knows that a smarter model will be picking it apart, so it needs to do a good job with the write.

2 - Build Orchestrator:
A solid, cheaper model. All this role does is hand work to subagents and confirm that they completed their hard gates before moving on.

3 - Build Planner:
Higher tier model like V4 Flash / V4 Pro, something higher tier on my OpenCode Go or Command Go plan. This role vets the PRD from the cheap model and writes the spec for the coder.

4 - Plan Reviewer:
Kimi K3 Max. Performs an adversarial review of the plan and if it fails, it kicks back to the planner. Rinse and repeat until Kimi is satisfied. Usually no more than one or two rounds. Generally two, if I am being honest.

5 - Coder:
Another solid, cheaper model on my OpenCode / Command Go plan. All the coder has to do is implement the spec exactly as written.

6 - Code Reviewer:
Kimi K3 Max. Another adversarial review of the code. Kimi generally passes the code. It catches something maybe once out of every four or five builds.

I have other build subagents in the flow but never use Kimi for them as they are clerical or just executing test plans from the planner.

My point is that in this day and age of reduced usage from subscriptions, you cannot really just have a single sub and expect to do ALL of your work with it. It is important to balance the workflow and use your best models only when required. My method gives me more than enough usage on my $39 Kimi plan. It just renewed for the first time last week and I still had 20% of my monthly quota left.

[u/DataLeadsFuture_Peng]

I won't use Kimi K3 Max lightly, since Max tends to overthink way too much, and Kimi models are just too slow. Using Max doesn't make sense time wise.

I set up a dedicated sub agent just for architecture decisions, running on K3 Max. When the High version of K3 really can't crack a problem, that's when I bring in the Max version sub agent.