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

Treating Agent Runs as Review Packets: A Practical Pattern for Claude Code & Codex
A developer shares how producing a structured folder per agent run (research, drafts, evals, approval packet, metrics, memory) makes failures visible and iterations faster.

Anthropic's undocumented OAuth rate limit pool requires Claude Code system prompt
When using Anthropic OAuth tokens, the API routes requests to the Claude Code rate limit pool based on whether your system prompt identifies as Claude Code. Adding "You are Claude Code, Anthropic's official CLI for Claude." to your system prompt resolves mysterious 429 errors.

Claude Code token audit reveals hidden costs from default tool loading
A developer analyzed 926 Claude Code sessions and found 45,000 tokens loaded at session start, with 20,000 tokens coming from system tool schema definitions. Enabling the ENABLE_TOOL_SEARCH setting reduced starting context from 45k to 20k tokens, saving 14,000 tokens per turn.

Three Overlooked Bottlenecks in AI Agent Workflows: Ingestion, Context Management, and Model Routing
A deep dive into the three layers often skipped when optimizing AI agents: clean input ingestion, context window management across steps, and task-appropriate model routing. Practical fixes include using structured parsing, summarized step outputs, typed schemas, and matching models to task complexity.