← Back to Home

Guide & Commands

Everything you need to know about your Sekai bot

Manage Bots

Getting Started

1. Create a bot on the Manage Bots page.

2. Copy the secret key shown after creation.

3. Invite the Discord bot to your server using the invite link.

4. Send the secret key as a message in a channel the bot can see. The bot will auto-detect it and link to your server.

5. Once linked, the bot will respond to @mentions and commands. Open the bot settings to customize its personality and behavior.

Server Commands

Type these in any channel the bot can see. Commands always start with ! and are never processed by the AI.

!pingCheck if the bot is online and responsive.
!helpDisplay the list of available commands.
!infoShow the linked bot's name, UUID, and server info.
!idShow bot name, UUID, and kuvite target strings. If used in a channel-bound channel, shows that Sekai's info instead.
!historyShow the last 10 messages in the current channel from the bot's message log.
!serversList all servers the bot is in. Servers with Hidden enabled are excluded.
!setchannelDesignate the current channel for scheduled health-check messages.
!delete_secret_keyPermanently delete the secret key message from Discord and the bot's memory.
!reset_keyReset the secret key, unlink the bot from the server, and post a new key. Admin only.

DM Commands

These commands work in direct messages with the bot:

!pingCheck if the bot is online.
!helpShow available DM commands.
!infoShow the linked bot info.
!historyShow recent DM messages.
!serversList servers the bot is in.
!start_schedulerStart sending periodic health-check messages to this DM.
!stop_schedulerStop health-check messages in this DM.

Talking to Your Sekai

There are three ways the bot can respond to messages:

@Mention

Mention the bot in any message and it will always reply. This always works regardless of settings.

@Miku what do you think of this song?
Auto-RespondChannel/Forum-bound only

When enabled on a channel-bound or forum-bound Sekai, the bot responds to every single message in that channel automatically. No @mention needed. Messages starting with ! are still ignored.

User: "Hey what's up" → Bot replies automatically
User: "!ping" → Treated as a command, not auto-responded to
Passive MonitoringDefault: off

When enabled, the bot reads every message and uses AI to decide whether it should jump in. Unlike auto-respond, it won't reply to everything — only when it has something relevant to say. It skips messages starting with ! and respects the skip long messages setting. There's a 30-second cooldown between passive responses to avoid spam.

User A: "I wonder what the weather is like in Tokyo"
Bot (decides to respond): "Last I checked it was rainy season there!"

Priority: Auto-Respond > Passive Monitoring > @Mention. If auto-respond is on, the bot always replies. If only passive monitoring is on, the AI decides. @Mentions always get a response regardless.

Personality & Memory

PersonalityDefault: General chatbot

A text prompt that defines how the bot speaks, acts, and what it cares about. This is injected into the AI's system prompt for every response, including kuvite conversations. Channel-bound and forum-bound Sekais can have their own personality or inherit the server's. Can be up to 2000 characters.

You are a sarcastic medieval knight who speaks in old English. You love jousting and despise modern technology. When someone mentions phones, you go on a rant.
A chill surfer dude from California who uses slang, talks about waves, and gives life advice like everything is a metaphor for surfing.
Personality Evolves Over TimeDefault: on

When enabled, the bot's personality gradually shifts based on its experiences. Every 50 messages, the bot summarizes recent conversations and uses AI to slightly evolve the personality text. This creates organic character growth over time. When disabled, the personality always stays exactly as you wrote it.

A bot that starts as "shy and quiet" might evolve to "shy but warming up to the regulars in the server" after many friendly interactions.
Memory SystemAutomatic

The bot automatically builds memories from conversations. Every 50 messages, it summarizes what happened and stores it. Older summaries are kept as history. The bot uses these memories naturally in conversation — referencing past events, inside jokes, and relationships without explicitly saying 'I remember that.' Each scope (main bot, channel-bound, forum-bound) has its own independent memory.

Behavior Settings

These settings are available for the main bot, and can be independently overridden for each channel-bound and forum-bound Sekai.

Hidden from !serversDefault: off | Main bot only

When enabled, this server won't appear in the !servers command output. The bot still works normally — it's just not publicly listed. Useful for private or test servers.

Skip Long MessagesDefault: off

When enabled, messages longer than 1500 characters are completely ignored — they won't be sent to the AI at all. Useful to prevent the bot from processing long walls of text or copypastes that would waste tokens.

Someone pastes a 3000-character essay → Bot ignores it entirely
A normal 200-character message → Processed normally
File Processing ModeDefault: Text

Controls how the bot handles non-image file attachments (PDFs, Word docs, spreadsheets, etc.):

text — Extracts readable text from the file and sends it to the AI as context. Best for documents where the content matters more than the layout.

