> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/tools/remote-tools-overview/use-terminal.md).

# Use Terminal

JFrog Connect makes it easy to troubleshoot and maintain devices by using remote support tools. This page describes how to use Terminal.

JFrog Connect’s Terminal tool enables you to connect to your terminal through a web-based SSH. Using Terminal, you can troubleshoot remotely and resolve issues on your edge devices.

## Prerequisites

In order to use Terminal, you need the following:

* At least one online device.
* The following software installed on the device: ssh-server and ssh-client. (The ssh-client is installed by default when you download Connect Agent to the device. You will need to install ssh-server separately.)
* The edge device is online.
* The `root` user enabled.

You do not need to open any ports on the device or the firewall for the terminal to function.

## Open Session

To open a Terminal session, do the following:

1. There are two ways to open a remote terminal session:

   * **From the Terminal Page**: Go to **Remote Tools>Terminal** in the left menu and choose a device from the dropdown list. (This is the list of online devices in the project.) Click **Open Terminal**.

   <div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/pp3v0i8CAApFwEQrnVss/use-terminal-nui-01.png" alt=""><figcaption></figcaption></figure></div>

   * **From the Devices Page**: On the Devices page, click the **More** icon (three dots) in the row of the relevant device, then click **Remote Terminal**.
2. A popup will appear showing the progress of opening your remote terminal session. Enter the username you want to use for connecting to the device and click **Open**. The default username is `root`.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/mOFXEw8Q4Uuco2uyxTJa/use-terminal-nui-02.png" alt="" width="375"><figcaption></figcaption></figure></div>

When your Remote Terminal session is open, you will see a new window with the command-line interface of your Linux terminal. You can start your troubleshooting in this window.

## View Remote Terminal Session History

To view a brief history of the remote control sessions you have had, go to **Remote Tools**/**Terminal** in the left menu.&#x20;

The terminal sessions are listed in order of Close Time. The latest closed sessions are on top, below any open sessions. For each session, the table shows:

* Device name and UUID
* Session Duration
* Close time
* State

If you don’t see the session you are looking for in the table, refresh the page or use the Search to locate the session.

## What’s Next?

Learn how you can access and control your edge device with Connect’s [Port Tunnel](/features-new-ui/tools/remote-tools-overview/remote-access.md) tool.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.connect.jfrog.io/features-new-ui/tools/remote-tools-overview/use-terminal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.