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

Check for Unused Codex Reset Credits Across Multiple ChatGPT Accounts via OpenClaw
One user found rate-limit reset credits expiring on a second OAuth account. Agent scanned both, found 6 total unused. Redeemed one to clear cooldown in under a minute. Pitfalls include undocumented endpoint and skill discovery issues.

Spent $850 on OpenClaw in One Month? Fix Your Architecture, Not Your Model
A developer burned $850 in a month on OpenClaw multi-agent setup — with $350 gone in a single day. The fix wasn't a cheaper model — it was system design: strict context pruning, session resets, n8n for non-reasoning tasks, and a routing tier for cheap vs. strong models.

Multi-Agent Orchestration in OpenClaw: Centralize Rules, Spawn Sub-Agents
An OpenClaw user describes moving from duplicated workspace instructions to a single main agent that spawns sub-agents, enforcing architectural rules (e.g., persist structured data as .JSON) across all agent workspaces.

10 Practical Tips for Using Claude Code from Reddit User
A Reddit user shares specific techniques for Claude Code including using /effort high with 'ultrathink' for extended thinking, creating isolated conversation branches with /fork, and setting up custom hooks in .claude/settings.json.