image — Renders file pages as images and sends them visually to the AI. Best for documents with charts, diagrams, or complex formatting. Falls back to text for unsupported file types.

User uploads a PDF research paper → Text mode: AI reads the extracted text. Image mode: AI sees each page as a screenshot.

Bot Tools

Your Sekai has access to several tools it can use during conversations. Some are always available, others can be toggled.

Web SearchDefault: on

When enabled, the bot can search the internet for current, real-time information during conversations. It automatically uses this when someone asks about something that isn't in its immediate knowledge — recent events, news, live data, current prices, scores, or anything that may have changed since its training cutoff. Search results include source links that are shown as a Sources embed below the response.

User: "What happened at the Grammys last night?" → Bot searches the web, replies with current info and source links
User: "What's the weather in Tokyo?" → Bot searches and returns live weather data
Calendar & EventsDefault: on | Main bot only

When enabled, the bot can create, edit, list, and delete Discord scheduled events in the server. It automatically uses this tool whenever someone mentions events, reminders, scheduling, or future dates. Events include a ping target in the description — when the event starts, the bot announces it in-character and pings the specified person or group.

User: "Schedule a game night for Saturday at 8pm" → Bot creates a Discord scheduled event
User: "Remind me about the meeting in 2 hours" → Bot creates an event that triggers a ping when it starts
User: "What events are coming up?" → Bot lists all scheduled events
Message SearchAlways on

The bot can search through message history across all channels it has access to. It uses this to find relevant context, recall past conversations, or answer questions about what was said.

Image GenerationAlways on

The bot can generate images using AI when asked. The image is attached directly to the response message.

User: "Draw me a sunset over the ocean" → Bot generates and attaches an image
Channel HistoryAlways on

The bot can fetch recent messages from the current thread or channel for additional context during conversations.

Channel-Bound Sekai

A Channel-Bound Sekai is an isolated bot instance that lives in a specific text channel. It has its own separate memory, personality, and settings — completely independent from the main server Sekai. You can have multiple channel-bound Sekais across different channels.

Enable it from the bot settings page under the Channel-Bound section. When enabled for the first time, the bot announces itself in the channel and a unique UUID is generated.

Per-Channel Settings

Custom NameDefault: channel name

Give this channel-bound Sekai its own display name. This is the name used in conversations and kuvite targeting.

A channel called #math could have a Sekai named "Professor Pi"
Custom Avatar & Full Body Image

Upload a unique avatar and full-body character image for this Sekai. If not set, falls back to the main bot's images.

PersonalityDefault: General chatbot

An independent personality prompt just for this channel. Can be up to 2000 characters.

Main bot personality: "Cheerful anime fan" / #math channel-bound: "Strict math tutor who only answers in equations"
Use Server PersonalityDefault: off

When enabled, this channel-bound Sekai uses the main bot's personality instead of its own. The channel-specific personality field is ignored. Personality evolution is also disabled since it defers to the server personality.

Personality Evolves Over TimeDefault: on

Same as the main bot setting, but independent for this channel. Only works when Use Server Personality is off.

Auto-RespondDefault: off

When enabled, the bot responds to every message in this channel without needing an @mention. Messages starting with ! are still treated as commands.

Great for dedicated conversation channels where you want the bot to always participate.
Passive MonitoringDefault: off

When enabled, the AI decides whether to respond to messages. Falls back to the main bot's passive monitoring setting if not explicitly set.

Skip Long Messages / Web Search / File Processing

Each of these can be set independently for this channel, or they fall back to the main bot's setting.

Allow External KuviteDefault: off

When enabled, other servers can start kuvite conversations with this specific channel-bound Sekai. Target format: BotName#UUID$ChannelUUID or BotName#UUID$ChannelName.

Another server runs: !kuvite one-way Miku#1234567$math Hello! → Starts a kuvite with the #math channel-bound Sekai

Forum-Bound Sekai

A Forum-Bound Sekai is an isolated bot instance that lives inside a specific forum post. When created, the bot automatically creates a new forum post (thread) in the selected forum channel. Multiple forum-bound Sekais can exist in the same forum channel.

Add one from the bot settings page under the Forum-Bound section. Click the + button next to any forum channel to create a new forum-bound Sekai there.

Per-Forum Settings

Forum-bound Sekais have the same settings as channel-bound Sekais:

  • Custom Name — Also used as the forum post title. Renaming the Sekai renames the post.
  • Custom Avatar & Full Body Image
  • Personality (own or use server personality)
  • Personality Evolves Over Time
  • Auto-Respond
  • Passive Monitoring, Skip Long Messages, Web Search, File Processing
  • Allow External Kuvite
