## Summary **Batch B of Phase 3** of the H1 → front-matter migration (`DOCS-484`; parent `DOCS-477`), the editorial follow-up to Batch A (#28030). For the **124** hand-authored pages whose leading body H1 differed from the manifest nav label, this promotes the richer body H1 to the front-matter **page title** and drops the duplicate H1, while keeping the short manifest **label** as the sidebar entry. Policy agreed with the docs owner: - Short sidebar labels win. Duplicate sidebar labels are acceptable. - Identical **page titles** across two pages are not. On a collision, rename the non-generated page's title. ## Page-title collisions resolved Promoting the H1 created 4 page-title collisions; each is disambiguated by renaming the non-generated / secondary page (sidebar labels left unchanged): | page | sidebar label | body H1 | → page title | |------|---------------|---------|--------------| | `install/index.md` | Install | Installing Coder | **Install Coder in your infrastructure** | | `install/cli.md` | Coder CLI | Installing Coder | **Install the Coder CLI** | | `ai-gateway/clients/jetbrains.md` | JetBrains | JetBrains IDEs | **JetBrains** | | `workspace-access/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | Web IDEs *(kept — primary user guide)* | | `extending-templates/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | **Web IDEs in templates** | | `workspace-management.md` | Workspace Management | Workspaces | **Manage workspaces** *(vs generated `api/workspaces.md`)* | These titles are the only non-mechanical editorial calls in this PR. ## Deliberately excluded: generated pages `admin/security/audit-logs.md` and `admin/setup/configuration-reference.md` are `make gen` outputs (`auditdocgen` / `configdocgen`) that Phase 2 did **not** update, so a hand-added title would be reverted on the next generation. They're excluded here and need their generators taught to emit front matter first (Phase 2 pattern), tracked as `DOCS-631`. Batch A (#28030) had the same issue for three other generated pages; it has been corrected there too. ## Verification AI was the primary author of this PR (see disclosure below); per the [AI Contribution Guidelines](https://coder.com/docs/about/contributing/AI_CONTRIBUTING) here is the manual verification. - Promote = set front-matter `title` to the body H1 (or the disambiguated title above) and remove that one duplicate H1. No other body prose is reflowed. - Every added front-matter block parses as YAML; all files pass `pnpm check-docs` (markdownlint-cli2 + table formatter): `Summary: 0 error(s)`. - Removing the H1 orphaned one in-page fragment (`[MCP](#mcp)` in `ai-gateway/mcp.md`), now repointed. A cross-file fragment audit into the retitled pages found no real breakage. Anchor-change note Unlike Batch A (title unchanged, a rendered no-op), Batch B changes each page's effective title from the manifest label to the body H1, so the rendered H1 **anchor slug changes**. An audit of cross-file `.md#fragment` links into these pages surfaced no links that break as a result (the only hits were false positives against a still-present `## TLS & Reverse Proxy` heading). Same-file fragments are enforced by markdownlint MD051, which is green. ## Title casing (follow-up, DOCS-742) A follow-up commit puts the promoted titles into sentence case and removes leading gerunds (for example, `Managing workspace schedules` → `Manage workspace schedules`): 57 of the 120 titles changed, the other 63 were already compliant. Proper nouns and branded names (Coder Validated Architecture, JetBrains, File Browser, Dev Containers, Island), acronyms (API, CLI, IDE, MCP, OIDC, URL, UI, CI/CD), the Premium license tier, and maturity labels (Beta, Experimental) are preserved. The four `Nk-users` pages become `Reference architecture: up to N users` (lowercase, matching the CVA landing page's own usage); the CVA landing page keeps its branded title. `pnpm check-docs`: `Summary: 0 error(s)`. Linear: DOCS-484, DOCS-742 > This PR was created with AI assistance (Coder Agents).
80 lines
2.2 KiB
Markdown
80 lines
2.2 KiB
Markdown
---
|
|
title: Install the Coder CLI
|
|
---
|
|
|
|
A single CLI (`coder`) is used for both the Coder server and the client.
|
|
|
|
We support two release channels: mainline and stable - read the
|
|
[Releases](./releases/index.md) page to learn more about which best suits your team.
|
|
|
|
## Download the latest release from GitHub
|
|
|
|
<div class="tabs">
|
|
|
|
## Linux/macOS
|
|
|
|
Our install script is the fastest way to install Coder on Linux/macOS:
|
|
|
|
```sh
|
|
curl -L https://coder.com/install.sh | sh
|
|
```
|
|
|
|
Refer to [GitHub releases](https://github.com/coder/coder/releases) for
|
|
alternate installation methods (e.g. standalone binaries, system packages).
|
|
|
|
## Windows
|
|
|
|
If you plan to use the built-in PostgreSQL database, ensure that the
|
|
[Visual C++ Runtime](https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist#latest-microsoft-visual-c-redistributable-version)
|
|
is installed.
|
|
|
|
Use [GitHub releases](https://github.com/coder/coder/releases) to download the
|
|
Windows installer (`.msi`) or standalone binary (`.exe`).
|
|
|
|

|
|
|
|
Alternatively, you can use the
|
|
[`winget`](https://learn.microsoft.com/en-us/windows/package-manager/winget/#use-winget)
|
|
package manager to install Coder:
|
|
|
|
```ps1
|
|
winget install Coder.Coder
|
|
```
|
|
|
|
</div>
|
|
|
|
To start the Coder server:
|
|
|
|
```sh
|
|
coder server
|
|
```
|
|
|
|

|
|
|
|
To log in to an existing Coder deployment:
|
|
|
|
```sh
|
|
coder login https://coder.example.com
|
|
```
|
|
|
|
## Download the CLI from your deployment
|
|
|
|
> [!NOTE]
|
|
> Available in Coder 2.19 and newer on macOS and Linux clients only.
|
|
|
|
Every Coder server hosts CLI binaries for all supported platforms. You can run a
|
|
script to download the appropriate CLI for your machine from your Coder
|
|
deployment.
|
|
|
|

|
|
|
|
This script works within air-gapped deployments and ensures that the version of
|
|
the CLI you have installed on your machine matches the version of the server.
|
|
|
|
This script can be useful when authoring a template for installing the CLI.
|
|
|
|
### Next up
|
|
|
|
- [Create your first template](../tutorials/template-from-scratch.md)
|
|
- [Control plane configuration](../admin/setup/index.md)
|