CLI unusable: `list` empty on Stable & Crashes/Slow on Beta

[Tjomas]

[Windows/PowerShell] CLI unusable: list empty on Stable & Crashes/Slow on Beta

Description:
I am experiencing critical issues with the Passbolt CLI on Windows using PowerShell. I have identified two distinct sets of blocking problems depending on the version used, leaving me with no working solution.

1. Stable Version: Empty Columns
When running passbolt list resource or passbolt list folder, authentication works and rows are returned, but essential columns like Name and ID are empty.

• Actual result: Table renders and row count seems correct (approx. 50 items), UUIDs for parents are visible, but Name/ID columns are blank strings.
• Impact: CLI is unusable for scripting (cannot resolve resource names for SSH autocompletion).

2. Beta Version: Performance & Crashing
I attempted to update to the Beta version to see if it resolved the issue, but encountered new blockers:

• Performance: The CLI is incredibly slow compared to the stable version.
• Crashing: The list command aborts completely.
• Hypothesis: It appears there is a specific resource in my Passbolt account that causes the CLI to fail. Instead of skipping the malformed/problematic resource, the entire process terminates.

Steps to Reproduce:

1. Install Passbolt CLI (Stable or Beta) on Windows.
2. Configure valid authentication.
3. Run passbolt list resource.

Environment:

• OS: Windows (running in PowerShell)
• Shell: PowerShell
• Stable Version tested: (Insert version here)
• Beta Version tested: (Insert version here)

Business Impact / Conclusion:
Please note that in its current state, the CLI is not suitable for professional use. As a paying Passbolt Cloud customer, the availability of a robust CLI was a decisive factor in our choice of Passbolt over other solutions.

Currently, there is effectively no functioning version available for us on Windows:

• The Stable version outputs incomplete data.
• The Beta version is too slow and crashes on list operations.

This blocks our planned automation workflows (e.g., SSH integration) completely. We kindly ask for a fix or a workaround.

[speatzle]

Hi, go-passbolt-cli and go-passbolt are community Projects which i maintain in my spare time. There is a Disclaimer in the respective Repositories Readme files.

With Passbolt V5 there were big changes in regard to resource metadata, which needed many modifications to keep the CLI going. These still need some time to work out. On-Premise installations can opt into keeping v4 resources for now as the workaround.

I can't really help you since your description (which seems AI Generated) is lacking the version numbers and a debug log of the crash.

There is a newer version than the latest beta here, which I haven't been able to release yet. This has a few extra bug fixes, which has resolved all issues besides slowness for other people:
https://github.com/passbolt/go-passbolt-cli/actions/runs/19029616319

To address the slowness, there are PRs being worked on that add some additional caching, but due to the additional encryption, it will always be slower than the old CLI.

[Tjomas]

Downgrading to v4 isn't an option for cloud users.

The last beta.2 is from August. The beta itself is not suitable for a production environment. Therefore, the usage of unknown artifacts is even more risky.

The Passbolt API 5.0.0 release is from Apr 10.
The CLI is actively advertised as a tool to manage Passbolt and i thought that the CLI is maintained by Passbolt itself.
If not, i am sorry for the misunderstanding, but this should be clearly communicated during the cloud registration process.

Thanks for your help.

[speatzle]

Just to be clear, I don't work for Passbolt. I think @stripthis can help if you have any questions for Passbolt.

Downgrading to v4 isn't an option for cloud users.

With on Premise Installations v5 Servers can still use v4 Resources, the Admin just needs to set that Preference. Please check if your Cloud Admin can't switch to V4 Resources. For On Premise Installation it looks like this:

-

The last beta.2 is from August. The beta itself is not suitable for a production environment. Therefore, the usage of unknown artifacts is even more risky.

The Releases, Beta Releases and the Linked Artifact are all built by the same CI in the same way.

The Passbolt API 5.0.0 release is from Apr 10.

The Server Release v5.0.0 Still used v4 Resources.
With Server 5.1.0 in May the Beta for v5 Resources was added.
Server v5.4.0 promoted v5 Resources to stable in August with a warning that integrations may not work with v5 Resources.
v4 Resources are Currently Still supported and can Easily be Migrated.

Currently the the Old CLI Builds have Better Performance with v4 Resources than the Beta Builds. The Betas are only if you need to use v5 Resources. But i am planning on promoting the Latest Build to Stable any Day now since all Big Issues besides slowness have been worked out.