---
url: https://clusto.app/docs/explorer-menu.md
description: >-
  Open a Clusto terminal or add a project from the Windows Explorer right-click
  menu, set up this PC as a node when it has none, and use local terminals that
  need no node.
---

# Explorer menu and local terminals

On Windows, Clusto adds a **Clusto** submenu to the File Explorer right-click menu. It
opens a terminal or creates a project for a folder without first switching to the app.
When this PC has no Clusto node in the cluster you are connected to, Clusto walks you
through setting one up. Local terminals are a separate, node-free way to get a shell in
the desktop app.

This is a desktop feature. It is not available on the web client or mobile.

## The Clusto menu

Right-click a folder, a drive, or empty space inside a folder, then choose **Clusto**.
On Windows 11 the classic menu is under **Show more options**.

| Entry | What it does |
|-------|--------------|
| **Open terminal here** | Opens a terminal session in that folder on the Clusto node running on this PC. If the folder is inside an existing project, the session starts under that project: it uses the project's default shell and is grouped with the project's terminals. |
| **Add as Clusto project** | Opens the New project dialog prefilled with the folder name, the folder path and this PC's node. If a project already uses that folder, Clusto opens that project instead. |

The installer adds the menu for the current user only, so it needs no administrator
rights. Uninstalling Clusto removes it.

Clusto does not need to be running. If the app is closed, choosing an entry starts it,
waits for it to connect, then performs the action.

### Turn the menu off or on

Open **Settings > This device > Explorer menu** and switch it off or on. Turning it off is
remembered across updates, so a new version does not bring the menu back.

## When this PC has no node

The menu acts on the Clusto node running on this PC. If the connected cluster has no node
for this PC, Clusto shows a dialog that explains this and offers the options that apply.

| Option | When it appears | What it does |
|--------|-----------------|--------------|
| **Set up this PC as a node** | No Clusto node is installed | Runs the app's [one-click setup](/downloads#set-up-this-computer-from-the-app), which starts a node inside the app ([local mode](/downloads#local-mode-a-node-inside-the-app)) with no administrator prompt; builds without the bundled CLI show one. No pairing code to copy. |
| **Add this PC's node to the cluster** | A node is installed but belongs to another cluster | Opens the Add node dialog. |
| **Open a local terminal** | Only for **Open terminal here** | Opens a [local terminal](#local-terminals) in the folder. |

### Setting up the node

1. Choose **Set up this PC as a node**. Approve the administrator prompt.
2. The app generates a pairing code and passes it to the installer itself.
3. When the app is not connected, it pairs with the new node, saves a profile and
   connects. When it is connected to a cluster, the Add node (adopt) dialog opens with
   the pairing code already filled in, ready to adopt the node.

After the node joins, Clusto runs the request you started with: the terminal or the
project. See [Node Identity & Pairing](/node-identity) for what the pairing code proves.

On Linux and macOS the setup option shows the command to run in a terminal instead of
launching an installer. The script runs the setup wizard itself:

```bash
curl -fsSL https://dl.clusto.app/install.sh | sh
```

### Always open a local terminal

For **Open terminal here**, the dialog has a checkbox, **Always open a local terminal on
this PC**. With it checked, Clusto skips the dialog next time and opens a local terminal
directly. The same preference is in **Settings > This device**.

## Local terminals

A local terminal is a shell the desktop app runs itself on this device, with no Clusto
node involved. It is for quick work on a PC that is not part of a cluster.

On a desktop PC the **Local terminals**
view appears in the navigation, and **Go to Local terminals** and **New local terminal**
are in the F1 command palette. **New local terminal** asks for a folder with the operating
system's folder picker.

The shell is chosen per platform:

* **Windows**: `pwsh` if installed, then `powershell`, then `cmd`.
* **Linux and macOS**: the shell in `$SHELL`.

### Limits

A local terminal is deliberately simple. Compared with a node session:

* It is not saved and is not visible on any other device.
* There are no agents, chats, or session history.
* It ends when the app closes. The app kills all local terminals on exit.
* Pasting images or uploading files is not available. A file pasted from the host is
  inserted as its path.
* It runs in the desktop app only (Windows, Linux, macOS), not on web or mobile.

Closing a running local terminal asks for confirmation. When a shell has exited, the
terminal shows **Restart** and **Close**.

## See also

* [Terminal Workspace](/terminal-workspace) - how terminals and projects are grouped
* [Node Identity & Pairing](/node-identity) - adopting a node with a pairing code
* [Separate Desktop Windows](/desktop-windows) - other desktop-only features
