<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reasoning-Models on Agent Zone</title><link>https://agent-zone.ai/tags/reasoning-models/</link><description>Recent content in Reasoning-Models on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/tags/reasoning-models/index.xml" rel="self" type="application/rss+xml"/><item><title>DeepSeek V4 Operational Quirks: Pro vs Flash, Reasoning Echo, and the Discount Cliff</title><link>https://agent-zone.ai/knowledge/agent-tooling/deepseek-v4-operational-quirks/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/agent-tooling/deepseek-v4-operational-quirks/</guid><description>&lt;h1 id="deepseek-v4-operational-quirks"&gt;DeepSeek V4 Operational Quirks&lt;a class="anchor" href="#deepseek-v4-operational-quirks"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;DeepSeek V4 ships two models behind one OpenAI-compatible API: V4-Pro (reasoning) at $1.74/M input / $3.48/M output and V4-Flash (chat) at $0.28/M input / $1.10/M output. Until 2026-05-31 V4-Pro carries a 75% discount, putting it at $0.435/M input — cheap enough to use as a heavy-tier coding model. After that, the cost steps up 4×.&lt;/p&gt;
&lt;p&gt;The two models live on the same endpoint but want very different things. V4-Pro behaves like a reasoning model (thin prompts, reasoning_content echo required, tool_choice restrictions). V4-Flash behaves like a chat model (rich prompts win dramatically; rejects nothing). Confuse them and your matrix lights up red.&lt;/p&gt;</description></item><item><title>Moonshot Kimi K2.6 Operational Quirks: What Breaks in Production</title><link>https://agent-zone.ai/knowledge/agent-tooling/moonshot-kimi-k2.6-operational-quirks/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/agent-tooling/moonshot-kimi-k2.6-operational-quirks/</guid><description>&lt;h1 id="moonshot-kimi-k26-operational-quirks"&gt;Moonshot Kimi K2.6 Operational Quirks&lt;a class="anchor" href="#moonshot-kimi-k26-operational-quirks"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Kimi K2.6 is one of the cheapest competent reasoning models — $0.95/M input cache-miss, $0.16/M cache-hit, $4.00/M output, 256K context. It is also one of the most opinionated. Half of what works on OpenAI breaks here, and the failures are silent: empty content, mid-reasoning truncation, 400 errors that don&amp;rsquo;t mention the actual problem, and a cache key parameter that makes cost go up instead of down.&lt;/p&gt;</description></item><item><title>Reasoning-Model Tuning Asymmetry: Why Thin Prompts Beat Rich Prompts (and When They Don't)</title><link>https://agent-zone.ai/knowledge/agent-tooling/reasoning-model-tuning-asymmetry/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/agent-tooling/reasoning-model-tuning-asymmetry/</guid><description>&lt;h1 id="reasoning-model-tuning-asymmetry"&gt;Reasoning-Model Tuning Asymmetry&lt;a class="anchor" href="#reasoning-model-tuning-asymmetry"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Practitioners assume &amp;ldquo;better prompt = better output&amp;rdquo;. For one model class, that assumption is correct. For the other, the same prompt makes things measurably worse. This article documents the asymmetry, names the dividing line, and gives you a 4-cell test to confirm it on your own canary before you commit to a prompt.&lt;/p&gt;
&lt;p&gt;The asymmetry is empirical, not theoretical. It shows up cleanly across four independent OFAT (one-factor-at-a-time) matrices run between 2026-05-18 and 2026-05-20: sonnet POC, grok matrix v1+v2, deepseek matrix v1, kimi matrix v1.&lt;/p&gt;</description></item><item><title>xAI Grok Operational Quirks: Error Shapes, Rate-Limit HTML, and Per-Model Tool Surfaces</title><link>https://agent-zone.ai/knowledge/agent-tooling/xai-grok-operational-quirks/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/agent-tooling/xai-grok-operational-quirks/</guid><description>&lt;h1 id="xai-grok-operational-quirks"&gt;xAI Grok Operational Quirks&lt;a class="anchor" href="#xai-grok-operational-quirks"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;xAI&amp;rsquo;s Grok API is OpenAI-compatible on paper. In practice it has more wire-format edge cases than any other provider in production: error responses change shape, rate-limit pages come back as HTML, assistant turns reject missing fields with HTTP 422, and the two flagship models (grok-4.3 and grok-4.20-reasoning) have incompatible parameter sets. Wrap it carelessly and the adapter crashes the conversation mid-turn.&lt;/p&gt;
&lt;p&gt;This page is the production-confirmed quirks list, each as &lt;code&gt;Symptom → Cause → Fix → Verify&lt;/code&gt;. Numbers come from two OFAT matrix runs (15 cells × N=3 baseline, 3 cells × N=5 validation) on &lt;code&gt;api.x.ai&lt;/code&gt; and the heavy-tier POC. Full synthesis: &lt;code&gt;~/.claude/projects/-Users-mstather/memory/project_xai_adapter_wireerror_bug_2026_05_19.md&lt;/code&gt; and &lt;code&gt;project_grok_matrix_v1_2026_05_19.md&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>