# Install labctl with Homebrew, Nix CLI tool for interacting with iximiuz labs and playgrounds. Version 0.1.101 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#labctl. ## Install ```sh sudo av install brew:labctl ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install labctl ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#labctl ``` Evidence: nixpkgs package indexes: pkgs/by-name/la/labctl/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:labctl - **Package manager:** Homebrew - **Version:** 0.1.101 - **Source summary:** CLI tool for interacting with iximiuz labs and playgrounds - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T21:02:15Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - labctl (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.1.101 ## Project history and usage labctl is the command-line client for iximiuz Labs, a hands-on learning platform for Linux, containers, Kubernetes, networking, and DevOps playgrounds. It starts, lists, stops, destroys, and connects to remote playground environments from a local terminal. Its history is tightly coupled to iximiuz Labs rather than to a broad standalone ecosystem, so the package history is best understood as the CLI surface of a hosted microVM playground service. ### Project history The labctl repository documents the tool as a way to start remote microVM playgrounds from the command line. The README lists Linux, Docker, Kubernetes, networking, and other DevOps playground types and describes those environments as ephemeral and disposable. As the iximiuz Labs playground model evolved, labctl accumulated commands for browser opening, SSH access, IDE integration, public web terminals, HTTP exposure, port forwarding, and lifecycle management. ### Adoption history Adoption is mostly iximiuz Labs users who prefer terminal access over a browser-only workflow. The README documents both the iximiuz install script and Homebrew installation on macOS and Linux, putting labctl into ordinary package-manager workflows despite its service-specific nature. The public release page shows frequent 0.1.x releases, including additions for playground status, wait behavior, regions, IDE integration, and readiness handling. ### How it is used A typical workflow is `labctl auth login`, followed by `labctl playground start docker`, `labctl playground start k3s --open`, or `labctl ssh `. The CLI can also expose shell sessions, forward ports, open local IDEs, and destroy playgrounds when finished. Credentials and SSH material are stored under the iximiuz labctl configuration and SSH paths documented in the package curation, which makes the Homebrew package both a CLI and a local session manager for remote training machines. ### Why package nerds care labctl is a useful example of a modern package-manager CLI whose main value is not local computation but authenticated orchestration of disposable remote environments. It turns a hosted learning product into scriptable terminal infrastructure. For DevOps learners and authors, that means reproducible playgrounds can be launched, connected to, exposed, and torn down with commands rather than browser clicks. ### Timeline - 2020s: iximiuz Labs popularized hands-on Linux, container, Kubernetes, and networking playgrounds. - 2020s: labctl became the command-line access layer for starting and connecting to those playgrounds. - 2025: The Playgrounds 2.0 write-up described labctl as an SSH access path for microVM-based playgrounds. - 2026: v0.1.x releases added region, readiness, IDE, and playground lifecycle improvements. ### Related projects - iximiuz Labs playgrounds are the hosted service labctl controls. - Firecracker is relevant to the platform architecture because iximiuz Labs describes its playground machines as microVMs. - VS Code Remote SSH, Cursor, Windsurf, and SSH tooling are adjacent user-facing integrations documented by labctl. ### Sources - - - - - ## Security Notes No matching local secret-handling manifest was found for labctl. Nucleus package metadata is still published here so future coverage has a stable package URL. ## 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: ~/.iximiuz/labctl/config.yaml ## Credential files - Unix: ~/.iximiuz/labctl/config.yaml, ~/.ssh/iximiuz_labs_user ## Other Package-Manager Records - Nix - labctl: normalized package name match | nixpkgs package indexes: pkgs/by-name/la/labctl/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/labctl.yml](https://github.com/mxcl/pkgdb/blob/main/combined/labctl.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