Slash commands
Typing / in the composer opens a list of the commands this agent can run. Picking one tells the agent exactly which tool to start with, rather than leaving the choice to it.
When to use it
Section titled “When to use it”Use a slash command when you already know the procedure you want. “/weekly-report” is faster and more reliable than “can you do the weekly report the way we did last time” — the second is a request the agent has to interpret first.
Describe what you want in prose when you do not know which skill applies, or when the job spans several. The agent still chooses freely from everything bound to it.
Using one
Section titled “Using one”-
Type
/at the start of the composer. The list appears above the input. -
Keep typing to filter. Arrow keys move through the list; hovering or selecting a row shows what that command does.
-
Open the ⓘ beside a row to read the whole skill — what it is for, and every command it carries.
-
Press Enter to insert it, then write the rest of your message — a command usually needs context. “/summarize the thread from Hana about pricing” is a command plus a subject.
-
Send. The agent starts its run with that command, then continues normally.
What is in the list
Section titled “What is in the list”The list has two groups, and they behave differently.
Built-in commands
Section titled “Built-in commands”Built-in commands are features of the app rather than things the agent does. They are always there, on every agent, and running one starts no run and spends nothing.
| Command | Does |
|---|---|
/usage | Shows what this conversation has spent — tokens, credits, and the models involved. See the usage dashboard |
Built-in names are reserved. If a skill happens to carry the same name, the built-in is what runs; the skill’s row stays in the list so you can still see it is there.
Skill commands
Section titled “Skill commands”The rest come from the skills bound to this agent. Two consequences:
- A different agent has a different list. The same command is not available everywhere unless the skill is bound in both places.
- If the group is empty, no skill is bound yet. Bind one in Agent Builder; the list follows on the next message.
What picking a skill command actually does
Section titled “What picking a skill command actually does”The command names a tool, and the agent is required to call that tool on its first step. After that step it is back to normal: it reads the result and decides what to do next, including calling other tools.
That is the useful shape. You get a reliable start — the right procedure, opened with your input — without freezing the rest of the run into a script.
A name that is not a command
Section titled “A name that is not a command”Sending /something that matches nothing does not go to the agent. The composer stops it and says the name is not a command, so a typo does not become a message the agent has to interpret.
Only a message that is a slash and a single word, with nothing after it, is read as a command. /usage in July, a file path, and a sentence that happens to start with a slash are ordinary messages and are sent normally.
Limits
Section titled “Limits”- Skill commands are per agent. There is no global list of them; only built-in commands are the same everywhere.
- A skill command directs the first step only; the agent chooses the rest of the run.
- Sending a command while a run is in progress steers that run instead of starting the command — steering carries your text, not the tool choice.
- The list shows what the agent can call right now. A skill you bind mid-conversation appears on the next message.
- What a built-in command draws is local to that screen. It is not a message, so it is not in the transcript and is gone after a reload.