Type a slash in the composer to run an action. The list you see depends on the surface (Chat, Work or Code), on whether you are in the desktop app, and on whether the chat already has messages.
Use a slash command
Enter /, then pick an entry or keep typing to filter. Use $ for skills only (Skills & Plugins), and @ or the + menu for plugins, connectors, files and other mentions. Commands that come from plugins or from Customize > Commands appear in the same menu; a skill with the same name as a built-in command takes precedence.
Available slash commands
Commands marked desktop are hidden on the web. Most are offered in Work and Code; a few only in Code.
| Command | Does |
|---|---|
/cloud | Run this chat in the cloud (desktop) |
/code-review | Review unstaged changes or compare against a branch (desktop) |
/commit | Create a Git commit (Code) |
/commit-push-pr | Commit, push and open a pull request (desktop) |
/compact | Summarize the conversation to free up context |
/cost | Show cost and token usage for this session (Code and Work) |
/diff | Review the changes made this session (Code) |
/explain | Explain code, a symbol or a concept in the project |
/fork | Continue in a new chat, in this workspace or a new worktree |
/goal | View or manage the thread's goal |
/ide-context | Attach open files, the active file and recent selection to the next message (Code, desktop) |
/init | Have the agent write an AGENTS.md for the project (desktop) |
/mcp | Manage MCP servers and connectors (desktop) |
/memory | Open memory settings |
/model | Switch the active model |
/new-chat | Start a new chat |
/pet | Wake or tuck away the desktop pet (desktop) |
/plan-mode | Turn plan mode on |
/plugin | Manage installed plugins |
/pr-comments | Summarize the comments on a GitHub pull request (Code) |
/reasoning | Set the reasoning effort |
/recap | Summarize the repository's structure |
/rewind | Restore the conversation to an earlier turn (Code) |
/side | Start a temporary side chat |
/summarize | Summarize this conversation into a new thread (Chat) |
Some commands, such as /compact, /fork and /side, only appear once the chat has a thread. The iOS and Android apps offer a shorter menu of 14 commands.
Attach editor context with /ide-context
In Code on desktop, /ide-context captures what you have open in the app: the open file tabs, the active file, any selection made in the file viewer in the last three minutes, and the workspace folder and branch. No external IDE connection is needed. A removable IDE context chip appears above the composer, and the snapshot is sent with your next message only. If nothing is open, ZeroTwo asks you to open a project or a file first.
Set or manage a goal with /goal
A goal is a standing objective that ZeroTwo keeps working toward until it is complete, paused or blocked. Use /goal <objective> to set one, then /goal edit <text>, /goal pause, /goal resume or /goal clear to manage it; a banner above the composer shows the goal's state and offers the same controls. An objective can run to 4,000 characters, with an optional token budget. Goals are tracked on the server and continue automatically (a goal on a local task continues only through the desktop that started it), and cannot be combined with plan mode in the same composer. See Goal mode.
Plan first with /plan-mode
/plan-mode tells the agent to research the task and present a step-by-step plan, and not to edit files or take irreversible actions until you approve it. The composer also has a Plan mode toggle, which keeps the sandbox read-only for the turn. After approving the plan, continue the work or set it as a /goal.