Bug type
Behavior bug (incorrect output/state without crash)
Summary
When receiving .doc files (MIME: application/x-cfb), OpenClaw core
auto-reads the binary content and embeds it into the prompt as text,
causing 70KB of garbage data and "high risk" rejections.
Expected: .doc files should be treated as binary attachments, not text.
Suggested: Use pandoc/catdoc to convert to text before embedding,
or skip content embedding for known binary formats.
Steps to reproduce
- Send a .doc file (Microsoft Word 97-2003 format) to OpenClaw via Feishu channel
- The file MIME type is application/x-cfb (binary OLE format)
- OpenClaw core auto-reads the binary content and embeds it into the prompt
- Result: 70KB of binary garbage data is inserted into the conversation history
- Subsequent messages fail with "high risk" error from the LLM provider
Expected behavior
-
When receiving a .doc file, OpenClaw should either:
- Skip embedding binary content (treat as attachment only)
- OR convert to text first using tools like pandoc/catdoc
-
The conversation history should only contain clean text content,
not raw binary data from .doc files
-
Subsequent messages should continue to work normally without
"high risk" errors
Actual behavior
OpenClaw treats .doc binary files as text and embeds raw binary
content into prompts, causing LLM "high risk" rejections and
corrupted conversation sessions.
OpenClaw version
OpenClaw 2026.3.23-2
Operating system
Linux mint
Install method
No response
Model
kimi code 2.5
Provider / routing chain
feishu -> openclaw -> kimi-coding
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Bug type
Behavior bug (incorrect output/state without crash)
Summary
When receiving .doc files (MIME: application/x-cfb), OpenClaw core
auto-reads the binary content and embeds it into the prompt as text,
causing 70KB of garbage data and "high risk" rejections.
Expected: .doc files should be treated as binary attachments, not text.
Suggested: Use pandoc/catdoc to convert to text before embedding,
or skip content embedding for known binary formats.
Steps to reproduce
Expected behavior
When receiving a .doc file, OpenClaw should either:
The conversation history should only contain clean text content,
not raw binary data from .doc files
Subsequent messages should continue to work normally without
"high risk" errors
Actual behavior
OpenClaw treats .doc binary files as text and embeds raw binary
content into prompts, causing LLM "high risk" rejections and
corrupted conversation sessions.
OpenClaw version
OpenClaw 2026.3.23-2
Operating system
Linux mint
Install method
No response
Model
kimi code 2.5
Provider / routing chain
feishu -> openclaw -> kimi-coding
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response