Mori docs
Slash commands
A / in the composer opens Mori's commands: quick actions that answer right where you typed them, in the thread, under the command.
How commands work
Type / at the start of the composer and a menu opens with every command this surface has. Keep typing to narrow it, use the arrow keys to move, and Enter or Tab to pick. A command answers with a line in the thread, under the command.
Most commands are local and cost nothing: they open a panel, change a setting or report where things stand. A few start real model work by design: /learn, /captain, /crew, /workflow, /retry, /review and /init with a folder bound.
A /word that is not a command is answered locally too, with the nearest real one ("No command /models. Did you mean /model?"); press Enter twice to send it as a message instead. A file path that starts with a slash goes through as text.
The thread
/new: start a fresh thread./clear: clear this thread./retry: run your last message again./undo: remove the last exchange./branch [back]: fork this thread;/branch backreturns to the original. The fork starts already summarized./saveand/import: save this thread to a file you can import later, and open a saved file as a new thread./export [md|html] [--redact]: save this thread to Downloads as Markdown or a styled page. Secrets are always scrubbed./sessions <query>: search the full text of every past thread./star: keep this thread forever, never pruned or archived on its own./project: dedicate this thread to a project.
How she works
/model [name]: switch the model for this thread./depth <instant|quick|balanced|deep|max>: how hard Mori thinks. See Mode and depth./stage <build|spark|trance|forge|swarm>: set the mode./mode: response modes (focus, architect, operator, researcher, ghost, nightshift) or one of your own./design: designer mode, with real references, a plan, and a look of its own./game: game engineer mode: the engine read first, its API, and the game crew./autonomy <guided|trusted|commander>: how much Mori may do without asking, when asking is on. Raising it needs the desktop./permissions: the ask mode, and the commands Mori may run here without asking./moa: advisors: other models draft first, at one extra call each per turn./deny: say why you stopped or refused the last action, and Mori learns from it.
Bigger work
/goal: keep working until this holds. See Goals./long: this thread's long task, where it stands, or change it. See Long tasks and helpers./budget: what a job and this thread may spend, and where they stand./workflow: run it as a workflow: fan out, gather sources, check, then report./captain: plan first: a read-only pass writes a spec you approve before the build./crew: do it with a crew: a Captain plans, members build, review and test./review: review the working changes of the bound folder, with findings by severity./init: write AGENTS.md for this folder: how to build, test and work in it./blueprint: set up a routine that runs on its own, like a morning brief./loop: check again every few minutes here until it holds./heartbeat: a standing look every few minutes, with one quiet line when nothing changed.
Knowledge and skills
/skills: browse the skills on this machine./learn <folder | url | topic>: turn a folder, a page, a topic, or the last task into a new skill. Covered below./graph: the brain as a shape: hubs, orphans, and links that point at nothing.
Where things stand
/usage: context usage: tokens, cost, and what is filling the window. See Context and usage./compress: fold older turns into a summary to free up context./cost: what the last turn spent: round trips, cache, and any wasted ones./status: whether a task is running right now./task: the current task: its objective and recent steps./help: every command.
The app
/theme <dark|light>: switch the theme in place./voice <on|off>: speak replies aloud, or stop./look: switch the layout: rail, tabs, thread list, chips./focus: one thread, nothing else./settings [section],/config: open Settings, or one part of it (/settings voice)./providers,/mcp: open Providers or MCP./pair: bot pairing on Discord or Telegram: codes, approvals and revokes.
/learn: teaching a skill on the spot
/learn turns what you give it into a skill:
/learnalone: Mori looks back at what you just did together and writes the procedure that worked, not a transcript./learn <folder or file>: she maps the folder and reads the key files, so the skill reflects how that project really works./learn <url>: she reads the page before writing./learn <topic>: she researches the topic first.
The skill lands pending on the Skills page until you approve it. If a task is running, /learn asks you to finish it first.
Desktop and bots
One list of commands serves the desktop and the bots on Discord and Telegram, and each surface offers only what it supports. Most commands work in both places. These are desktop only: /pair, /look, /focus, /loop, /heartbeat, /long, /captain, /review, /crew, /init, /config, /permissions, /providers, /mcp and /settings. Pairing a bot makes someone an owner, so only the computer itself can do it, and /autonomy from a bot can only lower the level.