# Install livekit-cli with Homebrew, Nix, winget Command-line interface to LiveKit. Version 2.18.2 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#livekit-cli. ## Install ```sh sudo av install brew:livekit-cli ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install livekit-cli ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#livekit-cli ``` Evidence: nixpkgs package indexes: pkgs/by-name/li/livekit-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - winget (92%): ```sh winget install --id LiveKit.LiveKitCLI -e ``` Evidence: Windows Package Manager source index: LiveKit.LiveKitCLI from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:livekit-cli - **Package manager:** Homebrew - **Version:** 2.18.2 - **Source summary:** Command-line interface to LiveKit - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T13:41:02+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - livekit-cli (alias) - lk (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 2.18.2 ## Project history and usage LiveKit CLI is the terminal interface for LiveKit projects. It packages common developer and operator workflows around LiveKit Cloud, self-hosted LiveKit servers, access tokens, rooms, egress, load testing, app templates, and agents. ### Project history The livekit/livekit-cli repository was created on May 10, 2021, shortly before LiveKit's public launch in July 2021. The CLI grew alongside LiveKit's open source SFU and SDK ecosystem as the project moved from realtime audio/video infrastructure toward a broader agent and voice-AI platform. LiveKit documentation describes the CLI, invoked as lk, as the primary interface for managing LiveKit Cloud projects, creating applications from templates, and deploying agents. The GitHub README also documents older core workflows such as token generation, room APIs, egress management, participant simulation, and load testing. ### Adoption history The CLI's adoption follows LiveKit's developer adoption rather than a separate ecosystem. As LiveKit became a self-hostable and managed realtime stack, the CLI became the practical bridge between package-manager installation and day-to-day project setup. By June 2024, LiveKit said its platform was used by more than 20,000 developers; the CLI sits in that workflow as a setup and management tool for both cloud projects and local/self-hosted testing. ### How it is used Developers install LiveKit CLI with Homebrew, a shell installer, winget, or source builds. The documented precedence order for command parameters is command-line flags, environment variables, local configuration files such as ./livekit.toml, and then default project configuration. The CLI can create access tokens, call LiveKit APIs, join rooms as a participant, publish demo media, start and manage egresses, run load tests, create app templates, authenticate to LiveKit Cloud, and deploy agents. ### Why package nerds care livekit-cli is a good example of a modern infrastructure CLI that is both a package-manager binary and a cloud control surface. Its aliases and package names matter because users may invoke either livekit-cli or lk depending on installation path and documentation vintage. For package maintainers, it combines typical Go CLI distribution with multimedia build considerations: the README notes audio and console subsystem dependencies around CGO, PortAudio, and WebRTC audio processing for source builds. ### Timeline - 2021-05-10: The livekit/livekit-cli repository was created. - 2021-07-07: LiveKit was publicly introduced as open source realtime audio/video infrastructure. - 2024-06-04: LiveKit reported more than 20,000 developers using the platform. - 2026-06-30: The livekit/livekit-cli repository showed active updates through GitHub metadata. ### Related projects - The CLI is related to the LiveKit server, LiveKit Cloud, LiveKit Agents, client SDKs, server SDKs, egress, ingress, SIP, and LiveKit app template repositories. ### Sources - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ./livekit.toml ## Credential files - Unix: ./livekit.toml ## Other Package-Manager Records - Nix - livekit-cli: normalized package name match | nixpkgs package indexes: pkgs/by-name/li/livekit-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - winget - LiveKit.LiveKitCLI: normalized package name match | Windows Package Manager source index: LiveKit.LiveKitCLI from https://cdn.winget.microsoft.com/cache/source.msix ## Combined YAML source View the package source record on GitHub. [combined/livekit-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/livekit-cli.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph