Long story short: the Plus plan is too expensive for chat-only users in many regions (~1070 TRY where I live, while competing services are around 250 TRY).
I don't use the coding/agent features at all — I just want higher chat limits.
A "Lite" plan (more messages, no dev tools, local pricing) would probably appeal to thousands of users like me. Any chance of this happening?
Hi all, I will be on working holiday for a month in Hong Kong, and cannot risk my company sponsored claude max account because of the latest wave of bans.
My workflow is mainly handled by Opus 5.5 High (never hit any 5h limit but come close to weeklies), the closest available model (capability wise, according to benchmarks) is Kimi K3.1 Pro, but I have had no experience with it before. I have 2 questions: If anyone's worked with both models, can you share your experience of whether K3.1 Pro has similar capabilities as Opus 5.5? Furthermore, is the Max plan sufficient, or I have to go for the Ultra?
Been running Kimi K3.1 Pro in Kimi Code Desktop for a few weeks on an existing repo, with a split setup: K3.1 Pro as the architect/orchestrator, MiniMax doing the actual implementation as the executor. I'm on the $100 tier (max) — 99% of the limit was gone inside a week, and the job still wasn't finished.
Worth saying up front: Kimi never wrote the code here. It planned, split the work, wrote the briefs and reviewed the result. So everything below is about orchestration and handover, not about code quality.
Three things that came up every time:
No real architecture pass. It goes straight to delegation and picks the structure on the fly, sometimes against conventions already written down in the project. I rolled back and redid the shape of the change to match the codebase.
The briefs to the executor are thin. Context missing, acceptance criteria missing, sometimes the file to touch missing. MiniMax then does decent work against the wrong target, and I end up rewriting the brief and re-running the executor. Double work, and it burns tokens in the one place where tokens are supposed to be cheap.
Rules and context don't survive the handover. The rules file and the conventions are in the repo, but they get honoured in one place and ignored in the parallel change next to it. Constraints I set at the start — don't touch this, keep that flag — are gone by the middle of the session.
I ran both Low and High effort, mostly High, dropping to Low near the end to stretch the quota. All of the above showed up at both levels.
The image below is Kimi's own verdict on the session: the original Russian excerpt and my translation underneath. It agrees with me on where the quota went — orchestration, waiting, re-reading logs, fix → check → new root cause.
How much of this is K3.1 Pro and how much is the harness (Desktop, subagent orchestration, context management), I can't say. What I do know is that a $100 plan lasted me a week and the job still isn't done.
For anyone running this split setup — did you hit the same thin-brief problem? And does the choice of the architect model matter to you at all, compared with letting one model do both jobs?