Slash Commands

Command Code ships with over 60 built-in slash commands covering sessions, context, permission modes, models, billing, and everything in between - and you can extend the set with your own custom commands, skills, and mod-added commands.

How the slash menu works

Type / at the start of the input to open the command menu:

• Filtering - as you type, rows are ranked by match quality: a command whose name starts with your query ranks highest, then commands containing it, then description matches. The list re-sorts on every keystroke.
• Exact-match highlighting - the input text stays plain while you type a partial name; it only turns accent-colored once it names a real command (a half-typed /mod stays plain, /model lights up).
• Aliases on canonical rows - an alias is not a second menu row. /new resolves to /clear everywhere, and the single canonical row advertises it as /clear (new). Typing the alias still surfaces and ranks that row.
• Navigation - ↑/↓ move the selection, Enter runs the selected command, Tab or → inserts it into the input with a trailing space so you can type arguments, Esc closes the menu.
• Dynamic rows - custom commands, mod commands, and skills load asynchronously; built-ins render first and the dynamic rows appear as discovery settles.

Built-in Commands

Every built-in command, grouped by area. Aliases are shown in parentheses on the canonical command; optional arguments in [brackets], alternatives separated by |.

Sessions

Context & Compaction

Modes & Planning

Models & Providers

Extensibility & Integrations

Workspace

Billing & Account

Utilities

Command behavior

Bare invocations that open a picker

/model, /effort, and /theme each take an optional value (/model gpt-5, /effort high, /theme dark) that applies directly as a one-shot. But unlike other optional-value commands, running them bare doesn't perform a default action - it opens an interactive picker immediately. Bare /mode also runs immediately, printing the current mode and the available switches (/mode:default, /mode:auto-accept, /mode:plan - or press shift+tab to cycle).

/effort only opens its selector when the current model supports reasoning effort levels; otherwise it prints a notice that effort isn't supported for that model.

/theme offers three values. dark and light pin a palette; auto — the default — automatically detects your terminal's background color at startup (OSC 11, falling back to COLORFGBG) and uses light or dark to match. A terminal that won't report its background falls back to dark.

Commands with meaningful default actions when bare

Some optional-argument commands do something useful with no argument instead of opening a picker: bare /share creates a share link, bare /import imports from all detected sources, bare /export exports in the default format, bare /goal (or /goal status) shows the current goal, bare /name shows the current session name, and bare /plan enters plan mode without a task.

Safe while the agent is busy

Most commands are blocked mid-turn - mode flips, session switches, model changes, compaction, and anything that would race an active turn waits until the agent finishes. A deliberate set of read-only or local commands stays available while a turn is running:

• /trace - capture the live trace id of the running turn (its main purpose)
• /session-file - read-only session facts
• /copy - clipboard only
• /todos (also ctrl+x) - edits local todo state, most useful mid-turn while a plan is being driven
• /exit / /quit - always available
• /goal clear - stops the goal loop; the current step finishes, then the loop stops. Setting a new goal mid-turn is refused with a busy notice.

Most other commands - /clear, /mode, /plan, /model, /compact, /worktree, /resume, /login, and the like - report busy and ask you to wait for the current turn (or press Ctrl+C). (/review is an exception: it runs mid-turn.)

/goal in detail

/goal <objective> sets an objective (up to a length limit) and arms an autonomous loop capped at a maximum number of turns. /goal status (or bare /goal) shows the active goal and progress; /goal clear clears it. /goal resume and /goal pause are reserved but not available yet.

Custom Slash Commands

Custom slash commands let you save frequently used prompts as markdown files. Define a command once, then run it anytime with dynamic arguments.

The command name comes from the markdown filename (without the .md extension).

Locations

The file's full trimmed body is the prompt that runs; the slash menu shows its first meaningful line (skipping YAML frontmatter and markdown markers, truncated to ~80 chars) plus the location label.

Namespacing

Organize commands in subdirectories to any depth. The subdirectory appears in the description label but does not affect the command name:

Argument templating

Placeholders in the command body are replaced with your arguments in a single pass (substituted text is never re-scanned, so an argument containing $1 lands literally):

Arguments split on whitespace, respecting single and double quotes:

Example (.commandcode/commands/commit.md):

Edge cases: an out-of-range slice (${@:9} with three args) expands to an empty string; an unrecognized ${...} expression (e.g. a literal ${HOME}) is left untouched so shell/env-style text survives; a template with no placeholders passes through unchanged.

Dispatch precedence

When multiple sources define the same name, dispatch resolves in this order - first writer wins:

1. Built-in commands (the full set, including any the menu hides)
2. Mod commands (added by active mods)
3. Custom commands (.commandcode/commands/, ~/.commandcode/commands/)
4. Skills

So a custom command can never override a built-in, and a skill shadowed by any of the above resolves to its owner. Shadowed skills still render in the menu with a - shadowed by /<name> note so you know they exist, and they run under the skill: namespace: /skill:<name> bypasses this whole ladder and only ever resolves to a skill. Lookup is case-insensitive (/Reload resolves to /reload).

Skill invocation

Installed skills are invocable as /<skill-name> and appear in the menu with a [skill] badge. A skill's argument-hint frontmatter leads its menu description (e.g. /pr-desc [skill] <branch> - Generate a PR…), and skills marked user-invocable: false stay model-invocable but never appear in the / menu. Duplicate skill names dedupe with project taking precedence over global.

Mod commands

Active mods can register their own slash commands; they slot in between built-ins and custom commands in both the menu and dispatch. Discovery is fault-tolerant - a broken commands directory or unreadable skill never breaks the menu; each source just degrades to empty.

Next steps

• Explore the CLI Reference for flags and subcommands
• Create your first custom command and try it out
• Join our Discord community for feedback, requests, and support.