#6454: fix: enable reasoning flag for Kimi K2.5 in Moonshot provider (#6451)
agents
Cluster:
Kimi Model Enhancements
## Problem
Kimi K2.5 outputs reasoning tokens but was configured with `reasoning: false` in the Moonshot provider config. This caused reasoning content to leak into user-visible output instead of being properly stripped.
## Root Cause
In `models-config.providers.ts`, the Moonshot provider had:
```typescript
{
id: MOONSHOT_DEFAULT_MODEL_ID,
name: "Kimi K2.5",
reasoning: false, // Wrong - model outputs reasoning
...
}
```
Meanwhile, the synthetic model catalog already correctly had `reasoning: true` for `hf:moonshotai/Kimi-K2.5`.
## Fix
Changed `reasoning: false` → `reasoning: true` for Kimi K2.5 in Moonshot provider config.
## Impact
- Enables reasoning tag stripping for Kimi K2.5 via Moonshot provider
- Prevents reasoning leaks in user-visible output
- Makes Moonshot config consistent with synthetic model config
## Testing
This is a configuration change that enables existing reasoning tag stripping infrastructure. The `reasoning-tags.ts` module will now be applied to Kimi K2.5 output.
Fixes #6451
<!-- greptile_comment -->
<h2>Greptile Overview</h2>
<h3>Greptile Summary</h3>
This PR updates the Moonshot provider’s default model definition for **Kimi K2.5** to set `reasoning: true` (was `false`) in `src/agents/models-config.providers.ts`. This aligns the Moonshot provider config with the synthetic model catalog and ensures the existing “reasoning tag stripping” pipeline is applied to Kimi K2.5 outputs, preventing model reasoning tokens from leaking into user-visible text.
Change is localized to the provider model metadata and fits the codebase’s pattern of per-provider static model catalogs used by `resolveImplicitProviders` and other config normalization utilities.
<h3>Confidence Score: 5/5</h3>
- This PR is safe to merge with minimal risk.
- The change is a one-line config correction (enabling `reasoning` for a model known to emit reasoning tokens) and does not alter control flow, APIs, or data formats beyond selecting existing output-stripping behavior.
- No files require special attention
<!-- greptile_other_comments_section -->
<sub>(4/5) You can add custom instructions or style guidelines for the agent [here](https://app.greptile.com/review/github)!</sub>
<!-- /greptile_comment -->
Most Similar PRs
#21911: Enable `reasoning: true` for Kimi models
by ighostych · 2026-02-20
87.2%
#9024: Fix/Moonshot Provider Issue with kimi-k2-thinking Model Role Mappin...
by fotorpics · 2026-02-04
87.0%
#5947: Feature/kimi reasoning support
by zzjj7000 · 2026-02-01
85.9%
#4459: fix: enable image input for Kimi K2.5 and refresh stale config mode...
by manikv12 · 2026-01-30
82.5%
#6960: feat: Add kimi-coding provider support
by YYW0228 · 2026-02-02
80.9%
#6015: CLI: clarify Moonshot AI/Kimi auth option labels based on user feed...
by xxr3376 · 2026-02-01
77.7%
#22194: fix(agent) Moonshot/Kimi kimi-k2.5 returns ROLE_UNSPECIFIED
by ShengFuC · 2026-02-20
77.6%
#19281: fix: set supportsDeveloperRole false as default for moonshot provider
by MisterGuy420 · 2026-02-17
76.4%
#14187: fix: add Moonshot AI to non-standard provider detection
by shad0wca7 · 2026-02-11
75.9%
#12063: feat: add Moonshot (Kimi K2.5) native video understanding provider
by xiaoyaner0201 · 2026-02-08
75.6%