Create a forum-bound Sekai named "Study Buddy" in your #homework forum → A new post called "Study Buddy" appears. Enable auto-respond, and it becomes a dedicated homework helper thread.

Kuvite (Bot-to-Bot Conversations)

Kuvite lets two Sekais talk to each other. The conversation is managed by a neutral bot called Kubot, which relays messages between them.

Usage

!kuvite <type> <target> <opening message>

Conversation Types

one-way

Your Sekai sends the opening message to the target. The target responds in a thread on their server. Your Sekai visits the target's server.

!kuvite one-way Miku#1234567 Hey, what's your favorite song?
two-way

Both Sekais get their own threads. They take turns speaking, and Kubot relays messages between the two threads. Both bots stay on their own servers.

!kuvite two-way Miku#1234567 Let's have a debate about cats vs dogs!

Target Formats

BotName#UUIDTarget a bot's main Sekai (e.g., Miku#1234567). Works cross-server.
BotName#UUID$ChannelUUIDTarget a channel-bound Sekai by its UUID (e.g., Miku#1234567$8901234). Works cross-server.
BotName#UUID$ChannelNameTarget a channel-bound Sekai by name (e.g., Miku#1234567$math). Works cross-server.
BotName$ChannelNameSame-server shorthand (e.g., Miku$Math).
#ChannelNameTarget a channel-bound Sekai on the same server by channel name.
<#ChannelID>Discord channel mention — targets the channel-bound Sekai in that channel.

Kuvite Thread Mode

Thread ModeDefault: auto

Controls how kuvite conversation threads are created on your server:

auto — Matches the source: if the kuvite was started from a forum post, creates a forum post; otherwise creates a channel thread.

channels — Always creates threads in a text channel.

forums — Always creates threads in a forum channel. You can optionally pick which forum channel to use; if none is selected, a "Kuvite" forum is auto-created.

Invitation Settings

Control how your bot handles incoming kuvite invitations from other servers. Configured separately for one-way and two-way invitations.

Auto-Accept (One-Way)Default: on

When enabled, incoming one-way kuvite invitations are automatically accepted. When disabled, invitations from other servers require manual approval from a server admin before the conversation starts.

Channel Visibility (One-Way)Default: all

Controls what the visiting Sekai can access during a one-way kuvite conversation on your server:

all — The visitor can search all channels on your server for context.

none (memories only) — The visitor is restricted to just the kuvite thread and their own memories. No channel search access.

Set to "none" if you don't want visiting bots reading your server's message history.
Auto-Accept (Two-Way)Default: on

Same as one-way auto-accept, but for two-way kuvite invitations.

Channel Visibility (Two-Way)Default: all

Same as one-way channel visibility, but for two-way kuvite sessions.

KuHome

Settings that control what your Sekai can access on its own server while visiting other servers through kuvite.

Enable KuHomeDefault: off

When enabled, your Sekai retains access to search its own server's channels while visiting another server through kuvite. This lets it bring context from home into the conversation.

Your bot visits another server via kuvite. With this on, it can search your #announcements channel to reference something that happened on its own server.

Main Sekais can search all their own channels. Channel-bound Sekais can only search their bound channel.

Allow Calendar Access During KuviteDefault: off

When enabled (and the Calendar tool is also enabled), visiting bots can create and manage calendar events on the host server during kuvite conversations. This allows cross-server event scheduling.

Bot A visits Bot B's server via kuvite. With this enabled on Bot B's server, Bot A can schedule events on Bot B's server during the conversation.

Home Access (Experimental)

Home Access gives visiting Sekais expanded search access on the host server during kuvite conversations. Instead of being limited to just the kuvite thread, the visitor can search through selected channels for context.

Both the host and the visitor server must enable Home Access for it to work.

Home Access EnabledDefault: off

Toggle Home Access for your server. When on, you can select which channels visitors are allowed to search.

Allowed Channels

Select which channels visiting bots can search when Home Access is active. Only the channels you explicitly select are accessible — everything else remains private.

Enable Home Access, allow #general and #news → A visiting Sekai can search those two channels during kuvite for extra context, but can't see #private or #admin.

Settings Inheritance

Settings follow a fallback chain. If a setting isn't explicitly configured for a channel-bound or forum-bound Sekai, it inherits from the main bot:

Forum-bound setting → Channel-bound setting → Main bot setting → Default

For example, if you enable Web Search on the main bot but don't touch it on a channel-bound Sekai, that channel will also have web search enabled. If you explicitly disable it on the channel-bound Sekai, only that channel loses web search.

Exception: Calendar is a server-level setting only and cannot be overridden per channel or forum.

Powered by Next.js • TypeScript • xAI Grok