> 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/control-center-remote-ssh-commands.md).

# Run Commands Remotely

With JFrog Connect, you can run a command remotely on one or multiple edge devices. View the command output and save the command to use again later.

In JFrog Connect, the Command Runner tool provides a simple solution for running commands remotely on your edge devices.

Connect provides several convenient ways to run commands on your edge devices.

* If you want to run several commands in succession, or run a command along with other operations on the edge device, create an [update flow](/features-new-ui/deployments/update-flow.md) that uses the [Run Command](/features-new-ui/deployments/update-flow/step-types/run-command.md) step type in one or more steps.
* If you want to run a single command remotely on multiple devices, you can do it using the Command Runner tool. This page describes how to create and run commands with Command Runner.&#x20;

You can create Bash commands, run them on devices you select, and save the commands for later use. After running a command, you will be able to view its output.

By default, Connect runs the commands on your edge device as a Linux root user. If you want the commands to run as non-root, see [Run Commands as Non-root User](/features-new-ui/tools/remote-tools-overview/control-center-remote-ssh-commands/running-commands-as-user.md).

## Enter and Run a Command

To enter and run a command, do the following:

1. Go to **Remote Tools**/**Command Runner** in the left menu and in the **Run Commands** tab, click **Run Command**. The Run Command wizard opens on the right.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/JOZKDa5aYtXsVu1ycFDT/run-commands-remotely-nui-01.png" alt=""><figcaption></figcaption></figure></div>

2. Enter a Bash command in the Command field. Click **Next**.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/fQ1AgMQ7DaNnpBSt26zQ/run-commands-remotely-nui-02.png" alt="" width="563"><figcaption></figcaption></figure></div>

3. Using groups and/or additional filters, select the device(s) to receive the command. Click **Next**.
4. View the number of devices affected by the filter you applied. If this does not look right, you can go back and reset your device filter. Once you are satisfied with the filter applied, run the command on the device(s) you have chosen.

## What’s Next?

Learn how to [run a saved command](/features-new-ui/tools/remote-tools-overview/control-center-remote-ssh-commands/run-a-saved-command.md).


---

# 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/control-center-remote-ssh-commands.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.
