Skip to content
Zide Zide

Terminal

You can use a functional terminal shell within Zide.

To open a Terminal tab, click Tools > New Terminal. The terminal opens in the root directory. Multiple Terminal tabs can be open simultaneously.

In the Terminal tab, click the Show prompt indicators on scrollbar icon to enable indicators on the scrollbar to navigate command history. Click on an indicator to quickly navigate back to the command.

Shells

You can open the Terminal tab with different shells. To open a terminal with a specific shell, click Tools > Shells and select a shell.

By default, a terminal opens in the system default shell. You can change the default shell in Settings.

Companion terminal

Companion terminals are terminals that open in a separate window. To open a companion terminal, click Tools > Companion Terminal.

CLI agent suggestion

If you run a known AI coding agent (such as Claude Code, Codex, or Gemini CLI) in a plain Terminal tab and you have not configured a CLI agent in Zide yet, a notice appears offering to run that tool in a dedicated CLI Agent tab instead, with prompt building and project context.

Clicking the notice’s open button configures the detected tool and opens a fresh CLI Agent session. The agent already running in your terminal is not affected. If you launched the tool with its unrestricted flag (for example claude --dangerously-skip-permissions), the new session uses the matching unrestricted profile and asks you to confirm before it starts.

Zide also scans for your other installed CLI agents in the background and creates profiles for everything it finds, so each tool is ready in the launcher afterward. A banner in the new CLI Agent tab confirms how many profiles were created, with a link to the CLI Agent Profiles dialog.

Zide detects the running tool by process identity only. It never inspects what you type into the terminal, and it never stores or logs command arguments.

Closing the notice with the ✕ hides it until you restart Zide. Click Don’t show again to suppress it permanently. The notice also stops appearing once any CLI agent is configured.