From 9a9f8a6d9945c9bf3118c557f85ad1956de4f553 Mon Sep 17 00:00:00 2001
From: hermesagent26 <276067471+hermesagent26@users.noreply.github.com>
Date: Sat, 16 May 2026 22:51:17 -0700
Subject: [PATCH] fix(run_agent): detect kimi models via model name for
 reasoning pad
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

 previously only checked provider ID and
base URL. When kimi-k2.6 is served via ollama-cloud (or any third-party
provider), provider is not 'kimi-coding' and base URL is not
api.kimi.com — so reasoning_content pad was never injected. This caused
HTTP 400 from Ollama Cloud's Go backend: 'invalid message content type:
map[string]interface {}'.

Fix: add model-name detection ('kimi' in model.lower()) so any route
serving a kimi model gets the required reasoning_content echo-back.

Refs the 400/401 Telegram errors where kimi-k2.6 via ollama-cloud
consistently failed after tool-call turns.
---
 run_agent.py | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/run_agent.py b/run_agent.py
index 41af78f16c3..b239f2aeb60 100644
--- a/run_agent.py
+++ b/run_agent.py
@@ -10437,12 +10437,16 @@ class AIAgent:
         Kimi ``/coding`` and Moonshot thinking mode both require
         ``reasoning_content`` on every assistant tool-call message; omitting
         it causes the next replay to fail with HTTP 400.
+
+        Also detects Kimi models served through third-party providers (e.g.
+        ollama-cloud) by matching ``kimi`` in the model name.
         """
         return (
             self.provider in {"kimi-coding", "kimi-coding-cn"}
             or base_url_host_matches(self.base_url, "api.kimi.com")
             or base_url_host_matches(self.base_url, "moonshot.ai")
             or base_url_host_matches(self.base_url, "moonshot.cn")
+            or "kimi" in (self.model or "").lower()
         )
 
     def _needs_deepseek_tool_reasoning(self) -> bool: