> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/getting-started-with-weka/weka-cli-overview.md). # New WEKA CLI (formerly wekactl) overview Explore wekactl capabilities, supported connection models, and links to administration, migration, and command reference topics. Explore wekactl, the modern WEKA command-line interface for cluster administration. It supports most legacy `weka` CLI operations and runs on Linux, macOS, and Windows. Starting with WEKA 6.0, wekactl is the default CLI. Running `weka` on a WEKA server invokes wekactl. Use wekactl from a workstation for day-to-day remote administration. Run it locally on a WEKA server when a command requires the local agent. ## Key capabilities * **Cross-platform administration:** Manage clusters directly from supported Linux, macOS, and Windows workstations. * **Version independence:** Use one binary to manage clusters across supported WEKA versions. * **Flexible output:** Use human-readable tables or machine-readable formats for automation. * **Secure connectivity:** Use TLS for network connections and isolated connection profiles. * **Remote access:** Connect directly, through an SSH bastion, or through a WEKA Operator deployment. ## Considerations * **Local-agent commands:** Commands that use the local agent require a WEKA server. These include `local`, `agent`, `diags`, `version`, `mount`, `umount`, and most `driver` commands. Running wekactl from a workstation gives you 23 command groups. Running it on a cluster server gives you all 28. * **Remote quota management:** Directory-based quota management requires enabled data services. Otherwise, run the commands on a WEKA server. * **Profile compatibility:** wekactl profiles do not work with legacy CLI profiles. ## Continue with the CLI Choose the topic that matches your goal: * [Manage WEKA with new CLI](/getting-started-with-weka/weka-cli-overview/manage-weka-with-new-cli.md): Install and use wekactl. Configure profiles, output, TLS, and remote connections. * [Migrate from legacy WEKA CLI](/getting-started-with-weka/weka-cli-overview/migrate-from-legacy-weka-cli.md): Update scripts and automation for CLI behavior changes. * [CLI reference guide](/getting-started-with-weka/weka-cli-overview/cli-reference-guide.md): Look up commands, subcommands, flags, and environment variables. --- # 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.weka.io/getting-started-with-weka/weka-cli-overview.md?ask=&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.