Commands

You can use the Commands tab to browse and manage commands used with Zide Assist. Use commands for frequently used tasks.

Navigate the Commands activity

To open Commands, click Assist > Commands.

Click a command to display the following information.

• Display Name: The name of the command.
• Command Name: The command to run in Zide Assist. The command name is based on the display name.
• Description: A brief description of what the command does.
• Inputs: Parameters the command accepts.
• Prompt: The instructions sent to Zide Assist when the command runs.

To open a command in a separate tab, right-click the command and click Open in New Tab.

Commands are organized into the Built-in, Global, and Project sections.

Built-in

The Built-in section displays read-only commands that ship with Zide. Built-in commands cannot be edited or deleted.

Global

The Global section displays user-created commands. Global commands are available in every project. Global commands are located in the commands folder of your Zide application data directory.

Project

The Project section displays project-specific commands. Project commands are located in the .zide/shared/commands/ directory of the repository and can be used by other members of that repository.

Create commands in Zide

To create a new command, complete the following steps.

1. In the Commands activity, click New Command.
2. Click New Global Command to create a global command or New Project Command to create a project command. A blank command is created in either the Global section or Project section.
3. Enter the name of the command in the Display Name field. The display name is also the command name used to run the command in Zide Assist.
4. Optional: Enter the description of the command in the Description field.
5. Optional: To add an input to the command, click New Input. Input types are text, textarea, bool, and enum.
6. Enter the instructions Zide Assist should follow in the Prompt field.
7. Optional: Click Enable multi-step processing to make the command a multi-step prompt. For more information, see Multi-step commands.
8. Click Save.

You can copy an existing command to create a new command. To copy a command, click the Make Copy icon and then click either Copy to Global or Copy to Project.

Click Save to save the changes you made to a command. Click Revert to remove all unsaved changes to a command.

Click the Delete icon to delete the command.

The same command name can be used for Project, Global, and Built-In. A project command with the same name as a global command or built-in command takes priority. A global command with the same name as a built-in command is run.

Inputs

Inputs let a command collect values when it runs. When you run a command that has inputs, Zide displays a dialog that collects each value before the prompt is sent. To add an input to the command, click New Input.

Each input has one of the following types.

• text: A single-line value.
• textarea: A multi-line value.
• bool: A checkbox that resolves to true or false.
• enum: A dropdown restricted to a fixed set of choices.

Reference an input in the command description with a {{name}} placeholder, where name matches the input name. When the command runs, Zide replaces each placeholder with the value collected from the input dialog.

While editing a command, the editor lists the command inputs as clickable icons. Click an icon to insert the placeholder at the cursor.

If you create an input field but do not reference the input in the command description using a {{name}} placeholder, Zide appends those values at the end of the command in a Parameter section.

Run a command

To run a command, type a forward slash, /, followed by the command name into the Zide Assist message box and then click Send.

You can also send a file to Zide Assist from the Files activity:

• Right-click a file and click Send to Zide Assist > As Prompt to send its contents as a prompt.
• Drag a file into a Zide Assist tab to use the file as an attachment.
• Drag a file into the Zide Assist message box.

Create and edit command files manually

Global and project commands can be created and edited as Markdown files.

The following is an example of a Markdown file for a Fix Issue command.

---
name: Fix Issue
description: Investigate and fix a GitHub issue
inputs:
  - name: issue
    label: Issue number
    type: text
    default: "#42"
  - name: scope
    label: Scope
    type: enum
    options:
      - backend
      - frontend
---

Investigate issue {{issue}} in the {{scope}} code and propose a fix.

You can manually choose which model the command runs on by starting the prompt with /model. The following line sets a command to use Claude Opus 4.8.

/model claude-opus-4-8