Overview
Discord integration allows Praxos to participate in your servers, channels, and direct messages.Features
- Server and channel messaging
- Direct message support
- Rich embeds and formatting
- File attachments
- Thread support
- Slash commands
- Role-based permissions
Setup
1. Create Discord Application
- Go to Discord Developer Portal
- Click “New Application”
- Name your application (e.g., “Praxos”)
- Navigate to “Bot” section
- Click “Add Bot”
- Copy the bot token
2. Configure Bot Permissions
Required permissions:- Read Messages/View Channels
- Send Messages
- Send Messages in Threads
- Embed Links
- Attach Files
- Read Message History
- Add Reactions
3. Configure Praxos
Add to your.env file:
4. Invite Bot to Server
- Go to OAuth2 > URL Generator in Developer Portal
- Select scopes:
bot,applications.commands - Select permissions from step 2
- Copy generated URL
- Open URL and select server to add bot
5. Start Using
- Direct Messages: Send DM to bot
- Channel Messages: Mention bot using
@Praxos - Slash Commands: Use
/askor other configured commands
Bot Commands
| Command | Description |
|---|---|
/ask [question] | Ask Praxos a question |
/summarize | Summarize recent channel messages |
/remind [time] [message] | Set a reminder |
/help | Show available commands |
Advanced Features
Slash Commands
Configure custom slash commands:Embeds
Praxos sends rich embeds for better formatting:Thread Support
Praxos can create and respond in threads:- Automatic thread creation for long conversations
- Context maintained within threads
- Clean channel organization
Role-Based Access
Configure which roles can interact with Praxos:- Admin-only commands
- Channel-specific permissions
- User-level restrictions
Configuration
Environment Variables
Server Settings
Configure per-server:- Active channels
- Command prefix
- Response behavior
- Notification preferences
Troubleshooting
Bot Appears Offline
- Check token is correct
- Verify intents are enabled in Developer Portal
- Check bot has proper permissions
Commands Not Working
- Ensure bot has “Use Application Commands” permission
- Re-sync slash commands
- Check bot role hierarchy