Srihari Sriraman shared in

Public

Analyzed PR fix applicability for Vercel AI GatewayPublic

Agent

Model

Kimi-K2.5

Started

Jan 29, 2:05 AM

Messages43

Downloads0

Summary

In Progress

Understand
Reviewed PR details and related session.
Understand
Understand
Identified API differences between OpenRouter and Vercel.
Understand
Understand
Analyzed tool call token leakage issue in Vercel session.
Understand

You are given one or more GitHub PR URLs: https://github.com/badlogic/pi-mono/pull/987 pull inot a local branch please

For each PR URL, do the following in order:

Read the PR page in full. Include description, all comments, all commits, and all changed files.
Identify any linked issues referenced in the PR body, comments, commit messages, or cross links. Read each issue in full, including all comments.
Analyze the PR diff. Read all relevant code files in full with no truncation from the current main branch and compare against the diff. Do not fetch PR file blobs unless a file is missing on main or the diff context is insufficient. Include related code paths that are not in the diff but are required to validate behavior.
Check for a changelog entry in the relevant packages/*/CHANGELOG.md files. Report whether an entry exists. If missing, state that a changelog entry is required before merge and that you will add it if the user decides to merge. Follow the changelog format rules in AGENTS.md. Verify:
- Entry uses correct section (### Breaking Changes, ### Added, ### Fixed, etc.)
- External contributions include PR link and author: Fixed foo ([#123](https://github.com/badlogic/pi-mono/pull/123) by [@user](https://github.com/user))
- Breaking changes are in ### Breaking Changes, not just ### Fixed
Check if packages/coding-agent/README.md, packages/coding-agent/docs/.md, packages/coding-agent/examples/**/.md require modification. This is usually the case when existing features have been changed, or new features have been added.
Provide a structured review with these sections:
- Good: solid choices or improvements
- Bad: concrete issues, regressions, missing tests, or risks
- Ugly: subtle or high impact problems
Add Questions or Assumptions if anything is unclear.
Add Change summary and Tests.

Output format per PR: PR: Changelog:

... Good:
... Bad:
... Ugly:
... Questions or Assumptions:
... Change summary:
... Tests:
...

If no issues are found, say so under Bad and Ugly.

continue

Let me read the relevant source files to understand the full context:

Let me check if there are any documentation updates needed and review the PR comments more carefully:

Now let me pull the PR into a local branch:

PR: https://github.com/badlogic/pi-mono/pull/987

Changelog:

Entry exists in packages/ai/CHANGELOG.md under ### Fixed
Issue: Missing PR link and author attribution for external contribution
Current: Fixed OpenRouter Kimi K2.5 tool-call replay by mapping reasoning fields to reasoning_content and ensuring it is present when reasoning is enabled.
Required format: Fixed OpenRouter Kimi K2.5 tool-call replay by mapping reasoning fields to \reasoning_content` and ensuring it is present when reasoning is enabled (#987 by @banteg)`

Good:

Targeted fix: The change correctly addresses the root cause. OpenRouter/Kimi expects reasoning_content specifically, not reasoning or reasoning_text
Safe fallback: Adding reasoning_content: "" when missing prevents 400 errors without changing behavior for working conversations
Minimal scope: Only affects OpenRouter provider, no risk of breaking other providers
Proper gating: The fix only applies when reasoningEnabled && isOpenRouter
Preserves existing reasoning: The field mapping preserves actual thinking content when present

Bad:

Changelog format: Missing PR link and author attribution per AGENTS.md rules
Comment from ben-vargas suggests broader fix: The check model.provider === "openrouter" won't work for Vercel AI Gateway or other proxies that route to Kimi. Checking model slug would be more robust (though this is an enhancement, not blocking)
Comment from kiranjd: Points out that Kimi returns reasoning_details with type: "reasoning.text" but pi-ai only stores reasoning.encrypted type. The PR's empty string fix stops the error but doesn't preserve actual reasoning. This is a valid observation, though the current fix is simpler and sufficient for the error case

Ugly:

Provider instability: Per badlogic's comments, OpenRouter's Kimi support is unstable ("clown shit"). This fix may become obsolete or need further changes as OpenRouter/Moonshot stabilize their implementation
No tests: No test coverage for the new behavior. The cross-provider handoff test suite could benefit from an OpenRouter Kimi case

Questions or Assumptions:

Does this fix also help with Vercel AI Gateway Kimi? badlogic's comment suggests Vercel also has issues ("It craps itself on Vercel as well")
Should the check be based on model ID (containing "kimi") rather than provider to catch all Kimi routing scenarios?

Change summary:

Pass reasoningEnabled boolean to convertMessages() based on options.reasoningEffort
Detect OpenRouter via model.provider === "openrouter"
Map reasoning field signatures (reasoning, reasoning_text, reasoning_content) to reasoning_content for OpenRouter
Add empty reasoning_content: "" to assistant tool-call messages when reasoning is enabled, OpenRouter, and the field is missing
Regenerated models list (adds Kimi K2.5 for OpenRouter/Vercel, removes some deprecated models)

Tests:

