Browse guidebook
GuidebookFor server owners

Set up your server

A clear path through AI access, AutoMod, vision, limits, and moderator permissions.

Start with two checks

  1. Check AIRun /ai status. It shows whether the server has approved local AI or a connected provider.
  2. Check AutoModRun /automod status. AutoMod is enabled by default, and this shows its current settings.

If OmniCore is not installed yet, use the installation guide. The server owner is the Discord account that actually owns the server; Administrator permission alone does not unlock owner-only AI and AutoMod controls.

Back to top ↑

Choose how AI works

Local AI

Bot owners can approve local Ollama for your server. Members can mention OmniCore without a server API key.

Your provider key

Run /ai setup for a private one-use setup link. Connect your OpenAI, Anthropic, or Gemini account there. Provider usage may incur charges.

Never post an API key in Discord. After connection, use /ai model to select an available model and /ai usage to review recent use. /ai disconnect removes the stored key. Moderation and basic utilities work without AI access.

Back to top ↑

Enable image recognition

Run /ai vision to review image settings and choose a model that supports vision. You can set a limit from one to three images per request. Members must attach images to the invoking message or directly reply to the exact image message; OmniCore does not search channel history for pictures.

DM vision requires your own connected provider key and an explicit /ai vision dm_enabled:true setting. The user must be the current owner of that server. Provider image requests may incur additional charges.

Back to top ↑

Configure AutoMod

AutoMod starts enabled. A first confirmed violation warns the member; another confirmed violation within 24 hours may trigger a timeout if timeouts are enabled and Discord permits it. Protected staff and server owners can be warned but are not automatically timed out.

Common settings/automod sensitivity level:normal/automod warnings enabled:true/automod timeouts enabled:true/automod timeout level:moderate duration:10m

/automod notifications enabled:true sends owner alerts. /automod diagnostics enabled:true sends bot operators the server, user, and a short flagged-message excerpt. /automod log-channel selects a private fallback channel for owner notices when DMs fail; @everyone must not be able to view it. Use /analytics moderation for trends.

Back to top ↑

Control access and prompts

/ai limitsSet daily usage and concurrency limits.
/ai channel /ai roleRestrict provider AI to selected channels or roles.
/ai thinkingControl local Ollama thinking for server text.
/change_promptAdministrator: change the server-wide local chat prompt.
/delete_memoryAdministrator: delete saved server AI history.

/get_prompt reads the current server prompt; /remove_prompt clears it. These are separate from personal DM prompts. Use /ai settings to inspect provider rules.

Back to top ↑

Commands for moderators

Moderation commands check the caller’s Discord permission. The bot also needs the matching permission and a role above the target for timeouts, kicks, and bans.

/time /untimeModerate Members
/kickKick Members
/ban /unbanBan Members
/purgeManage Messages
/lock /unlockManage Channels; the bot also needs Manage Roles
/set_prefixManage Server

A server owner can also request a timeout by mentioning OmniCore, naming one member, and specifying a duration up to two days. The bot checks permissions separately from the AI model.

Back to top ↑

Bot owners are separate

OmniCore bot owners approve local AI for guilds and review private DM requests. Owning a Discord server does not grant these operator powers. In a private DM, bot owners use /dmaccess pending, /dmaccess approve, /dmaccess deny, and /dmaccess owner_prompt. The bot-owner-only /restart command runs in a server.

For operator help, use the support page. Keep API keys and private messages out of public channels.

Back to top ↑
Next stepNeed to check a command?Open command reference ↗