> ## Documentation Index
> Fetch the complete documentation index at: https://sitectl.libops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Terminal UI

> The interactive terminal interface for monitoring sites, running operator workflows, and setting up new environments.

export const Compose = () => <Tooltip headline="Compose" tip={<>
        Docker Compose is Docker's tool for defining and running multi-container applications.{" "}
        <a href="https://docs.docker.com/compose/">https://docs.docker.com/compose/</a>.
      </>}>
    <>
      <Icon icon="docker" />
      {" "}
      Compose
    </>
  </Tooltip>;

export const TUI = () => <Tooltip headline="TUI" tip="Terminal User Interface: an interactive command-line interface for navigating and operating sitectl.">
    TUI
  </Tooltip>;

The `sitectl` <TUI /> is the main interface for day-to-day site operations. Launch it by running `sitectl` with no arguments:

```bash theme={null}
sitectl
```

## What it shows

The <TUI /> gives you a live view of your configured contexts and the <Compose /> projects behind them. From a single screen you can see:

* **Container health:** which services are running, restarting, or unhealthy.
* **Host resource usage:** CPU, memory, and disk on the host machine.
* **Logs:** recent log output from your containers.
* **Context overview:** which site and environment you're looking at, and how to reach it.

When you have multiple contexts configured, the <TUI /> lets you move between them without leaving the interface.

## What you can do

<Columns cols={2}>
  <Card title="Set up an existing site" icon="server">
    Walk through the prompts to connect sitectl to a <Compose /> project you already run locally or remotely.
  </Card>

  <Card title="Create a new site" icon="square-plus">
    Use the guided create flow, powered by your installed plugin, to scaffold and configure a new site.
  </Card>

  <Card title="Monitor health" icon="heart-pulse">
    Watch container status, host resources, and log output from the dashboard without running individual commands.
  </Card>

  <Card title="Switch environments" icon="arrows-rotate">
    Move between local and remote contexts for the same site to compare or operate across environments.
  </Card>
</Columns>

## When to use the CLI instead

The <TUI /> is designed for interactive use. For automation, scripting, or one-off operations, the individual sitectl commands are more direct:

```bash theme={null}
sitectl compose ps
sitectl drupal drush cr
sitectl debug
```

Both modes share the same underlying logic. You can use them interchangeably based on what the task calls for.