Slash command reference
このコンテンツはまだ日本語訳がありません。
Slash commands are interactive terminal user interface (TUI) controls, not shell subcommands. The registry is assembled at startup from built-in commands plus whatever the loaded plugins and extensions register.
How do I find a command or keybinding?
Section titled “How do I find a command or keybinding?”Type / in the prompt to list the registry active in the current session, and /hotkeys to read the resolved terminal key map. Autocomplete narrows the list as you type, so it reports the current release, mode, and extension set rather than a published snapshot.
Which subsystems have their own commands?
Section titled “Which subsystems have their own commands?”| Subsystem | Entry point |
|---|---|
| Models and routing | /model |
| Sessions and history | /session, /resume, /tree, /branch, /fork, /compact, /export |
| F5 Distributed Cloud | /context, /namespace, /manifest, /validate, /diff, /apply, /get, /create, /delete |
| Capabilities | /tools, /agents, /plugin, /extensions, /mcp |
| Session state | /settings, /hotkeys, /memory, /usage, /plan |
/context status, /mcp list, and /plugin list report the current state of those subsystems without changing anything.
Slash commands are resolved from the active built-in, extension, plugin, and project capability set,
so /help is the complete lookup surface for the running session. Keybindings depend on the active
component: a modal selector consumes keys before the prompt editor, and global actions apply only
when no focused surface overrides them. If a shortcut differs from this page, record the xcsh
version, active modal, and /help entry before filing a defect.