Claude Code 2.1.80 adds rate limit visibility, MCP push messaging, and memory improvements
Claude Code 2.1.80 is a release that adds several practical features for developers using the AI coding assistant, focusing on visibility, configuration, and performance improvements.
Key features in 2.1.80
- Rate limits visible in statusline: You can now see rate limit status directly in the interface instead of guessing when you're being throttled.
- Inline plugin config via settings.json: Configure MCP plugins directly in the settings.json file without editing separate configuration files.
- --channels flag (research preview): Enables MCP push messaging for server-to-client notifications.
- Per-command effort overrides: Set different effort levels for specific slash commands.
- 80 MB saved on startup: Memory reduction that's noticeable when running multiple sessions.
- Fixed --resume dropping parallel tool results: Resolves an issue where parallel tool results were lost when using the --resume flag.
The release notes mention that the --channels flag is currently in research preview, indicating it's an experimental feature for testing MCP push messaging functionality.
📖 Read the full source: r/ClaudeAI
👀 See Also
Stripe's Minions: Enhancing Developer Productivity with One-Shot End-to-End Coding Agents
Stripe Minions are one-shot, end-to-end coding agents designed to boost developer productivity by automating complex tasks within the Stripe ecosystem.
MCP Works with Local Models Too — Server Ecosystem Maturing Fast
MCP isn't Claude-only. Local models with function calling work fine. Open Web UI now has basic MCP client. 13B+ models handle multi-step tools best.
SDNY Ruling Denies Attorney-Client Privilege for AI Chat Communications
Judge Rakoff ruled in U.S. v. Heppner that communications with AI tools like ChatGPT do not qualify for attorney-client privilege, requiring disclosure of all AI-generated legal work. The court found AI lacks the human confidentiality required for privilege protection.
OpenClaw Early User Reports Telegram Issues, Agent Profile Hardcoding, and Session Reset Problems
A user's first three days with OpenClaw revealed several practical challenges: Telegram responses disappearing, agent profiles hardcoded to 'messaging' in source code, and Wacli becoming unavailable after session resets. The user ran micro tests on Docker, connected Telegram and Wacli, and set up a heartbeat.