Ctrlk
Customer Support
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Installing Flosum DevOps-CLI Extension

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.

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.

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.

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

Prerequisites

1

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.

Full instructions, prerequisites, and troubleshooting for the CLI are in a separate article.

2

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.

Installing DevOps-CLI Extension

1

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.

  4. Click Install for the Flosum DevOps-CLI Extension.

  5. Click Trust Publisher & Install to confirm.

  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.

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.

2

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:

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.

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.

Troubleshooting

The Flosum launcher does not appear in the Status Bar

  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.

The Flosum CLI is an older version than the one published

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:

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.

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.

Extension commands fail even though the extension is installed

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.

PreviousInstalling Flosum CLI Node.js Package
NextUsing DevOps CLI in VS Code

Last updated

Was this helpful?