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
MiniMax M2.7 Model Released with Improved Coding Performance
MiniMax has released M2.7, an AI model that scores 56% on SWE-Pro coding benchmarks and includes self-optimization capabilities. The model maintains pricing at $0.30 per million input tokens.
Mozilla's State of Open Source AI: 3% Performance Gap, 50x Cost Reduction, 79% Developer Adoption
Mozilla's first State of Open Source AI report reveals open models now trail closed systems by just 3% in performance, cost up to 50x less, and are used by 79% of developers — but capture only 4% of revenue.
The "I don't know, Claude wrote this" pandemic: When cognitive surrender replaces code ownership
Engineers defer architectural decisions to Claude, then can't explain the PR. Addy Osmani calls it 'cognitive surrender' — AI's output becomes yours without review.
Claude 4.6 Opus Can Reproduce Linux's list.h From Minimal Input
A user demonstrated that Claude 4.6 Opus can generate a near-identical copy of Linux's list.h header file when given the first 43 lines as input with temperature set to 0, raising questions about GPL licensing implications for AI models trained on open-source code.