Hide OpenClaw Exec Lines in Telegram Chat: One-Command Fix

If you use OpenClaw via Telegram, you've likely seen raw ⚙️ Exec: lines cluttering your chat after every agent command. This happens because the config keys streaming.preview.toolProgress and streaming.progress.toolProgress default to true, streaming all tool progress — including exec details — into Telegram messages. These keys are not written to openclaw.json by default, so they must be added manually.
The Fix (One Command)
Run the following Python command to automatically back up your config and write the required keys:
python3 -c "
import json, os, shutil
p = os.path.expanduser('~/.openclaw/openclaw.json')
shutil.copy(p, p + '.backup')
with open(p) as f: c = json.load(f)
c.setdefault('channels', {}).setdefault('telegram', {})['streaming'] = {
'preview': {'toolProgress': False},
'progress': {'toolProgress': False}
}
with open(p, 'w') as f: json.dump(c, f, indent=2)
print('Done. Restart OpenClaw gateway.')
"Validate JSON
After the change, verify your config is valid JSON:
node -e "JSON.parse(require('fs').readFileSync(require('os').homedir()+'/.openclaw/openclaw.json','utf8')); console.log('JSON OK')"Restart Gateway
Kill the running OpenClaw gateway and start it again (replace <YOUR_PORT> with your actual port):
pkill -f "openclaw.*gateway" && sleep 2 && openclaw gateway --port <YOUR_PORT> & bg %1Note: after the &, the process may hang in a Suspended state. Running bg %1 resumes it.
Relevant Config Keys
streaming.preview.toolProgress– set tofalsestreaming.progress.toolProgress– set tofalse
The original blog post and videos (English and German) are linked in the source below.
📖 Read the full source: r/openclaw
👀 See Also

Claude Code Token Waste Fix: Disable Attribution Header for Better Cache Hits
Setting CLAUDE_CODE_ATTRIBUTION_HEADER=false in your shell configuration can improve Claude Code's cross-session prompt cache hit rate from 48% to 99.98%, reducing system prompt processing costs by 7x per session.

Claude Code Visual: Practical Notes on Hooks, Subagents, MCP, and CLAUDE.md
A developer shares practical experience using Claude Code Visual, covering MCP hook syntax, CLAUDE.md for project context, subagent delegation patterns, and the /loop command for recurring tasks.

Field Report: Qwen 3.6 27B on an M2 MacBook Pro (32GB) – Painfully Slow but Smart Output
Running Qwen 3.6 27B IQ4_XS on an M2 MacBook Pro with 32GB RAM yields 7.9 t/s initially, degrading to 3.1 t/s at 52k context. Code quality impresses, but memory bandwidth is the bottleneck.

Using project narratives to manage memory in large OpenClaw projects
A developer shares a process where after each major milestone, they spawn a separate OpenClaw worker to analyze the codebase and write a 'project narrative' document, which helps identify broken pipelines, redundancies, and missing pieces that the main worker might overlook.