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

# Using the Web Terminal

> Access running custom containers directly from the AirCloud Console

The Web Terminal lets you connect to a running container through a browser-based shell directly from the AirCloud Console.

It is ideal when you need quick operational access without configuring `sshd`, registering SSH keys, or setting up a local terminal.

## When to Use the Web Terminal

The Web Terminal is recommended when you want to:

* Open a shell directly from the Console.
* Quickly inspect files or running processes inside a container.
* Run lightweight verification or debugging commands.
* Avoid configuring SSH access.

## Availability

### Custom Containers

For custom containers deployed by users, click **Terminal** from the endpoint overview page while the container is running.

<img src="https://mintcdn.com/aieev-723717ca/wvjECKx2Z_KXqy1h/images/terminal1.png?fit=max&auto=format&n=wvjECKx2Z_KXqy1h&q=85&s=a3743ef654049d76b6551fc2290ad83d" alt="Terminal1" width="776" height="692" data-path="images/terminal1.png" />

### AirCloud Templates

Some AirCloud-provided templates include their own built-in terminal interface.

Examples include:

* Notebook environments opened with **Open Notebook**
* Web-based IDE environments

<img src="https://mintcdn.com/aieev-723717ca/wvjECKx2Z_KXqy1h/images/jupyter_notebook.png?fit=max&auto=format&n=wvjECKx2Z_KXqy1h&q=85&s=3a54a772a9b52f1e812f915be2f3b5aa" alt="Jupyter Notebook" width="686" height="542" data-path="images/jupyter_notebook.png" />

<img src="https://mintcdn.com/aieev-723717ca/wvjECKx2Z_KXqy1h/images/terminal2.png?fit=max&auto=format&n=wvjECKx2Z_KXqy1h&q=85&s=54be9ce7c8fd0208fc5119d042826fc5" alt="Terminal2" width="632" height="644" data-path="images/terminal2.png" />

In these cases, you can use the terminal already provided within the notebook or IDE without opening the **Terminal** button on the endpoint page.

## How the Web Terminal Works

### 1. Open the Terminal

From the endpoint overview page, click **Terminal**.

### 2. Enable Terminal Access

The first time you open the terminal for an endpoint, an activation dialog appears before the session starts.

This enables browser-based terminal access for the endpoint without requiring an `sshd` configuration.

<img src="https://mintcdn.com/aieev-723717ca/wvjECKx2Z_KXqy1h/images/%ED%99%9C%EC%84%B1%ED%99%94.png?fit=max&auto=format&n=wvjECKx2Z_KXqy1h&q=85&s=ef36acd88c19765eb979d723c5732085" alt="Enable Terminal Access" width="2150" height="434" data-path="images/활성화.png" />

Once terminal access has been enabled, you will not be prompted again unless the endpoint's access policy is reset.

### 3. Select a Replica

After terminal access has been enabled:

* If there is **one running Replica**, the session connects automatically.
* If there are **multiple running Replicas**, you are prompted to choose which Replica to connect to.

<img src="https://mintcdn.com/aieev-723717ca/wvjECKx2Z_KXqy1h/images/select_replica.png?fit=max&auto=format&n=wvjECKx2Z_KXqy1h&q=85&s=cb340b42d824235c65f48376b9b23efc" alt="Select Replica" width="680" height="482" data-path="images/select_replica.png" />

If the selected Replica is restarted or replaced while the session is active, the Web Terminal automatically attempts to reconnect.

### 4. Connect to the Replica

After selecting a Replica, a browser-based terminal session is opened for that Replica.

<img src="https://mintcdn.com/aieev-723717ca/wvjECKx2Z_KXqy1h/images/image-4.png?fit=max&auto=format&n=wvjECKx2Z_KXqy1h&q=85&s=6b474f0d5df520d70fd4a64838a36f51" alt="Image 4" width="2168" height="1292" data-path="images/image-4.png" />

### 5. End the Session

You can close the session by:

* Running `exit`
* Pressing `Ctrl + D`

After the session ends, the terminal window automatically closes after approximately **2 seconds**.

<img src="https://mintcdn.com/aieev-723717ca/wvjECKx2Z_KXqy1h/images/image-5.png?fit=max&auto=format&n=wvjECKx2Z_KXqy1h&q=85&s=6b5c139abc476ac7eef2ff799c87277b" alt="Image 5" width="1262" height="1010" data-path="images/image-5.png" />

## If the Web Terminal Does Not Open

Check the following:

* The endpoint is running.
* At least one Replica is running.
* You have permission to access the endpoint.

If no running Replica is available, the terminal cannot be opened until a Replica becomes available.

## Using `aircloud exec` from a Local Terminal

If you prefer SSH-free shell access from your local terminal instead of the AirCloud Console, use `aircloud exec`.

### Open a Shell

```bash theme={null}
aircloud exec <endpoint_id>
```

Example:

```bash theme={null}
aircloud exec 7fe76055-4159-47a5-a68d-320564e20540
```

### Connect to a Specific Replica

```bash theme={null}
aircloud exec <endpoint_id> -r <replica_id>
```

### Use a Different Shell

```bash theme={null}
aircloud exec <endpoint_id> -c "/bin/sh"
```

### End the Session

Run `exit` or press `Ctrl + D` to close the session.

## Web Terminal vs. `aircloud exec`

Both **Web Terminal** and **`aircloud exec`** provide SSH-free shell access to running containers.

The difference is where you start the session:

* **Web Terminal** starts from the AirCloud Console.
* **`aircloud exec`** starts from your local terminal.