Slash commands
Slash commands
Slash commands are shortcuts you type directly in the composer. They let you perform common actions — starting a new session, changing settings, clearing the screen — without leaving the keyboard.
[SCREENSHOT: Slash command menu open in the composer showing a list of available commands with descriptions]
Using slash commands
Type / at the very beginning of a message. A command menu appears above the composer listing all available commands and a short description of each. Continue typing to filter the list. Use the arrow keys to move between entries and press Enter to select one, or click a command directly.
The menu dismisses if you press Escape or delete the / character. If the selected command opens a dialog or panel, the composer text is cleared automatically.
Available commands
| Command | What it does |
|---|---|
/new | Start a new chat session. Navigates to a fresh session without closing the current one. |
/reset | Same as /new — start a fresh conversation in a new session. |
/clear | Clear the visible message history in the current session and start fresh. |
/stop | Stop the running agent immediately. Equivalent to clicking the Stop button. Cancels the active stream and marks any in-flight message as sent. |
/title <name> | Rename the current session. The name is set immediately and persisted to the gateway. Example: /title Project Alpha. |
/reasoning <level> | Change the reasoning effort for the current session. Valid levels: off, low, adaptive. Example: /reasoning off. |
/model | Open the model selector to view or change the active model. |
/save | Save the current conversation. |
/skills | Browse and manage installed skills. |
/plugins | List installed plugins and their status. |
/mcp | Open the MCP server management panel. |
How slash commands are handled
Client-side commands (/new, /reset, /clear, /stop, /title, /reasoning, /model, /save, /skills, /plugins, /mcp) are intercepted by the chat screen before the message is sent to the agent. The text never reaches the gateway.
Custom user-defined commands (created on the Commands page) are expanded client-side: the stored prompt template is substituted and sent to the model as a normal message.
Commands that are not matched client-side are passed through as plain text to the model, so you can still type /something-custom and have the model respond to it as a regular message.
Common issues
The menu does not appear when I type / — Make sure the / is the very first character in the composer. Leading spaces prevent the menu from opening.
A command opens the wrong panel — /model and /skin dispatch custom browser events that the settings panel listens for. If the panel does not respond, try reloading the page.
I want to send a literal / message — Type your slash text as normal and wait for the menu to appear, then press Escape to dismiss it, then continue typing and send. Alternatively, start the message with any non-slash character and add the / later.