openclaw - 💡(How to fix) Fix [Bug]: kimi-coding/k2p5 XML function calling format leaks to user messages

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

When using kimi-coding/k2p5 model, XML function calling format leaks directly to user messages instead of being parsed and executed.

Root Cause

When using kimi-coding/k2p5 model, XML function calling format leaks directly to user messages instead of being parsed and executed.

Code Example

<function_calls>
  <invoke name="exec">
    <parameter name="command">cat ~/.openclaw/logs/cron.log</parameter>
  </invoke>
</function_calls>

### OpenClaw version

2026.3.8

### Operating system

macOS26.3.1

### Install method

npm global

### Model

kimi-coding/k2p5

### Provider / routing chain

moonshot

### Config file / key location

_No response_

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

right return

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: kimi-coding/k2p5 XML function calling format leaks to user messages