Slash commands

Slash commands run inside an interactive Veyyon session. Type / in the composer to open the picker. Commands below are the builtin set; extensions may add more.

A command nothing can handle is rejected, not sent to the model. If you mistype a name, or type a command your installed build does not have, you get:

Unknown command "/secrt". Nothing handled it, so it was not sent to the model. Type / to see the
commands this build has, or drop the leading slash to send it as a message.

The refusal states the command and never repeats what followed it, because the tail of a mistyped /secret is a credential. The rule reaches further than one mistyped word: in a terminal the whole argument line of /secret is the credential, whatever it happens to spell, so there is no tail there that is safe to echo back.

A message that merely begins with a filesystem path is prose, not a command, and is sent as usual:

/etc/hosts is broken

The separator decides. A command name is one segment of letters, digits, underscores and hyphens starting with a letter, so anything holding a slash is a path.

Every argument is a plain word

No slash command takes an option. Nothing is spelled with a dash, so there is nothing to look up and nothing to get in the wrong order. A word means something for one of two reasons: the POSITION it sits in, or a CLOSED SET or SHAPE it belongs to.

Plenty of commands take a single argument, listed with them in the tables below. These are the ones with a grammar to state, and each used to spell part of it with dashes:

/mcp add <name> [http|sse] [url <url>] [token <token>] [run <command...>]
/mcp remove <name>
/mcp smithery-search <keyword...> [<limit 1-100>] [semantic]
/ssh add <name> <host> [user <user>] [<port>] [key <keyPath>]
/ssh remove <name>
/stats [<port>]

/secret has its own grammar and its own page: see Secrets.

Position covers every required word, so /mcp remove project removes a server actually named project. Where meaning is taken from a word’s shape instead, the sets provably cannot overlap: on /ssh add a port is digits and nothing else the command reads is, and user and key are the only two keywords, each taking the word after it. A word the command cannot use is rejected rather than ignored, because a word that is silently dropped looks like a setting that was applied.

A spelling that was an option

Each of these commands remembers the option spellings it used to have, and rejects them, stating the plain word that replaced each one:

/ssh add box example.com --port 2222
--port is gone: write the port as a plain integer.
Usage: /ssh add <name> <host> [user <user>] [<port>] [key <keyPath>]

The plain word gets the same answer as the dashed one. /stats port 8080 is rejected the way /stats --port 8080 is, and /mcp add srv project the way /mcp add srv --scope project is, because the operator who types the word an older grammar taught is asking the same question either way and wants the same answer. Which words those are is read from the same table the refusal text comes from, so the two spellings cannot drift apart.

A word that never was an option is rejected more briefly, since there is no replacement to name: Unknown argument: <word>, or Invalid port: <word> where a port was the only thing the command reads.

/mcp smithery-search is the exception, and it is one on purpose: its trailing words are search terms, arbitrary text with no closed set, so a plain project there is a keyword to search for and is searched for. Only the dashed spellings are rejected.

A bare command that has subcommands

Some commands take a subcommand: /account status, /account manager, /usage reset. Typing the command on its own opens a picker listing every subcommand it has, with what each one does. Move with the up and down arrows, click a row, press enter to run it, or press escape to close and run nothing. Choosing a row runs exactly what typing that subcommand runs.

A subcommand that takes an argument, such as /account name <text>, does not run straight away. The picker writes /account name into the composer and leaves the cursor after it, so you type the argument and press enter.

Outside a terminal, in ACP and --print mode, there is no picker to open. A bare command prints the same list instead.

A few commands mean something on their own rather than standing for a subcommand, and those still act on a bare invocation: /yolo, /fast, and /browser flip a switch, /goal enters goal mode, /todo shows the list, /secret opens the masked value field, /setup opens the wizard, /plugins lists plugins, and /compact compacts.

Session and navigation

Model, modes, and behavior

Tools, context, and jobs

Auth and usage

Extensions

Side agents and misc

Every subcommand

The tables above write … where a command takes a subcommand. This is the full set, so a name is findable without opening the picker. What each one does is on the picker row and in that feature’s own page; typing the bare command lists them with their descriptions.

Extension packages (for example swarm) register additional commands when installed. The live set is whatever the session registers; use /help or the command palette in the TUI. Status line: /statusline opens the Status Line settings group (see Multi-agent monitoring). Keybindings: /hotkeys. Memory: /memory and settings under the active memory backend.