DiscordOS is a Discord bot that turns a server into a state-driven “operating system”. Instead of relying on dozens of slash commands, DiscordOS uses live dashboards (screens), buttons, select menus, modals and threads to manage a server in a structured, observable way.
This project is designed for advanced Discord administrators and developers who want clear visibility, safety, and explainability when managing complex servers.
DiscordOS is built around the concept of STATE.
• The bot maintains an internal state (incidents, processes, security, permissions). • Screens render that state into Discord channels. • Interactions update the state. • The UI refreshes by editing a single message per screen (no spam).
Discord becomes a control panel instead of a chat flood.
- INCIDENT MODE (Start / Update / Resolve)
Incident Mode provides a structured way to handle critical situations.
• Start Incident
- Opens a modal (title, impact, optional on-call mention)
- Creates a dedicated incident thread
- Posts a structured OPEN message with a checklist
• Post Update
- Opens a modal (status update + optional next ETA)
- Posts an UPDATE message in the incident thread
- Updates the incident screen with latest info
• Resolve Incident
- Opens a modal (resolution summary)
- Posts a RESOLVED message
- Archives the incident thread
Use cases: • Production outages • Moderation emergencies • Raids • Staff escalation workflows
- PERMISSION SIMULATOR (EXPLAIN+)
The Permission Simulator answers the real admin question:
“WHY is this allowed or denied?”
It supports: • User or Role target • Channel selection • Action selection (View, Send, Manage Messages, etc.)
Explain+ output shows the full resolution path: • Base permissions from roles • @everyone overwrite • Role overwrites (deny union / allow union) • Member overwrite • Final computed result
This makes Discord permission logic transparent and debuggable.
- PROCESS MANAGER
DiscordOS treats long or structured operations as processes.
• Each process has a state (RUNNING / DONE / FAILED / CANCELED) • Each process can create its own thread • The process screen shows current activity
This is the foundation for future workflow automation.
- EVENT BUS (Operational Logs)
The Event Bus is an internal log stream that shows: • Incident lifecycle events • Permission simulations • Secure mode blocks • Admin actions • Process lifecycle changes
This makes the bot observable and trustworthy.
- SECURE MODE (LOCKDOWN)
Secure Mode is a safety mechanism.
When enabled: • Risky actions are blocked • Read-only actions remain available • All blocked actions are logged
Use Secure Mode during incidents or investigations.
• Screens Channels that display live dashboards by editing a single message.
• Router Central interaction router handling buttons, selects, and modals.
• Managers IncidentManager, ProcessManager, SecurityState, EventBus.
• Render Queue Prevents spam and rate-limit issues by batching UI updates.
• Threads Used as contextual workspaces (incidents, processes).
-
Install dependencies npm install
-
Create environment file Copy .env.example to .env and fill in your values.
-
Run the bot npm run dev
Required permissions: • Manage Channels • Send Messages • Embed Links • Manage Threads
• Replace command spam with state-driven UI • Make admin actions explainable and auditable • Use Discord native features to their full potential • Provide a foundation for future automation and workflows
This project is a prototype architecture. State persistence is currently in-memory and can be extended later using a database such as SQLite or PostgreSQL.
MIT