AI Chatbot
Configure a channel-based AI companion with vision support, bounded memory, usage limits, and safety controls.
How it works
The AI Chatbot is separate from @someone. It responds when a message starts with an Airwavy mention or when a member posts in the configured chatbot channel, then keeps short-lived conversation context for that member in that server.
Before you start
- Choose a public or staff channel where generated responses are appropriate and publish clear community rules for AI use.
- Do not submit secrets, private credentials, confidential documents, or sensitive personal data to the chatbot.
Configure it
- Open AI Chatbot in the dashboard and enable it.
- Choose the dedicated chatbot channel and a preset personality or eligible custom style.
- Save, then either start a message with an Airwavy mention or post text in the configured channel using non-sensitive test content.
Start a conversation
- Start a message with Airwavy's Discord mention in a server text channel, or send a non-empty message in the configured chatbot channel.
- A prompt can include text and an image attachment for the chatbot to look at and describe or answer questions about.
- Messages from bots and webhooks are ignored.
- A mention elsewhere in the message does not start the chatbot; put the Airwavy mention first.
Personalities and memory
- Preset styles include Airwavy, chill, comedian, storyteller, zen, tech, and fitness.
- Eligible premium servers can provide bounded custom style text, but it cannot override Airwavy's identity or core safety rules.
- Conversation history stores at most 20 user-and-assistant messages, roughly ten exchanges, for each member and server.
- Inactive conversation history expires after 30 minutes, and reaching the history bound starts a fresh context.
- /resetmemory clears the command user's current conversation context in that server.
Vision (image understanding)
Attach an image to a message that starts a conversation, and ask about it naturally — describe it, read text in it, or answer a question about what's shown.
- The chatbot reads and understands attached images; it does not generate new ones.
- Use only images you have the right to share, and avoid private or identifying material.
- A request with an unsupported or unreadable attachment falls back to a normal text reply.
Usage limits
- Free access uses a 10-second per-member cooldown, up to 15 prompts per member and 300 per server each hour.
- Premium uses a 3-second per-member cooldown, up to 200 prompts per member and 5,000 per server each hour.
- A displayed upstream retry period or temporary service-unavailable response can pause requests independently of these plan limits.
Safety, privacy, and accuracy
- Generated mentions are neutralized so the chatbot does not unexpectedly ping members or roles.
- Airwavy applies fixed safety instructions and an output check for high-severity harmful instructions; blocked or unavailable output may return a refusal or service message.
- Long replies that do not fit a Discord message can be delivered as a text attachment.
- AI output can be inaccurate or incomplete. Verify important information with an authoritative source and never use it as the sole basis for high-stakes decisions.
- Prompts, attached images, and generated replies may be processed by configured AI service providers; do not treat the chatbot as private storage.
Expected result
- An eligible text message or supported image attachment receives a generated response.
- Conversation context remains scoped to the member and server, expires after inactivity, and can be cleared with /resetmemory.
Common errors
The chatbot does not respond
Check that the feature is enabled, the message starts with Airwavy's mention or is in the configured chatbot channel, and the message contains text or an image. Then wait for any displayed cooldown or service retry period.
Saved changes do not take effect
Reload the feature page and confirm the saved values. Then verify that the selected Discord channel or role still exists and that Airwavy can access it.
Discord reports missing permissions
Check the permission on both the server role and the target channel. Channel overwrites and role hierarchy can deny an action even when the server-level permission is present.