---
url: https://clusto.app/docs/concepts.md
description: >-
  Plain-language definitions of the words Clusto uses - node, cluster, session,
  chat, project, working directory, workspace, team and task - with links to the
  pages that cover each in detail.
---

# Concepts

The words Clusto uses, in the order you meet them. The app opens a short version
of this list once after your first connect (**F1 > What do Clusto terms mean?**
brings it back), and its **Learn more** links land here.

## Node

A computer running Clusto in the background, such as your PC, a server or a
Raspberry Pi. Its background service (the daemon, `clustod`) runs your
terminals, chats and tasks, and the app connects to it to show them.

The app and the `clusto` CLI are clients: they hold no sessions of their own. If
you close the app, everything keeps running on the node. See
[Architecture](/architecture) and [Downloads & Installation](/downloads) for how
to set one up, including the one-click setup for the computer you are using.

## Cluster

Several nodes linked together. Every node shares the same sessions, chats,
projects and settings, so you can connect to any one of them and reach the rest.

A single node is already a cluster of one. Nodes find and trust each other
through pairing and pinned identities. See [Clustering](/clustering) and
[Node Identity & Pairing](/node-identity).

## Session

A terminal running on a node: a shell or an agent CLI such as Claude Code. It
keeps running when you close the app, and you can reattach from any device.

Sessions are shown in the **Terminals** view, in panes you can split and
rearrange. A session is not tied to a pane: closing a pane leaves the session
running, and closing the session stops it. See
[Terminal Workspace](/terminal-workspace) and
[Transport & Resume](/transport).

## Chat

A conversation with an AI agent in Clusto's own chat view instead of a terminal.
The agent runs on a node and the history follows you across devices.

Use a chat when you want a transcript, attachments and queued follow-ups; use a
session when you want the agent's own terminal interface. See [Chats](/chats).

## Project

A named folder on a node, such as a code repository. Sessions, tasks and teams
start in it. The Locations page lists your projects next to chat workspaces and
SSH connections. With the unified workspace migrated, chat workspaces are
projects and the Workspaces tab is gone.

A project can carry defaults such as the shell, the OS account to run as and a
repository link. See [Importing Projects](/project-import) and
[GitHub](/github#clone-a-repository-as-a-project).

## Working directory

The folder a terminal, task or agent starts in, on the node that runs it. It
defaults to the project folder; the folder button next to the field browses that
node.

Because the folder is on the node, not on the device you are holding, a path
you type must exist there. The browse button lists the folders of the node the
session will run on. See [Tasks](/tasks#defining-a-task).

## Workspace

Two things share this name. The Workspace view is your layout of terminal panes.
A chat workspace is a folder whose files travel with a chat to any node.

For the pane layout, see [Terminal Workspace](/terminal-workspace). For the chat
folder, see [Chats](/chats#portable-workspace-layout).

## Team

A group of AI agents that work together: a leader splits the work and workers
pick up their parts, messaging each other as they go.

A team can show up as a **Team** tab beside the conversation that started it.
See [Teams](/teams).

## Task

A command or agent prompt that runs on a node on a schedule or when you start
it, with every run and its output kept for later.

A task can run as a chosen OS account and can post a report when it finishes.
See [Tasks](/tasks) and [Reports](/reports).
