fcakyon/claude-codex-settings / plugins/hetzner-skills/skills/hetzner-deploy
hetzner-deploy
VerifiedThis skill should be used when user asks to "deploy to Hetzner", "create Hetzner server", "manage Hetzner Cloud", "hcloud CLI", or works with Hetzner Cloud infrastructure including servers, networks, firewalls, load balancers, DNS zones, and volumes.
references/getting-started/setup.md
View on GitHub<!--
---
date: "2026-09-07"
date_changed: "2026-09-07"
title: "Installing the hcloud CLI"
tags: []
language: "en"
description: ""
docs_type: ["getting_started"]
product_category: ["Integrations"]
translation: ["Integrations", "CLI", "Tutorials", "Installing the hcloud CLI"]
scrape_type: "whole"
priority: 100
---
-->
# Setup the hcloud CLI
This tutorial will guide you through the process of setting up the hcloud CLI on your local machine.
## Prerequisites
Before you begin, ensure you have the following:
- A [Hetzner Console account](https://console.hetzner.com).
## 1. Install the hcloud CLI
### 1.1 Manual installation
You can download pre-built binaries from our [GitHub releases](https://github.com/hetznercloud/cli/releases).
Install them by extracting the archive and moving the binary to a directory in your `PATH`.
On a 64-bit Linux system, it could look something like this:
```bash
curl -sSLO https://github.com/hetznercloud/cli/releases/latest/download/hcloud-linux-amd64.tar.gz
sudo tar -C /usr/local/bin --no-same-owner -xzf hcloud-linux-amd64.tar.gz hcloud
rm hcloud-linux-amd64.tar.gz
```
### 1.2 Installation using Go
If you have Go installed, you can also install hcloud CLI from source using the following command:
```bash
go install github.com/hetznercloud/cli/cmd/hcloud@latest
```
> [!NOTE]
> Binaries built with Go will not have the correct version embedded.
> [!NOTE]
> Both of the above installation methods do not provide automatic updates. Please make sure to keep your installation up to date manually.
### 1.3 Installation using .deb package (Debian/Ubuntu)
> [!WARNING]
> Debian packages are experimental and might change or break in the future.
On Debian and Ubuntu-based distributions, you can install the hcloud CLI using the `.deb` package:
1. Download the latest `.deb` package from the [GitHub releases page](https://github.com/hetznercloud/cli/releases/latest).
2. Install the package using `dpkg`:
```bash
# Download the package (replace with the actual version and architecture)
curl -sSLO https://github.com/hetznercloud/cli/releases/latest/download/hcloud-cli_<version>_linux_amd64.deb
# Install the package
sudo dpkg -i hcloud-cli_<version>_linux_amd64.deb
```
The `.deb` package includes shell completions for bash, zsh, and fish, as well as man pages.
### 1.4 Installation using .rpm package (Fedora/RHEL/CentOS)
> [!WARNING]
> RPM packages are experimental and might change or break in the future.
On Fedora, RHEL, CentOS, and other RPM-based distributions, you can install the hcloud CLI using the `.rpm` package:
1. Download the latest `.rpm` package from the [GitHub releases page](https://github.com/hetznercloud/cli/releases/latest).
2. Install the package using `rpm` or `dnf`:
```bash
# Download the package (replace with the actual version and architecture)
curl -sSLO https://github.com/hetznercloud/cli/releases/latest/download/hcloud-cli-<version>-1.x86_64.rpm
# Install using dnf (Fedora/RHEL 8+/CentOS 8+)
sudo dnf install hcloud-cli-<version>-1.x86_64.rpm
# Or install using rpm
sudo rpm -i hcloud-cli-<version>-1.x86_64.rpm
```
The `.rpm` package includes shell completions for bash, zsh, and fish, as well as man pages.
### 1.5 Installation using Homebrew
On Linux and macOS you can also install the hcloud CLI using Homebrew:
```bash
brew install hcloud
```
### 1.6 Installation on Windows using WinGet or Scoop
> [!WARNING]
> The WinGet and Scoop package entries are not maintained by Hetzner.
On Windows, you can install `hcloud` using WinGet (Windows Package Manager) or Scoop:
```bash
winget install HetznerCloud.CLI
```
```bash
scoop install hcloud
```
### 1.7 Using hcloud with Docker
Instead of installing hcloud on the host, you can also use our docker image at `hetznercloud/cli`.
```bash
docker run --rm -e HCLOUD_TOKEN="<your token>" hetznercloud/cli:latest <command>
```
If you want to use (and persist) your configuration, you can mount it to `/config.toml`:
```bash
docker run --rm -v ~/.config/hcloud/cli.toml:/config.toml hetznercloud/cli:latest <command>
```
The image is based on Alpine Linux, so a shell is available in the image. You can use it to run commands interactively:
```bash
docker run -it --rm --entrypoint /bin/sh hetznercloud/cli:latest
```
---
> [!WARNING]
> Some third-party package repositories may provide outdated versions of the hcloud CLI.
> Please consider one of the other installation methods.
## 2. (Optional) Setup auto-completion
hcloud CLI offers auto-completion for bash, zsh, fish and PowerShell. It is recommended to enable it for a better user experience.
### 2.1 Bash
To load completions into the current shell execute:
source <(hcloud completion bash)
In order to make the completions permanent, append the line above to
your .bashrc.
### 2.2 Zsh
If shell completions are not already enabled for your environment need
to enable them. Add the following line to your ~/.zshrc file:
autoload -Uz compinit; compinit
To load completions for each session execute the following commands:
mkdir -p ~/.config/hcloud/completion/zsh
hcloud completion zsh > ~/.config/hcloud/completion/zsh/_hcloud
Finally add the following line to your ~/.zshrc file, *before* you
call the compinit function:
fpath+=(~/.config/hcloud/completion/zsh)
In the end your ~/.zshrc file should contain the following two lines
in the order given here.
fpath+=(~/.config/hcloud/completion/zsh)
# ... anything else that needs to be done before compinit
autoload -Uz compinit; compinit
# ...
You will need to start a new shell for this setup to take effect.
### 2.3 Fish
To load completions into the current shell execute:
hcloud completion fish | source
In order to make the completions permanent execute once:
hcloud completion fish > ~/.config/fish/completions/hcloud.fish
### 2.4 PowerShell
To load completions into the current shell execute:
PS> hcloud completion powershell | Out-String | Invoke-Expression
To load completions for every new session, run
and source this file from your PowerShell profile.
PS> hcloud completion powershell > hcloud.ps1
## 3. Create a context
The hcloud CLI uses contexts to manage multiple Hetzner Cloud tokens and set configuration preferences.
First, you need to create an API token.
Follow the instructions in the [Hetzner Cloud documentation](https://docs.hetzner.com/cloud/api/getting-started/generating-api-token/) to create your project API token.
Once you have your token, you can create a context using the following command:
```bash
hcloud context create <context-name>
```
Ideally, keep the context name similar to the project name so you can easily identify it later.
When prompted, enter the API token you created earlier. Your context should now be created and activated.
## 4. Verify everything works
To verify that the hcloud CLI is working correctly, you can run the following command:
```bash
hcloud location list
```
You should see something like this:
```plaintext
ID NAME DESCRIPTION NETWORK ZONE COUNTRY CITY
1 fsn1 Falkenstein DC Park 1 eu-central DE Falkenstein
2 nbg1 Nuremberg DC Park 1 eu-central DE Nuremberg
3 hel1 Helsinki DC Park 1 eu-central FI Helsinki
4 ash Ashburn, VA us-east US Ashburn, VA
5 hil Hillsboro, OR us-west US Hillsboro, OR
6 sin Singapore ap-southeast SG Singapore
```
If you see this output, congratulations! You have successfully set up the hcloud CLI on your local machine.
If there are any problems, make sure you followed all steps of this tutorial correctly. If there still are problems,
you can reach out to our [Support](https://console.hetzner.com/support) to get help.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |