> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/getting-started/onboarding/agent-deployment/cybaagent-linux.md).

# CybaAgent - Linux

*<mark style="color:$info;">Command-line installation on Linux</mark>*

This guide walks you through installing CybaAgent on a Linux machine using the terminal.\
The installation takes about 2–3 minutes.

### <mark style="color:$primary;">Before you Start</mark>

Make sure you have the following ready:

* An account with sudo privileges on the Linux machine.
* Access to CybaOps so you can open Asset Manager.
* A working internet connection.
* The tar command available (installed by default on most distributions).

## <mark style="color:$primary;">Step 1 — Download CybaAgent from Asset Manager</mark>

1. Sign in to CybaOps and open Asset Manager.
2. Click the Deploy Agent button in the top-right corner.
3. In the Deploy Agent window, set Select Agent to CybaAgent and Select Operating System to Linux.
4. Click Download Agent and save the CybaAgent.tar.gz archive to your Downloads folder

{% hint style="warning" %}
**Keep this window open: The Deploy Agent window also shows your install command**\
**with your activation code pre-filled — you'll copy it in Step 3.**
{% endhint %}

## <mark style="color:$primary;">Step 2 — Open a Terminal</mark>

1. Open your terminal application (for example GNOME Terminal, Konsole, or any terminal you normally use).
2. Move into the folder where the archive was downloaded by typing the command below and pressing Enter:

{% code overflow="wrap" %}

```
cd ~/Downloads
```

{% endcode %}

(If you saved the file somewhere else, use cd followed by the full path to that folder instead.)

## <mark style="color:$primary;">Step 3 — Run the Install Commands</mark>

Copy each command from the Deploy Agent window in CybaOps and paste it into the\
terminal, pressing Enter after each one. Run them in order:

Extract the archive — this produces a CybaAgent binary in the current folder:

{% code overflow="wrap" %}

```
tar -xvf ./CybaAgent.tar.gz
```

{% endcode %}

Make the CybaAgent binary executable:

{% code overflow="wrap" %}

```
chmod +x ./CybaAgent
```

{% endcode %}

Install the agent (replace tt-YOURACTIVATIONCODE with the one shown in Deploy Agent):

{% code overflow="wrap" %}

```
sudo ./CybaAgent -i -t tt-YOURACTIVATIONCODE -s https://cybaverse.cybaops.com/
```

{% endcode %}

{% hint style="info" %}
**Tip: Always copy the command directly from Deploy Agent rather than typing it — that**\
**way your activation code is guaranteed to be correct.**
{% endhint %}

{% hint style="info" %}
**About the password prompt: When you run a sudo command, you'll be asked for your**\
**login password. Type it and press Enter — the cursor won't appear to move while you**\
**type, but the characters are being entered.**
{% endhint %}

### <mark style="color:$primary;">What the Commands do</mark>

* **tar -xvf ./CybaAgent.tar.gz** — extracts the downloaded archive into the current folder.  \
  The -x flag means extract, -v lists files as they're unpacked, and -f tells tar which  \
  archive to use.
* **chmod +x ./CybaAgent** — marks the extracted file as executable so the system will let  \
  it run.
* **sudo ./CybaAgent -i -t … -s …** — runs the installer as root. -i installs the agent, -t passes  \
  your unique activation token, and -s tells the agent which server to report into.

## <mark style="color:$primary;">Step 4 — Confirm it Installed</mark>

The terminal will show progress messages while the installer runs. When it finishes,\
CybaAgent is installed and will start communicating with the server automatically. The\
device should also appear in Asset Manager shortly afterwards.

You can close the terminal window at this point.

### <mark style="color:$primary;">Troubleshooting</mark>

* **"Permission denied”** — Make sure you included sudo at the start of the install  \
  command, and that you ran chmod +x ./CybaAgent first.
* **“No such file or directory”** — You're not in the folder containing the archive or the  \
  extracted binary. Run ls to check, then re-run the cd command in Step 2.
* **tar: command not found** — Install tar through your distribution's package manager  \
  (for example sudo apt install tar on Debian/Ubuntu or sudo dnf install tar on  \
  Fedora/RHEL).
* **Activation code rejected** — Double-check the code and make sure it starts with tt-.  \
  Copy and paste it rather than typing it to avoid mistakes.
* **Nothing happens / connection error** — Confirm the machine has internet access and  \
  that no firewall is blocking outbound HTTPS to cybaverse.cybaops.com.

### <mark style="color:$primary;">Need Help?</mark>

If the install still won't complete, contact our support team and include the full output\
shown in the terminal — that helps us identify the issue quickly.

Please contact <support@cybaops.help> for assistance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybaops.com/getting-started/onboarding/agent-deployment/cybaagent-linux.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
