What engineering leaders and their teams report about Kimi Code, with every finding tied to its evidence.
Read the findingsPractitioner sentiment, all practitioners
−36 Negative from 42 sources that take a side
How this figure is madeFrom 39 authors in 40 discussions. Use a task pilot to measure accepted work and review time.
May 2026 to Oct 2026.
42 sources from practitioners, by month and sentiment.
Across 42 sources, 9 are positive, 9 mixed, and 24 negative. Usage limits are raised in 8 sources and discussed in 6 more, and practitioners split on whether a plan is good value, while the praise centers on skills, plugins and MCP support.
Positive, mixed and negative sources
The score counts them as 8 positive, 9 mixed and 22 negative votes, one per author. See How the numbers work.
See the evidenceBelow: 1 praise theme, 2 concerns and 1 disagreement.
Counted for All practitioners, from 42 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for All practitioners.
Mixed
T0ha, owner of Camelot
Integrate Kimi Code CLI as a third agentGitHub issue
Kimi Code has no setup-token equivalent: its device-code OAuth tokens stay inside the CLI's home directory and cannot be moved into Camelot's credential store, while an env-only model config works.
Positive
Sidney Gathrid, owner of agent-smith
Add Kimi Code CLI providerGitHub pull request
Adds Kimi Code CLI as a first-class worker provider beside Antigravity, Codex, OpenCode and Claude, with headless stream JSON and session resume.
Mixed
Paulo R. Kraemer, owner of Luvus
fix(integration): run the Kimi Code hook on WindowsGitHub pull request
Luvus's Kimi Code hook never ran on Windows until it switched to a PowerShell command, so Kimi Code now reports its session there too.
Mixed
Fynn Fluegge, owner of agtx
feat: add kimi CodeGitHub pull request
agtx adds Kimi Code as its tenth supported agent with skills and MCP config, working around a CLI that rejects an opening prompt as an unknown command and a trust dialog whose default option exits.
Positive
Doug Finke, owner of PSAISuite
Add Kimi Code providerGitHub pull request
Adds Kimi Code to PSAISuite as an OpenAI-compatible provider that lists the subscription's models and keeps Kimi's reasoning context through tool calls.
Mixed
Mohid Makhdoomi, collaborator on Codev
Support Kimi Code CLI as a builderGitHub issue
A spike found Kimi Code feasible with caveats as a Codev builder agent and validated it end to end, with Kimi as architect left out of scope.
GILD's fact checks, which don't count as sources
Checked Oct 28, 2026.Kimi Code CLI integrates with Zed and JetBrains IDEs over the Agent Client Protocol through the kimi acp subcommand. Using Kimi Code CLI in IDEs
Open them in the recordEvery concern practitioners raise, most raised first.
Counted for All practitioners.
Raised as a concern, 13
Negative
M3-c, MWN Software
VS Code window freezes and offers Reopen when loading a large session from the history listGitHub issue
Opening a large past session from the extension's list made the whole VS Code window stop responding and VS Code offered Reopen; after reopening, the session still could not be loaded.
Negative
krasotun, frontend developer at InfoWatch
VS Code extension: copying chat messages to clipboard does nothingGitHub issue
In the VS Code extension 0.8.3, assistant messages could not be copied by button or Cmd+C, and both failed with no error shown.
Negative
liutengxi, GitHub user
bug: reasoning remains English despite Chinese prompt and explicit Chinese-thinking requestGitHub issue
With Kimi K3.1 Pro Highspeed on Kimi Code CLI 2.3.3, the final answer followed the language of a Chinese prompt but the reasoning stayed English, despite an explicit request for Chinese reasoning.
Negative
wong2kim, owner of wmux
Agent-written OSC 133 marks are read as the shell'sGitHub issue
Kimi Code CLI 2.3.2 writes its own OSC 133 prompt marks and never closes them, and pushes keyboard flags at startup, which breaks wmux's shell integration.
Negative
SHNN16, GitHub user
EnterPlanMode over ACP leaves plan-mode state residue on failure and permanently wedges the sessionGitHub issue
A failed EnterPlanMode call over ACP left every later tool call failing with an internal error; two production sessions of about 600K context were permanently wedged. Reproduced with K3.1 Pro and its 256K variant.
Negative
scott-huberty, OSS developer and statistician at UCLA
Kimi crashes on startup on Node 23.0 to 23.7 despite the published engines rangeGitHub issue
Installed from npm on Node 23.6.0, inside the published engines range, kimi crashed on startup with a missing zlib export.
Negative
Dinoraptor101, 3rd Path LLC
Subagent default model not covered by subscription kills all spawns with 401GitHub issue
The subagent model that /login set up was not included in the author's tier, so every subagent spawn failed with a 401 and resuming the session could not repair it.
Negative
mike-lmctl, founder of lmctl
Restored session permanently loses tool/subagent access when its persisted runtime binding is staleGitHub issue
Sessions first driven over ACP and resumed elsewhere failed on every tool call and subagent spawn; restarting turns did not help, and only a new session escaped.
Negative
keawewong, Digital Strategic Marketing Team
VS Code 0.7.5: approval request never rendered, turn hangs silently until manual abortGitHub issue
An approval request never appeared and the turn hung for 12.2 minutes until manual abort; earlier turns that day ran 41.7 and 14.4 minutes before manual aborts.
Negative
brunoazoulay, Fusengine
Tool calls silently degraded: truncated tool names, dropped arguments, and no-op Bash substitutionsGitHub issue
Tool names arrived truncated and arguments dropped, so the engine answered Tool not found, the model retried, and turns looped until the step budget ran out.
Negative
BougieZoe, Kimi Code CLI user on pay-as-you-go
Ordinary multi-step tasks of 10 or more model round trips froze for tens of minutes to hours, with time to first token up to 243 seconds and 429 retries the user never saw.
Negative
KronisLV, software engineer
Kimi Code's local web UI: a dead subagent stop button and input lag past 600 turnsHacker News comment
In the local web UI, the subagent stop button did nothing, and long conversations slowed until keyboard input lagged by seconds, past about 600 turns.
Negative
Sasank Chilamkurthy, Kimi Code CLI user
No thinking indictor makes it feel like it has hungGitHub issue
Version 0.21.0 dropped the thinking indicator, so the CLI looked hung while the model was working, and the user downgraded to get it back.
Discussed without concern, 2
Mixed
T0ha, owner of Camelot
Integrate Kimi Code CLI as a third agentGitHub issue
Kimi Code has no setup-token equivalent: its device-code OAuth tokens stay inside the CLI's home directory and cannot be moved into Camelot's credential store, while an env-only model config works.
Mixed
Paulo R. Kraemer, owner of Luvus
fix(integration): run the Kimi Code hook on WindowsGitHub pull request
Luvus's Kimi Code hook never ran on Windows until it switched to a PowerShell command, so Kimi Code now reports its session there too.
Counted for All practitioners.
Raised as a concern, 8
Negative
ivanshnarski-netizen, GitHub user
Ultra plan usage stays at 0% despite active K3.1 Pro usageGitHub issue
On Kimi Code CLI 2.3.3 with K3.1 Pro on the Ultra plan, /usage showed 0% of the 5-hour and monthly limits after hours of work that local logs count as 1,367 model calls.
Negative
Dinoraptor101, 3rd Path LLC
Subagent default model not covered by subscription kills all spawns with 401GitHub issue
The subagent model that /login set up was not included in the author's tier, so every subagent spawn failed with a 401 and resuming the session could not repair it.
Negative
Footprint0521, Hacker News commenter
Comment on: GPT 5.6 CyberHacker News comment
Finds Kimi Code's rate limits very low for the price against OpenAI's larger limits.
Negative
SwellJoe, works on Virtualmin
Kimi Code with K3 burned the 5-hour limit and $100 of extra usage on a security-auditing benchmark that was 11% doneHacker News comment
After a coding task, the author ran Kimi Code with K3 on a security-auditing benchmark: it burned through the 5-hour limit and $100 in extra usage and was only 11% finished.
Negative
ffsm8, Hacker News commenter
Comment on: Kimi K3 Is Competitive with Fable; Kimi K3 and Fable Is SoTAHacker News comment
Used more than half of the weekly Kimi allowance in a day and a half and renewed the Anthropic subscription as well.
Negative
thevinter, Hacker News commenter
Comment on: Moonshot AI suspends new subscriptions due to Kimi K3 demandHacker News comment
K3 in Kimi Code thought for about 12 minutes on a repository report and then said the daily quota was exhausted.
Negative
Altern4tiveAcc, Hacker News commenter
Comment on: Moonshot AI suspends new subscriptions due to Kimi K3 demandHacker News comment
One simple prompt through OpenCode on the plan's API key used the whole 5-hour quota, where Cursor finished the same prompt in minutes.
Negative
SwellJoe, Hacker News commenter
Comment on: The Kimi K3 MomentHacker News comment
Kimi K3 worked far longer on a task the commenter runs with every model and used almost all of a 5-hour window on the $19 plan (Kimi's plan page shows $ without naming a currency), where a US$20 OpenAI plan finished in minutes.
Discussed without concern, 6
Positive
Om Londhe, Tech Lead Manager at Mercor
Kimi Code CLI 2.3.2 stopped spawning subagents on its own.X post
Kimi Code CLI 2.3.2 stopped spawning subagents on its own, swarms start only with /swarm, and 2.3.3 warns on high usage, which the author calls a good default.
Mixed
twilwa, owner of red-durable
Add Kimi Code membership provider with K3.1 ProGitHub pull request
Adds Kimi Code subscription-key onboarding with K3.1 Pro and documents Kimi's restriction on non-interactive use, leaving existing background jobs in place.
Mixed
ricsipbr, r/kimi member
I just measured Kimi Quota for Coding on AllegrettoReddit post
Measured one 5-hour window on the legacy Allegretto plan as about 4.5% of the monthly quota and about $7.20 of usage at API prices.
Mixed
Ian Allaway, owner of quota-widget
Add Kimi Code usage to Moonshot providerGitHub pull request
Adds a Kimi Code sign-in that reads the weekly and per-window quotas from the Kimi Code usage endpoint, documented as a reverse-engineered source.
Mixed
easytiger, Hacker News commenter
Comment on: Kimi K3: Open Frontier IntelligenceHacker News comment
Found a gift quota drawn down by Kimi Code CLI use and calls the quota screens odd and vague.
Mixed
Evan-Kim2028, owner of agent-harness-optimizations
Doc: adding Kimi Code CLI (Kimi K2.6) to Droid CLI via BYOKGitHub issue
Uses a Kimi Code subscription with K2.6 in the Droid CLI through BYOK so no paid Droid plan is needed, and notes the Kimi Code endpoint accepts only recognized coding-agent User-Agents.
GILD's fact checks, which don't count as sources
Checked Oct 28, 2026.New subscribers have a rolling 5-hour window and a monthly total quota with no weekly limit, every device and API key shares one quota, and Extra Usage, charged by actual usage, can continue past the quota. Membership benefits
Open them in the recordStatements this group's sources agree on, then the ones close to agreement.
For all practitioners, no statement reaches 5 sources from 3 authors.
Questions the sources split on, with the count on each side.
Evidence remains split
Good value, 2 sources
Some find the allowance generous for the price, especially with high cache rates or as a second plan for review.
Quota too tight, 5 sources
Others use up a 5-hour window or a week's share in one long session and return to Claude or ChatGPT plans.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 1 accounts; GILD prints their sentiment from 20.
1 sources. This group has one account, from a tech lead manager at Mercor.
41 sources. These accounts focus on plan quotas, model quality, and how Kimi Code compares with Claude Code.
42 sources. This count includes every practitioner: individual builders and the team accounts together.
42 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes Plan quotas, model quality, and gaps against Claude Code
Emphasizes Subagent defaults and high-usage warnings in the CLI
What changes with scale. Individual builders try Kimi Code for its models and price and most often hit the quota on long K3 sessions. Developers who build tools around it praise its skills, MCP and plugin support and report CLI bugs in their integrations.
Where this group's sources were published.
Counted for All practitioners, from 42 sources. Change group
48 sources for this group, 6 of them documentation
Earlier evidence remains when it still applies. Records tied to legacy plans or fixed releases carry Needs a recheck.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 48 sourcesAbout this read
A running review of what engineering teams report about Kimi Code, from individual builders to engineering leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 1, individual builders 1 of 41, all practitioners 1 of 42.
Each row opens its sources for the group you are reading.
| Finding | Engineering leaders and teams | Individual builders | All practitioners | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 1 positive, 0 mixed, 0 negative | 8 positive, 9 mixed, 24 negative | 9 positive, 9 mixed, 24 negative | Sources |
| PraiseModel Quality | 0 of 0 positive (under the minimum) | 4 of 4 positive (under the minimum) | 4 of 4 positive (under the minimum) | Sources |
| PraiseModel and Thinking Choice | 0 of 0 positive (under the minimum) | 1 of 1 positive (under the minimum) | 1 of 1 positive (under the minimum) | Sources |
| PraiseSkills, MCP & Plugins | 0 of 0 positive (under the minimum) | 6 of 6 positive | 6 of 6 positive | Sources |
| PraisePrice and Cache Efficiency | 0 of 0 positive (under the minimum) | 3 of 4 positive (under the minimum) | 3 of 4 positive (under the minimum) | Sources |
| PraiseHarness and CLI | 1 of 1 positive (under the minimum) | 0 of 1 positive (under the minimum) | 1 of 2 positive (under the minimum) | Sources |
| ConcernQuota and Usage Limits | 0 of 1 raise it (under the minimum) | 8 of 13 raise it | 8 of 14 raise it | Sources |
| ConcernGaps Against Claude Code | 0 of 0 raise it (under the minimum) | 1 of 1 raise it (under the minimum) | 1 of 1 raise it (under the minimum) | Sources |
| ConcernSpeed and Stalls | 0 of 0 raise it (under the minimum) | 4 of 4 raise it (under the minimum) | 4 of 4 raise it (under the minimum) | Sources |
| ConcernCLI Bugs | 0 of 0 raise it (under the minimum) | 13 of 15 raise it | 13 of 15 raise it | Sources |
| ConcernPermission Safety | 0 of 0 raise it (under the minimum) | 3 of 3 raise it (under the minimum) | 3 of 3 raise it (under the minimum) | Sources |
| DisagreementIs a Kimi Code plan good value against Claude or ChatGPT plans? | Good value 0, Quota too tight 0 (under the minimum) | Good value 2, Quota too tight 5 | Good value 2, Quota too tight 5 | Sources |
| Current readEvidence mix | 7 sources | 47 sources | 48 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
