> ## Documentation Index
> Fetch the complete documentation index at: https://docs.westyx.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Westyx CLI

> Manage secrets, configs, and feature flags from your terminal.

The `westyx` CLI is the unified command-line interface for the Westyx platform. Install it once
and use it across all your projects - on your local machine, in CI/CD pipelines, and on any
server.

<CardGroup cols={2}>
  <Card title="Installation" icon="download" href="/cli/installation">
    Linux, macOS, and Windows download instructions.
  </Card>

  <Card title="Getting started" icon="bolt" href="/cli/getting-started">
    Log in, set up your project, and run your first command.
  </Card>

  <Card title="Command reference" icon="book" href="/cli/reference">
    Full reference for every command and flag.
  </Card>

  <Card title="CI/CD" icon="gear" href="/cli/ci-cd">
    Use the CLI in automated pipelines with token-based auth.
  </Card>
</CardGroup>

## What you can do

<AccordionGroup>
  <Accordion title="Manage secrets, configs, and flags from the terminal">
    Read and write individual values without opening the browser. Every operation supports
    `--format=json` and `--format=plain` for easy scripting.

    ```bash theme={null}
    westyx secret get DB_PASSWORD --service=payments --format=plain
    westyx config set LOG_LEVEL debug --service=api
    westyx flag set new_checkout true --service=payments
    ```
  </Accordion>

  <Accordion title="Migrate from .env files">
    `westyx analyze` reads an existing `.env` file, classifies each entry as a secret, config,
    or feature flag, and writes a `.wx` file ready to push to Nexus.

    ```bash theme={null}
    westyx analyze .env
    westyx dev push
    ```
  </Accordion>

  <Accordion title="Run your app with injected Nexus values">
    `westyx dev run` starts any command with all Nexus values injected as environment variables.
    Scripts and profiles are defined in `.westyx/config` and committed to git.

    ```bash theme={null}
    westyx dev run           # starts default script
    westyx dev run dev       # hot reload
    westyx dev run test      # run tests
    ```

    Falls back to cached `.wx` values when Nexus is unreachable.
  </Accordion>

  <Accordion title="Developer WIF - no static API keys in your local env">
    `westyx dev setup` provisions short-lived Developer WIF credentials. The Nexus SDK in your
    app detects them automatically - no `api_key` needed in your local config.

    ```bash theme={null}
    westyx dev setup --service=my-api
    # start your app normally - the SDK picks up credentials automatically
    ```
  </Accordion>
</AccordionGroup>

## Current version

`v0.5.0` - shipped 2026-06-04

| Version | Commands added                                                      |
| ------- | ------------------------------------------------------------------- |
| v0.1.0  | `login`, `logout`, `version`, `tenant list/set`, `project list/set` |
| v0.2.0  | `analyze`, `dev push`                                               |
| v0.3.0  | `dev setup`, `dev pull`, `dev status`, `dev teardown`               |
| v0.4.0  | `dev run`                                                           |
| v0.5.0  | `secret get/set/list`, `config get/set/list`, `flag get/set/list`   |