Kimi K3 behaves very differently across API, Claude Code, and its native client
APPSO · wechat · 2026-07-23
This hands-on comparison tests Kimi K3 in four setups for a screenshot-to-HTML task: direct API, Claude Code, Kimi’s native client, and Codex.
What happened
- Direct API: shortest path, but no process feedback; despite that, it delivered the first runnable page fastest.
- Claude Code: felt like a real coding agent because it could inspect files, use the terminal, and iterate, but the first pass generated code without actually writing files to disk.
- Native Kimi client: showed the model inside Moonshot’s own prompting, tools, and delivery flow.
- Codex baseline: used as a comparison point after the bridge to Kimi through CCSwitch kept failing with 502 errors.
Main takeaways
- The same model can behave very differently depending on the harness around it.
- Agent wrappers can add capabilities, but they also add new failure modes: file writes, tool calls, execution feedback, and verification can all break.
- The native client is valuable not because it always produces the prettiest output, but because it hides the operational complexity from normal users.
The article’s bigger point: “wrapper” is not just packaging. A harness can organize capability, create capability, and introduce new bugs at the same time.
More from coding & agent
- SF 'Code Engineering' event picks up where 1,000-person harness engineering meetup left off — LangChain · 2026-10-27
- Prompt turns Claude Code into an iPhone backup forensics tool exposing 30-day 'deleted' photo copies — alex_verem · 2026-10-27
- Prompt turns Claude Code into a forensics tool finding deleted iPhone photos in backups — alex_verem · 2026-10-27
- Phones won't be mobile IDEs but control planes for agent fleets, argues Yuchen Jin — Yuchenj_UW · 2026-10-27
- FrontierCS 2 launches on Kaggle: 48 tasks make agents beat published CS papers — MeganRisdal · 2026-10-27
- Agent Field Kit launches $29 security runbooks for production AI agents — alvelda · 2026-10-27