Get Emoji-Decorated Checklists in Claude by Adding One Line to CLAUDE.md

A Reddit user shared a simple CLAUDE.md configuration that makes Claude decorate checklists with emoji icons for status tracking. Drop this single line into your user-level CLAUDE.md (with at least one line of whitespace on either side):
Status-checklist markers. In progress reports that track multiple items (parallel tasks, batch jobs, build steps), prefix each item with a status marker so the list is scannable at a glance. Use this fixed 14-marker set — treat it as closed; don't invent new ones: ✅ done · 🕵️ running · 🛰️ monitoring/polling · ⏳ queued · 🌗 partial/degraded · ❌ failed · 🚫 blocked-by-external · ⏭️ skipped · ⏸️ paused · ❗ needs attention · ⚠️ caution/caveat · ⏰ timer/cron/scheduled · ❓ open question · 🤔 judgment call. This is an explicit opt-in to emoji for status reporting only — not for prose, code, comments, or files. Don't add decorative markers; past ~14 the reader decodes a legend instead of scanning.
Once added, Claude will automatically use these markers in checklists within progress reports. The author explicitly restricts emoji use to status reporting — not for prose, code, comments, or files — and warns against inventing new markers or exceeding the 14-item set, as scanning becomes a legend lookup.
This is useful for developers who want quick visual scanning of batch jobs, build steps, or parallel tasks. No installation or payment required — just a CLAUDE.md edit.
Note: the entire configuration must be on one line with whitespace padding.
📖 Read the full source: r/ClaudeAI
👀 See Also

Why Most Claude Pipeline Failures Trace Back to Prompts, Not Models — and How to Fix with Skills
A Reddit post argues that the root cause of pipeline failures in Claude workflows is treating prompts like skills. The fix: define input contracts, output schemas, and a learnings file — making a skill what you promote to v1.

OpenClaw Implements API Cost Fix and Local Model Tool Improvements
OpenClaw has rolled out key updates addressing API usage costs and improving local model tool integrations, enhancing developer experience and operational efficiency.

How to Cut OpenClaw Agent Costs by 80% with Model Switching
A user tracked token usage for 14 days and found 67% of spend was on tasks where cheap Flash models matched Opus quality. Switching to Flash by default and using /model mid-session cut costs from ~$170 to ~$35/month.

Running OpenClaw Inside Ollama's Docker Container for Simpler Networking
A Reddit user shows how to install OpenClaw inside the official ollama/ollama Docker container so OpenClaw talks to Ollama via localhost, avoiding host.docker.internal and extra networking setup. Trade-off is higher RAM usage.