Kimi K3 image recognition hallucinates in Cursor, but works correctly on the official Kimi website

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Long-standing multimodal hallucination bug with Kimi K3 inside Cursor Chat/Agent.

When I attach a screenshot to the chat and ask the model to describe it, Cursor’s Kimi K3 frequently invents content that is not in the image at all (fabricated UI text, wrong apps, wrong websites).

The same model on the official Kimi/Moonshot product describes the same images correctly. So this appears to be a Cursor-side issue (image preprocessing / prompt wrapping / vision pipeline), not a base-model capability problem.

Steps to Reproduce

  1. Open Cursor Chat/Agent and select model: Kimi K3.
  2. Attach a clear screenshot (example: a Gitee profile page showing username @wlgtcl and a private repo “ARC-AGI”).
  3. Ask: “Describe this image accurately. Only report what is visible.”
  4. Observe the response.

Actual result (examples from the same Gitee screenshot):

  • First response hallucinated a Windows CMD window running ping www.google.com -t with IPv6 and “General failure”.
  • After asking to re-identify, it hallucinated a Kaggle ARC Prize 2026 leaderboard with specific fake scores/usernames.
  • Neither Google, CMD, nor Kaggle appears anywhere in the image.
  1. Upload the same screenshot to the official Kimi K3 web product and ask the same question → description is correct (Gitee profile / repo page).

Expected Behavior

The model should only describe content that is actually visible in the attached image.
If uncertain, it should say so, instead of inventing detailed fake UI, text, or brand names.
Cursor’s Kimi K3 vision path should match the official Kimi K3 behavior on the same image.

Screenshots / Screen Recordings

2.png
2.png1588×474 24.2 KB
1.png
1.png653×782 67.5 KB
3.png
3.png944×630 31.4 KB

Operating System

Windows 10/11

Version Information

Version: 3.13.21 (user setup)
VS Code Extension API: 1.128.0
Commit: 55434bd8062ece6fee083b82beed2aee42d253f0
Date: 2026-07-27T03:26:14.573Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Kimi K3

For AI issues: add Request ID with privacy disabled

e42cfd98-245e-4f4f-9f69-9ba5f5da153e

Additional Information

This has been happening for a long time with Kimi K3 vision in Cursor.
Official Kimi K3 web app describes the same images correctly.
Example: a Gitee profile screenshot was misread as CMD ping Google, then as a Kaggle leaderboard.

Important comparison: the official Kimi K3 product does NOT have this problem.

I tested the exact same screenshots on the official Kimi website / app. Image recognition there was correct and stable.

Only inside Cursor Chat/Agent (with Kimi K3 selected) does the model hallucinate image content that is not present in the screenshot.

This strongly suggests a Cursor-side multimodal/vision pipeline issue (image preprocessing, prompt wrapping, or request formatting), not a base-model failure of Kimi K3 itself.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

A post was merged into an existing topic: Kimi K3 completely broken multimodal capabilities