Claude users report faster sessions by requesting markdown instead of Word documents

A Claude user on Reddit shared a practical optimization: switching from requesting Word documents to asking for markdown output resulted in noticeably faster sessions and reduced token consumption.
What's happening under the hood
When users ask Claude to "write me a document about X" and specify .docx format, the AI performs several steps:
- Spins up a code execution environment
- Imports python-docx library
- Builds the document programmatically
- Applies styles and formatting
- Runs the script to generate the file
This entire process happens just to create the container format, while Claude's native output is already markdown.
The performance impact
The user reported immediate improvements after switching to markdown requests:
- Faster response times
- Fewer tokens burned on format conversion
- Reduced failures when python-docx encounters formatting issues
- Better compatibility when feeding output back to the AI for editing or expansion
Markdown is Claude's native format, so when you need to edit or expand content later, the AI can work directly with the markdown. With .docx files, the AI must first parse the document apart before processing, effectively paying for format conversion twice.
Practical recommendation
The user suggests continuing to request .docx files when you need actual Word documents for clients or systems that require that format. For internal use, reading on screen, or when you'll be processing the content further with AI agents, markdown requests eliminate unnecessary overhead.
This optimization is particularly relevant for developers using AI coding agents who frequently generate project specs, outlines, and documentation. The token savings and speed improvements accumulate quickly with regular use.
📖 Read the full source: r/ClaudeAI
👀 See Also

OpenClaw API Budget Drain: Settings to Change Immediately
OpenClaw's default Heartbeat feature can drain API budgets by checking tasks every 30 minutes and loading full context files, memory, and chat history each time. The source recommends changing Active Hours, using cheaper base models, manually switching to premium models only when needed, and using /new to reset sessions.

OpenClaw Discord proxy fix for REST API timeout issues
A user reports fixing OpenClaw Discord connection issues where WebSocket connects but REST API calls fail with "fetch failed UND_ERR_CONNECT_TIMEOUT" errors. The solution involves creating a proxy-preload.cjs file and setting global undici proxy settings.
![[Update] You Asked for a Secure, 'Always-On' Way to Run OpenClaw Without the VPS Headache. We Built It. Waitlist is Open.](/covers/article-139.jpg?v=3)
[Update] You Asked for a Secure, 'Always-On' Way to Run OpenClaw Without the VPS Headache. We Built It. Waitlist is Open.
OpenClaw announces a new feature that allows users to run their platform securely and continuously without the complexities of VPS. The waitlist is now open for early access.

Browser Agents Ate My API Budget: The Hidden Cost of Observation Loops
Running AI agents on real web tasks? A Reddit user reports that browser observation loops — not the model — are the dominant cost driver. Every click, wait, and observe triggers a round trip, and poor snapshot quality creates a compounding failure spiral that inflates token usage. Isolated browser environments and faster agent execution are key cost-saving measures.