Skip to content

[codex] Fix claw-wall Discord rate limiting#148

Merged
mostlydev merged 1 commit intomasterfrom
issue-147-claw-wall-rate-limit-fix
Apr 13, 2026
Merged

[codex] Fix claw-wall Discord rate limiting#148
mostlydev merged 1 commit intomasterfrom
issue-147-claw-wall-rate-limit-fix

Conversation

@mostlydev
Copy link
Copy Markdown
Owner

Summary

  • select exactly one claw-wall reader token per consumed Discord channel and inject an explicit wall poll interval
  • add typed Discord 429 parsing plus channel-scoped and token-scoped cooldown tracking in claw-wall
  • expand tests for wall selection, poll interval defaults, rate-limit parsing, cooldown behavior, and cooldown expiry

Root Cause

claw-wall was polling duplicate channel/token pairs and retried every non-200 response on the next tick, which could amplify Discord rate limits across multi-bot pods.

Validation

  • go test ./cmd/claw-wall/... -count=1
  • go test ./cmd/claw -run 'TestInjectConversationWall|TestPrepareClawAPI|TestValidateClawAPI' -count=1
  • go test ./... -count=1
  • go vet ./...

Closes #147.

@mostlydev mostlydev merged commit 0c17672 into master Apr 13, 2026
1 check passed
@mostlydev mostlydev deleted the issue-147-claw-wall-rate-limit-fix branch April 13, 2026 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

claw-wall can trigger Discord global rate limits via per-bot channel polling and missing 429 backoff

1 participant