Claude Code Bug Replaces German Umlauts with ASCII Substitutes

Bug Details and Timeline
Since December 2025, Claude Code and the Claude.ai app have been randomly replacing German umlauts with ASCII substitutes. The affected characters are:
- ä → ae
- ö → oe
- ü → ue
- ß → ss
The bug is reportedly getting progressively worse each day. Even when users explicitly tell Claude Code to use umlauts, the fix only works for about 2 minutes before the system reverts back to ASCII substitutes.
Support Channel Failures
The user has attempted multiple support avenues over 3+ months with no resolution:
- GitHub issue filed December 13, 2025 (https://github.com/anthropics/claude-code/issues/14131) — no Anthropic employee response, only automated bots with wrong labels
- Multiple /feedback and /bug reports
- Multiple Intercom support tickets — all resulting in automated responses or generic login troubleshooting templates unrelated to the issue
- Direct email to [email protected] — same result, generic login template sent twice despite the issue having nothing to do with login
The user is a paying Max subscriber who was promised Priority Support within one US business day, a promise that has been repeatedly broken.
Community Impact
Many other users are reportedly affected by this issue. The original poster encourages others experiencing the same problem to comment on the GitHub issue to increase visibility.
📖 Read the full source: r/ClaudeAI
👀 See Also

DeepSeek-V4 Pro and Flash: 1.6T Parameters, 1M Token Context, Hybrid Attention
DeepSeek-V4-Pro (1.6T params, 49B active) and V4-Flash (284B params, 13B active) support 1M token context. New hybrid attention (CSA + HCA) reduces single-token inference FLOPs to 27% and KV cache to 10% of DeepSeek-V3.2.

Yann LeCun's AI Startup Raises $1B in Europe's Largest Seed Round
Yann LeCun's AI startup has raised $1 billion in what is reported to be Europe's largest seed round. The news was shared on Hacker News with 186 points and 107 comments.

OpenClaw 2026.3.22 Update: Useful Features but Three Critical Issues Require Caution
The OpenClaw 2026.3.22 update introduces useful features like the /btw command, health monitor configurability, Telegram reply fix, and per-agent reasoning defaults, but three open issues (#53158, #53202, #53195) make it risky to deploy immediately without monitoring.

OpenClaw agent spending patterns and lack of spending caps
A developer tracked OpenClaw agent spending over two months and found most agents average $40–$80/month in API and service charges when left unchecked, with spikes occurring on weekends and overnight. The default behavior is unlimited with no built-in spending cap.