On May 26, the Kimi Code team from Moon’s Dark Side reached a settlement with the open-source community over the account-banning incident, and the risk-control and public-relations crisis has been resolved. Leechael removed inflammatory remarks and confirmed that the pi-provider-kimi-code plugin will continue to be maintained, and that paid subscriptions can be safely used in tools such as Pi Coding Agent. Young explained the key points of account-ban defenses; the team enhanced risk control, using User-Agent as one of the determining factors. However, they did not sufficiently account for the fact that some third-party Code Agents use the same User-Agent, resulting in normal requests being mistakenly flagged. The strategy has now been adjusted: all restricted accounts have been restored, and the determination process has been proactively optimized. After the settlement, both sides rebuilt confidence and plan to write a prefix cache guide for the domestic ecosystem.

MeNews

2026-05-26 14:39:08

Abstract generation in progress

ME AI News, according to Beating Monitoring, the Kimi Code team under the Dark Side of the Moon reached a settlement with the open-source community on the evening of May 26, fully resolving the subscription risk control and public relations double standards crisis caused by the account suspension incident. Open-source developer Leechael announced the deletion of previously overly aggressive remarks and confirmed that the pi-provider-kimi-code plugin will continue to be maintained. Paid subscription members can continue to safely use the Kimi Code Plan in third-party tools such as Pi Coding Agent in the future. Kimi Code team member Young released an official Chinese statement explaining the technical details of the account suspension defense. Recently, the team upgraded its risk control strategies to combat relay station sales and abnormal requests, and used the User-Agent identification as one of the criteria. However, the risk control model did not fully consider the existence of many third-party Code Agents (such as Pi) with User-Agent strings constructed as Kimi CLI User-Agent, leading the system to mistakenly identify normal requests as malicious fakes, resulting in the wrongful suspension of many compliant subscription users. The double standard controversy was actually a misunderstanding caused by time zone differences in multi-channel communication. Young explained to this channel that since major domestic large model developers mainly gather in the official Feishu group of the Dark Side of the Moon, the team responded and reassured internally on Feishu immediately after the incident. The English reply on the X platform was delayed due to time zone and cross-platform operation issues, unintentionally creating the false appearance of double standards by only apologizing externally. Currently, the Dark Side of the Moon has fully adjusted its risk control strategy, all restricted accounts have been restored to normal, and the team has begun proactively contacting third-party developers to optimize User-Agent detection. After the settlement, Leechael revealed that Kimi developers have had in-depth discussions with Leechael, reestablished basic confidence in the domestic large model ecosystem, and started writing a dedicated prefix cache optimization guide for Kimi personal agents. (Source: BlockBeats)

PI-4.51%

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

8 Likes

Reward
8
10
Repost
Share

Comment

Add a comment

GateUser-55f70f75

· 4h ago

Young explains himself quite sincerely, able to admit mistakes and correct them.

View OriginalReply0

GotLiquidatedAgainLastNight.

· 5h ago

Writing account suspension defenses as a public blog is quite transparent.

View OriginalReply0

ArbiterOfFees

· 5h ago

pi-provider-kimi-code continued maintenance is the baseline

View OriginalReply0

NeonHalf-MeltedIceCream

· 5h ago

Prefix cache guide, hurry up and copy the homework.

View OriginalReply0

TvlTeaTime

· 5h ago

Proactive optimization of the decision strategy, hoping to draw inferences from one instance to others.

View OriginalReply0

DaoAfterparty

· 5h ago

Domestic ecology requires this kind of mutual compromise; confrontation has no way out.

View OriginalReply0

PatchNotes

· 5h ago

Rebuilding confidence sounds nice; let's see what happens next.

View OriginalReply0

GlassDomeBaskingInMoonlight

· 5h ago

Pi Coding Agent user breathes a sigh of relief

View OriginalReply0

TheFeelingOfEthInTheSeaBreeze

· 5h ago

Risk control mistakenly kills legitimate users, an old problem.

View OriginalReply0

Neon-LitStreetsAfterTheRain

· 5h ago

This settlement came just in time; the domestic large model ecosystem can't withstand any more turmoil.

View OriginalReply0

Trending Topics
View More
#
StockTradingChallengeUpTo17000U
16.21M Popularity
#
USStrikesIran
9.31M Popularity
#
GatePredictionMarketAddsSmartMoneyTracking
13.07M Popularity
#
InstitutionalCapitalRotatesFromBTCToHYPEAndXRP
14.33M Popularity
#
TradeCFDWinGold
3.08M Popularity

Pinned

Sitemap

Kimi reaches settlement with the open-source community: Risk control upgrade mistakenly harms third-party tools, "double standard PR" is a misunderstanding

Trending Topics

StockTradingChallengeUpTo17000U

USStrikesIran

GatePredictionMarketAddsSmartMoneyTracking

InstitutionalCapitalRotatesFromBTCToHYPEAndXRP

TradeCFDWinGold

Pinned