Usage and Limits
Limits exist at multiple layers. Disabling one cooldown does not disable Discord rate limits, provider budgets or service admission.
| Surface | Source-reviewed constraint |
|---|---|
| Ask | 8 requests per user per 60 seconds on that path |
| Image generation | One generation per hour per user |
| AI-channel cooldown | Integer 0–3,600 seconds; zero disables only that cooldown |
| AI reminder scheduling | 5 seconds to 1 year ahead; prompt at most 2,000 characters |
| Timeout duration | Capped at Discord’s 28-day maximum |
| Media video download | Registered path advertises up to 300 MiB; additional runtime caps apply |
| Voice playback | One voice connection per server; playback across channels is serialized |
No invented tiers
Section titled “No invented tiers”This edition does not advertise a subscription, premium entitlement or unlimited quota that has not been established in the product. Provider credits and operational policies may still restrict use. The exact command page lists any reviewed command-specific constraints.
When a limit is reached
Section titled “When a limit is reached”Read the returned wait time or availability error. Wait instead of repeatedly submitting. A failed external operation may have an uncertain outcome; inspect the state before replaying a mutation. Changing a personal thinking setting can change requested provider behavior but cannot bypass metering.