LFX CLI

lfx is a developer-facing command-line tool for authenticating with the Linux Foundation's LFX platform and making authenticated API calls, following the same interaction model as the gh CLI (lfx auth login → lfx auth token).

Installation

curl -sSL https://linuxfoundation.github.io/lfx-cli/install.sh | sh

This downloads the correct prebuilt binary for your OS/architecture from the Releases page, verifies its checksum, and installs it to /usr/local/bin (or ~/.local/bin if that's not writable). Set LFX_CLI_VERSION to pin a specific release, or LFX_CLI_INSTALL_DIR to override the install location. This works out of the box on macOS and Linux, and on Windows under Git Bash or WSL.

On native Windows (PowerShell), use install.ps1 instead, since Windows has no sh interpreter by default:

irm https://linuxfoundation.github.io/lfx-cli/install.ps1 | iex

This installs to %LOCALAPPDATA%\lfx-cli\bin by default (or LFX_CLI_INSTALL_DIR if set), and honors LFX_CLI_VERSION the same way as install.sh.

Alternatively, install with Go:

go install github.com/linuxfoundation/lfx-cli/cmd/lfx@latest

Usage

# Log in via the Auth0 Device Code flow.
lfx auth login

# Show the current authentication status.
lfx auth status

# Print a valid access token (e.g. for use in scripts or other tools).
lfx auth token

# Log out and remove stored credentials.
lfx auth logout

# Make an authenticated call to an LFX platform API endpoint.
lfx api '/my-grants?v=1&object_type=project'
lfx api /projects --field name=example   # auto-promotes to POST
lfx api -X PUT /projects/123 --input - -H "If-Match: <ver>" < input.json  # Content-Type: application/json is added automatically

Credentials (refresh token, cached access token) are stored in your operating system's credential store by default (macOS Keychain, Windows Credential Manager, Linux Secret Service/KWallet/pass). Which of these is actually used can vary between invocations on the same machine (e.g. Secret Service reachable in one shell session but not another); pass --backend to pin it to one explicitly (see lfx auth backends for the available names). Once a login has pinned a backend, later commands must pass the same --backend value. Pass --insecure-storage to instead store credentials in a plain, unencrypted, owner-only file, at the cost of weaker protection for the stored tokens. On Windows, this owner-only mode relies on inherited directory permissions rather than a real ACL, since Go's Chmod(0600) maps to the read-only attribute there rather than restricting access to the current user.

lfx auth login --insecure-storage
lfx auth login --backend=keychain

Run lfx --help or lfx <command> --help for full details on any command.

Development

make build   # Build ./bin/lfx
make check   # Format, vet, and lint
make test    # Run tests

See AGENTS.md for detailed development workflows and architecture notes.