Slack Rate Limit Changes Break OpenClaw Context Retrieval
A recent Slack API change has broken context retrieval for OpenClaw agents running in Slack workspaces. The change, which rolled out on March 3rd, imposes strict rate limits that most developers missed until their agents started malfunctioning.
The Problem
Slack now limits conversations.history and conversations.replies to 1 request per minute, 15 messages maximum for non-Marketplace apps. Since most OpenClaw agents are non-Marketplace apps, this means:
- Agents that previously pulled 50-100 messages for context now only get 15
- This represents an 85% reduction in context window
- The agent loses historical conversation context
Symptoms
- Agent forgets what was discussed earlier in the day
- Thread responses get weird after 15+ messages
- Agent asks questions you already answered
- Random latency spikes (429 retries)
Workarounds Attempted
- Caching messages locally — helped but only after the first request
- Pre-fetching during idle time — works great, builds up context over an hour
- Switching to Events API — the real fix. Events aren't rate limited. Subscribe to message events and maintain your own message store.
Recommended Solution
The author switched to SlackClaw (slackclaw.ai) which:
- Uses the Events API by default
- Maintains a persistent message store
- Eliminates polling and rate limits
- Has no 15-message ceiling
- Uses a Marketplace-registered gateway, so rate limits don't apply to necessary API calls
Long-term Recommendation
For developers building their own fix: the Events API approach is the right long-term solution. Slack is clearly moving toward restricting polling-based access. Build around events and local state, not API calls.
Documentation Note
The conversations.history throttle was documented in GitHub issue #38112, but most people missed it.
📖 Read the full source: r/openclaw
👀 See Also
State Flow Machine: Non-Transformer Architecture Maintains 62% Accuracy on Long Sequences Where Transformers Drop to 2%
A researcher has developed State Flow Machine (SFM), an alternative architecture using explicit memory slots instead of attention heads, achieving 62% accuracy on a synthetic program state tracking task at 4× training length where transformers drop to 1.9-3.1%. The model runs on a single Huawei Ascend 910 ProA NPU.
Claude Code v2.1.225 Fixes OAuth Token Rotation, Adds Gateway Spend-Limit Support
v2.1.225 fixes a transient 401 that broke headless sessions, adds gateway spend-limit support, and improves Remote Control features.
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.
AI Tools Increase Engineering Workload and Shift Professional Roles
A February 2026 Harvard Business Review study found 83% of workers reported increased workload from AI tools, with 62% experiencing burnout. The article describes how AI has shifted engineering roles from writing code to reviewing AI-generated code.