kiro-discord-bot

Command Reference #

Commands are available as slash commands. Most also have ! text-command equivalents for environments where slash commands are less convenient. Sensitive admin surfaces use private interaction responses where Discord supports ephemeral replies.

Channel Setup and State #

CommandPurpose
/cwdOpen the private project/CWD setup panel. Use this to initialize or move a channel to an allowed project.
/start <cwd>Advanced direct CWD binding. Prefer /cwd for normal setup.
/statusShow agent state, queue length, context use, session ID, and uptime.
/doctorRun deployment, permission, and ACP diagnostics for the current target.
/resetRestart the current channel or thread agent.
/clearClear conversation history for the current target.
/compactAsk the active engine to compact conversation context where supported.

Work Control #

CommandPurpose
/cancelAsk the current ACP session to cancel the active task.
/interruptSoft-cancel first, then interrupt the process group if the same task remains stuck.
/pauseSwitch the current target to mention-only mode. In a parent channel, also disables new task threads.
/backRestore full-listen mode and new task threads for the parent channel or current thread.
`/thread [onoff]`Show or set whether future parent-channel tasks create Discord threads.
`/silent [onoff]`Control compact vs detailed tool output visibility.

Model and Agent Mode #

CommandPurpose
/modelShow the current model.
/model <model-id>Switch the model for the current channel/thread agent. Kiro can use its fallback model list; OMP validates model IDs from the active ACP session.
/modelsList available models. Kiro can fall back to kiro-cli; OMP requires the channel/thread agent to be running because models come from ACP session/new.
/agentList available modes for the current channel/thread agent.
/agent <mode-id>Switch agent mode, such as planner/guide modes or OMP modes advertised by the active ACP session.
/engineShow the current agent engine (kiro/omp) and which engines are enabled.
`/engine <kiro\omp>`Switch the engine for this channel/thread (only engines listed in AGENT_ENGINES_ENABLED). Starts a fresh session on the new engine; recent conversation context is replayed.

Memory and Steering #

CommandPurpose
/memoryAdd, list, remove, or clear persistent Discord-native memory rules.
/flashmemoryManage session-scoped emphasis rules.
`/steering <statuscreateedit>`Manage shared AGENTS.md guidance for the current project.

If a memory rule is visible in /memory list, it affects future turns. To retire stale persistent guidance completely, remove it, then run /clear and /reset.

See Daily Workflows for the operational difference between memory, flash memory, steering, and session cleanup.

MCP and Admin #

CommandPurpose
/mcp statusShow catalog and current channel policy status.
/mcp enable / /mcp disableEnable or disable a server at channel scope.
/mcp manageOpen the private MCP policy panel, scan tools, and manage tool allowlists.
/audit [limit]Privately inspect recent audit events for the current channel or thread.
/usage [user]Show agent usage for today, week, and month-to-date, including credits or USD cost when the engine reports metering metadata.

Use slash /audit for audit data. Text !audit is intentionally not supported for audit rows because Discord cannot make those replies private.

See Audit, Usage, and Privacy for how audit rows, audit prompt investigations, and usage attribution work.

Scheduling #

CommandPurpose
/cronCreate a recurring scheduled task through a form.
/cron-prompt <description>Create a scheduled task from natural language.
/cron-listList scheduled tasks with management buttons.
/cron-run <name>Run a scheduled task manually.
/remind <time> <content>Create a one-time reminder that tags the requester when due.

Scheduling commands must be run in the parent channel. Cron agents use the channel's current CWD at execution time.

See Cron and Reminders for scheduling scope, MCP-created jobs, and owner expectations.

Thread-only Helpers #

Inside a Discord thread, the same slash commands usually target the thread agent when that is least surprising: /status, /reset, /cancel, /interrupt, /compact, /clear, and /model. !close closes the current thread agent, and !close-thread <thread_id> can close an inactive thread agent from the parent channel scope.