Slash commands

Slash commands are shortcuts you type into the chat composer to steer the agent’s next turn — start a goal, force a compression, run a coding agent, kick off research, and more.

Typing a command

The command palette listing every slash command enabled for the agent

In any chat with an agent, type / as the first character of a message, then the command name and any arguments:

 

/goal Fix every failing test in tests/ and report the command that passes

Press Enter to send it like a normal message. A few rules:

• The / must be the very first character — a slash mid-sentence is treated as plain text.
• Everything after the command name is passed as arguments; arguments can span multiple lines (useful for a Rubric: block).
• If a command name isn’t one of the built-ins below, the agent tries to run it as a skill of the same name.

All commands

Command	What it does	Capability toggle	Details
/clear	Wipes the conversation history for this session and destroys the session sandbox, giving you a clean slate.	Always on (no toggle)	—
/compress	Forces context compression right now instead of waiting for the automatic threshold. Refuses when the conversation has 5 messages or fewer.	/compress	—
/code	Runs a coding agent (Claude Code or Codex) in the session sandbox using your own plan. Sub-verbs for login, status, and runs.	/code	Coding agents
/deep-research <topic>	Delegates once to a research sub-agent that produces a cited report. Single-shot.	/deep-research	Deep research
/mission …	Rubric-judged orchestration — a strict coordinator that decomposes and drives an objective to completion.	/mission	Missions
/goal …	A session outcome the agent keeps iterating toward until an evaluator says it’s met.	/goal	Goals
/loop …	Schedules a prompt to run on a recurring interval, or self-paced when you give no interval.	/loop	Scheduled work
/stop (or /cancel)	Interrupts the turn that’s running right now. Messaging channels only.	Always on (no toggle)	—
/<skill-name> [args]	Runs an attached skill (or consults an active expert) by name.	Per skill attachment	below

/clear and /stop are always available — neither has a capability toggle. Every other built-in is gated by a per-agent toggle on the CONFIG page’s Capabilities tab (see Configure an agent). A master switch there turns all built-in commands on or off at once, with individual toggles below it. When a command is turned off, typing it has no special effect.

/clear in detail

/clear does two things at once:

1. Replaces the entire conversation history with an empty context — the next turn starts fresh.
2. Destroys the session’s sandbox if one exists, so any files, processes, or checkouts from this session are gone.

It confirms with Conversation cleared. Use it when the current context is no longer useful and you want to keep working in the same session with a clean start. The durable event log is untouched; only the model-visible context is reset.

/stop in detail

/stop (or /cancel) is how you interrupt an agent from Slack, Telegram or WhatsApp. Send it on its own, with nothing else in the message. It travels out of band — it doesn’t queue behind the turn it’s cancelling, which is why a long run can still be stopped mid-flight. The bot acknowledges with ⏹ Stopping the current run…; nothing is added to the conversation history.

On Web there is no /stop. While a turn is running the send button becomes a stop control that does the same thing (see Chatting with an agent).

On Slack, typing /stop opens Slack’s own command menu instead of sending a message — put a single space before the slash so Slack passes it through.

/compress in detail

/compress runs the configured context compressor immediately rather than waiting for the automatic threshold, then replies with a short summary of what happened. If the conversation has 5 or fewer messages it refuses with “Context is too small to compress” — there is nothing meaningful to compact yet. Use it before continuing a long session that’s approaching its context limit.

Running a skill

Any slash command that isn’t a built-in is resolved as a skill attached to the agent:

 

/research vector databases
/babysit-prs

When the command name matches an attached skill, the agent inlines that skill’s instructions (its SKILL.md) into your message before the model acts on it, and stages any supporting files the skill ships. Anything you type after the name is passed to the skill as its request. If the matched skill is an active expert, the command instead runs an expert consultation and hands the expert’s deliverable back into the conversation.

If no attached skill matches the name, your message reaches the agent unchanged (it just looks like text that starts with /). Built-in command names are reserved and are never treated as skill names. Which skills are attached — and therefore which /<skill-name> commands exist — is configured per agent on the CONFIG → Skills tab.

Related pages

• Goals (/goal) — iterate toward a session outcome.
• Missions — the dashboard for /goal and /mission runs.
• Scheduled work — the /loop schedules an agent runs.
• Coding agents (/code)
• Deep research (/deep-research)