> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/code/devops-cli/installing-flosum-devops-cli-extension.md).

# Installing Flosum DevOps-CLI Extension

{% hint style="warning" %}

#### Known Issues: Required Update

**An update is required.** The current release of Flosum DevOps requires the latest versions of the Flosum CLI (**@flosum/cli** package) and the **Flosum DevOps-CLI Extension**. Earlier CLI releases do not support topologies and cannot work with a DevOps tenant that uses them, so existing installations must be updated.

**Node.js 22 is required.** On **Node.js 24**, the install and update commands appear to succeed but leave you on an earlier release. Move to Node.js 22 before installing or updating.
{% endhint %}

{% hint style="success" %}

#### Operating System Compatibility

**Flosum CLI** and **Flosum DevOps-CLI Extension** are compatible with the following operating systems:

* **macOS**
* **Linux**

These tools are currently not designed to work with Windows.
{% endhint %}

## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview

This article explains how to install the Flosum DevOps-CLI Extension for Visual Studio Code (VS Code). The extension helps you work on DevOps projects by providing direct access to Flosum CLI commands in VS Code through an easy-to-use interface. For more information about the DevOps CLI and how to use it, see the following articles.

* [Overview of DevOps CLI in VS Code](/devops/code/devops-cli/overview-of-devops-cli-in-vs-code.md)
* [Using DevOps CLI in VS Code](/devops/code/devops-cli/using-devops-cli-in-vs-code.md)

The extension runs the Flosum CLI, which is installed separately. Install the Flosum CLI first, then install the extension.

* [Installing Flosum CLI Node.js Package](/devops/code/devops-cli/installing-flosum-cli-node.js-package.md)

## Prerequisites

{% stepper %}
{% step %}

### Flosum CLI

The Flosum CLI must be installed before the extension can be used. It has its own prerequisites, including a specific version of Node.js and a C++ build toolchain.

1. Complete the installation described in the following article.
2. Confirm that `flosum --version` returns a version number, and make a note of it.

{% hint style="info" %}
Full instructions, prerequisites, and troubleshooting for the CLI are in a separate article.

* [Installing Flosum CLI Node.js Package](/devops/code/devops-cli/installing-flosum-cli-node.js-package.md)
  {% endhint %}
  {% endstep %}

{% step %}

### Visual Studio Code

1. Confirm you are running **Visual Studio Code** version **1.106.0** or later.
2. Select **Help > Check for Updates** and install any available updates before you continue.
   {% endstep %}
   {% endstepper %}

## Installing DevOps-CLI Extension

{% stepper %}
{% step %}

### Install Flosum DevOps-CLI Extension

1. Launch VS Code.
2. Open the Extensions view by selecting the **Extensions** icon in the Activity Bar.
3. In the **Search** box, enter **Flosum DevOps-CLI Extension**.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FjGR5xDyis5ezBylmvu49%2FInstallDevopsCli-S02-01.png?alt=media&amp;token=9f2911e4-f88b-4890-8bc5-1cf1e61f2a73" alt="" width="563"><figcaption></figcaption></figure></div>
4. Click **Install** for the **Flosum DevOps-CLI Extension**.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FWw29sPdfHaWWqmyfwPXi%2FInstallDevopsCli-S02-02.png?alt=media&amp;token=5e02bec5-932c-4e71-96db-62088bec11df" alt="" width="563"><figcaption></figcaption></figure></div>
5. Click **Trust Publisher & Install** to confirm.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FMEithibOC6Vlb6T2MK18%2FInstallDevopsCli-S02-03.png?alt=media&amp;token=281575f9-9a20-4b0f-9f75-157e843808c2" alt="" width="563"><figcaption></figcaption></figure></div>
6. If the Flosum DevOps-CLI Extension is successfully installed, you will see the **Flosum** command palette launcher on the left side of the VS Code **Status Bar**.&#x20;

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FFDHpUxPYj3GCxrHvuaME%2FInstallDevopsCli-S02-04.png?alt=media&amp;token=cdbdbe71-40cc-43c3-9c74-2977691da516" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}

#### Flosum Command Palette

To access the **Flosum Command Palette**, ensure the **Status Bar** in VS Code is visible. Control its visibility through **View** > **Appearance** > **Status Bar**.
{% endhint %}
{% endstep %}

{% step %}

### Verify Both Are Current

1. In the **Extensions** view, confirm that the **Flosum DevOps-CLI Extension** shows no available updates.
2. In a terminal, compare the installed Flosum CLI against the latest published release:

   ```
   flosum --version
   npm view @flosum/cli version
   ```

{% hint style="warning" %}

#### Restart Visual Studio Code if flosum Is Not Found

If the terminal reports that `flosum` is not found, close **Visual Studio Code** completely and reopen it, then try again. Opening a new terminal tab does not work because **Visual Studio Code** only reads your **PATH** when it starts.
{% endhint %}

{% hint style="warning" %}

#### Keep Both Up to Date, but Do Not Compare Their Versions

The extension and the Flosum CLI are numbered independently. Their version numbers are not the same and are not meant to match, so check each one against its own source rather than against each other.

The Flosum CLI does not update itself, so it becomes outdated while the extension updates automatically through Visual Studio Code. An outdated CLI is most often caused by installing on a Node.js version other than 22, which installs an older release without reporting any errors. Older releases do not support current Flosum DevOps and will not work.
{% endhint %}
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>The Flosum launcher does not appear in the Status Bar</summary>

1. Select **View > Appearance > Status Bar** and confirm the **Status Bar** is turned on.
2. In the **Extensions** view, confirm that **Flosum DevOps-CLI Extension** is installed and enabled.
3. Reload the window by selecting **Developer: Reload Window** from the command palette.

</details>

<details>

<summary>The Flosum CLI is an older version than the one published</summary>

The extension and the CLI are numbered independently, so a difference between their version numbers is expected and is not a problem. Compare the CLI against the published release instead:

```
flosum --version
npm view @flosum/cli version
```

If `flosum --version` reports the lower number, the CLI is out of date.

1. Run `node --version` and confirm it reports **v22.x**.
2. If it does not, install **Node.js 22** as described in the CLI article.
3. Remove the existing CLI, reinstall it, then compare the two commands again.

{% hint style="info" %}
Installing the CLI on **Node.js 24** silently installs an older release without reporting an error. This is the most common reason the CLI becomes outdated.

* [Installing Flosum CLI Node.js Package](/devops/code/devops-cli/installing-flosum-cli-node.js-package.md)
  {% endhint %}

</details>

<details>

<summary>Extension commands fail even though the extension is installed</summary>

The extension runs the Flosum CLI, so a problem with the CLI appears as a failing extension command.

1. Open a terminal in **Visual Studio Code** and run `flosum --version`.
2. If the command is not found, close **Visual Studio Code** completely, reopen it, and run the command again. This resolves it in most cases, because the editor only picks up **PATH** changes when it starts.
3. If it is still not found, open a terminal outside **Visual Studio Code** and run the same command. A version number there means the editor is running with an outdated environment. No version number means the CLI is not installed correctly.
4. If the command reports a missing module, the CLI installation did not finish. Follow the troubleshooting steps in the CLI article.

</details>


---

# 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.flosum.com/devops/code/devops-cli/installing-flosum-devops-cli-extension.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.