No new tests added
PR author states: "Reproduced the failing session locally and confirmed the converted assistant tool-call message now includes reasoning_content"
npm run check passes (per PR description)

Documentation:

No documentation updates needed for packages/coding-agent/README.md or docs/*.md. This is a provider compatibility fix, not a user-facing feature change.

The PR is now in local branch fix/kimi-pr-987-work. If you want to merge, I'll need to fix the changelog attribution first.

/Users/badlogic/.pi/agent/sessions/--Users-badlogic-workspaces-pi-mono--/2026-01-29T02-05-25-874Z_bb1f1612-2f68-4d2b-a37e-f97536a9d087.jsonl

any idea if we use @packages/ai/src/providers/openai-completions.ts for vercel? this is a session where the model eventually spits out a thinking trace that includes a tool call

Looking at the session, Vercel AI Gateway with Kimi K2.5 uses anthropic-messages API, not openai-completions:

So the PR fix won't help Vercel because it only modifies openai-completions.ts.

The last message in that session shows the problem: Kimi's internal tool call format leaked into the thinking trace:

This is the model outputting what should be tool calls as raw text inside the thinking block. The stop reason is "stop" (not "toolUse"), so the tool calls were never properly parsed.

Let me check how Vercel models are configured:

So the picture is:

OpenRouter Kimi K2.5 → openai-completions API → PR fix applies here
Vercel AI Gateway Kimi K2.5 → anthropic-messages API → PR fix does NOT apply

The session you shared shows Kimi outputting its internal tool call format (<|tool_calls_section_begin|>) as raw text inside the thinking block instead of proper tool calls. This is a different bug that the PR doesn't address.

Let me check the Anthropic provider to see if there's anything relevant:

The Anthropic provider has proper thinking handling for Claude, but Kimi isn't Claude. When Vercel routes Kimi through anthropic-messages API format, Kimi appears to emit its internal control tokens (<|tool_calls_section_begin|>, <|tool_call_begin|>, etc.) as raw text instead of proper tool calls.

Summary:

PR #987 scope: Only fixes OpenRouter Kimi via openai-completions API
Vercel Kimi issue: Different bug. Vercel uses anthropic-messages API for Kimi, and the model outputs its internal tool call format as literal text in thinking traces
The PR won't help Vercel at all

The Vercel issue is likely:

Kimi doesn't properly support the Anthropic message format for tool calls when thinking is enabled
Or Vercel's translation layer doesn't handle Kimi's reasoning+tool combination correctly

This aligns with badlogic's comment on the PR: "It craps itself on Vercel as well" and "OpenRouter is clown shit, HF is meh, rest is fine". The "rest is fine" probably refers to providers that route directly to Moonshot (like OpenCode Zen), not Vercel.

Should we still merge the PR for the OpenRouter fix, or wait for broader Kimi support to stabilize?

Changelog:

Entry exists in packages/ai/CHANGELOG.md under ### Fixed

Issue: Missing PR link and author attribution for external contribution

Current: Fixed OpenRouter Kimi K2.5 tool-call replay by mapping reasoning fields to reasoning_content and ensuring it is present when reasoning is enabled.

Required format: Fixed OpenRouter Kimi K2.5 tool-call replay by mapping reasoning fields to \reasoning_content` and ensuring it is present when reasoning is enabled (#987 by @banteg)`

Good:

Targeted fix: The change correctly addresses the root cause. OpenRouter/Kimi expects reasoning_content specifically, not reasoning or reasoning_text

Safe fallback: Adding reasoning_content: "" when missing prevents 400 errors without changing behavior for working conversations

Minimal scope: Only affects OpenRouter provider, no risk of breaking other providers

Proper gating: The fix only applies when reasoningEnabled && isOpenRouter

Preserves existing reasoning: The field mapping preserves actual thinking content when present

Bad:

Changelog format: Missing PR link and author attribution per AGENTS.md rules

Comment from ben-vargas suggests broader fix: The check model.provider === "openrouter" won't work for Vercel AI Gateway or other proxies that route to Kimi. Checking model slug would be more robust (though this is an enhancement, not blocking)

Comment from kiranjd: Points out that Kimi returns reasoning_details with type: "reasoning.text" but pi-ai only stores reasoning.encrypted type. The PR's empty string fix stops the error but doesn't preserve actual reasoning. This is a valid observation, though the current fix is simpler and sufficient for the error case

Ugly:

Provider instability: Per badlogic's comments, OpenRouter's Kimi support is unstable ("clown shit"). This fix may become obsolete or need further changes as OpenRouter/Moonshot stabilize their implementation

No tests: No test coverage for the new behavior. The cross-provider handoff test suite could benefit from an OpenRouter Kimi case

Change summary:

Pass reasoningEnabled boolean to convertMessages() based on options.reasoningEffort

Detect OpenRouter via model.provider === "openrouter"

Map reasoning field signatures (reasoning, reasoning_text, reasoning_content) to reasoning_content for OpenRouter

Add empty reasoning_content: "" to assistant tool-call messages when reasoning is enabled, OpenRouter, and the field is missing

Regenerated models list (adds Kimi K2.5 for OpenRouter/Vercel, removes some deprecated models)