# Install astro with Homebrew, winget To build and run Airflow DAGs locally and interact with the Astronomer API. Version 1.43.1 via Homebrew; verified 2026-07-02. ## Install ```sh sudo av install brew:astro ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install astro ``` Evidence: local Homebrew formula metadata ### Windows - winget (92%): ```sh winget install --id Astronomer.Astro -e ``` Evidence: Windows Package Manager source index: Astronomer.Astro from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:astro - **Package manager:** Homebrew - **Package manager page:** - **Version:** 1.43.1 - **Source summary:** To build and run Airflow DAGs locally and interact with the Astronomer API - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-07-02T16:40:03Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - astro (cli) - astro (alias) ## Dependencies - podman ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 1.43.1 - Package-manager updated: 2026-07-02 - Local data: ok - Upstream repository: https://github.com/astronomer/astro-cli - Upstream latest detected: v1.43.1 (current) ## Project history and usage Astro CLI is Astronomer's command-line interface for developing Apache Airflow projects locally and deploying them to Astronomer products. In package-manager terms it is the small Go binary that turns a directory of DAGs, requirements, Dockerfile, and Astro project metadata into a repeatable local Airflow environment and a deployable unit. ### Project history The CLI grew out of Astronomer's Airflow platform tooling and was distributed publicly as the astro-cli repository. Its README describes it as a command-line interface for data orchestration that works with Astronomer products, and its release notes mark all releases before 1.0.0 as beta. Version 1.0.0 was published in May 2022 as the converged Astro CLI release, while Astronomer's own CLI release notes document the transition from older astrocloud command names to the standardized astro login, astro logout, astro dev init, and deployment commands. The tool's center of gravity is local developer experience for Airflow: astro dev init creates a project skeleton, astro dev start runs the Airflow stack locally in containers, and deployment/workspace commands talk to Astronomer APIs. Later releases added Windows package-manager support, organization and context switching, richer config commands, and deployment inspection/logging features. ### Adoption history Homebrew packages the CLI as astro and the upstream README documents brew install astro for macOS, winget install -e --id Astronomer.Astro for Windows, and an install.astronomer.io shell installer for Linux. That multi-channel distribution matters because Airflow teams often need the same CLI in laptops, CI, and enterprise Windows workstations. Adoption is tied to Astronomer's hosted Astro and Astronomer Software/Private Cloud products rather than being a general Airflow replacement. The CLI became the user-facing packaging point for Astronomer's Airflow workflow: initialize a project, run it locally, test DAGs, and deploy to a managed Deployment. ### How it is used Typical package usage starts with brew install astro, then astro dev init in an empty project directory and astro dev start to build and run local Airflow containers. The generated project includes dags, tests, Dockerfile, requirements.txt, packages.txt, plugins, include, and an .astro/config.yaml file for project settings. Astro CLI stores project settings in .astro/config.yaml and global settings in a user-level Astro config file. Astronomer documentation notes project-level settings such as webserver and Postgres ports and says global configuration is stored centrally with the executable, for example under ~/.astro/config.yaml on Unix-like systems. Login-related context and cached identity state also live in the user-level config. ### Why package nerds care For package nerds, astro is a good example of a cloud-product CLI that still earns a normal package-manager slot because its heavy dependencies are external services and container runtimes, not vendored platform SDKs. The package is mostly a single command surface, but it orchestrates Docker/Podman, generated project files, Airflow commands, and authenticated API calls. The formula is also notable because it has to track a fast-moving SaaS CLI while preserving enough compatibility for CI images and developer laptops. Astronomer's docs warn that backward compatibility is guaranteed only between matching minor versions of the platform and CLI, which makes package version selection operationally important. ### Timeline - 2021: Public beta-era Astro CLI releases were already being published from the astronomer/astro-cli repository. - 2022-05-27: Astro CLI v1.0.0 was published as the converged v1 release. - 2022-06-28: Astronomer documented Astro CLI 1.2.0 and the standardized astro command names. - 2022-10-27: Astro CLI v1.6.0 added documented winget installation support for Windows. - 2026: Astronomer documentation continues to position Astro CLI as the command reference and local development tool for Astro projects. ### Related projects - Apache Airflow is the workflow engine Astro CLI packages around for local and managed development. - Docker or Podman provide the local container runtime used by astro dev commands. - Astronomer Astro and Astronomer Software/Private Cloud are the platform targets for deployment and context commands. ### Sources - - - - - - ## Security Notes No matching local secret-handling manifest was found for astro. 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: .astro/config.yaml, ~/.astro/config.yaml - Windows: .astro/config.yaml, %USERPROFILE%\.astro\config.yaml ## Credential files - Unix: ~/.astro/config.yaml - Windows: %USERPROFILE%\.astro\config.yaml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** astro - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - winget - Astronomer.Astro: normalized package name match | Windows Package Manager source index: Astronomer.Astro from https://cdn.winget.microsoft.com/cache/source.msix ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [podman](https://www.automicvault.com/pkg/brew/podman/) - Runtime dependency declared by Homebrew. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [amber](https://www.automicvault.com/pkg/brew/amber/) - Shares av.db curated category or tags: cli, developer-tools, web-framework. - [angular-cli](https://www.automicvault.com/pkg/brew/angular-cli/) - Shares av.db curated category or tags: cli, developer-tools, javascript. - [babel](https://www.automicvault.com/pkg/brew/babel/) - Shares av.db curated category or tags: cli, developer-tools, javascript. - [bower](https://www.automicvault.com/pkg/brew/bower/) - Shares av.db curated category or tags: cli, developer-tools, javascript. - [chalk-cli](https://www.automicvault.com/pkg/brew/chalk-cli/) - Shares av.db curated category or tags: cli, developer-tools, javascript. - [closure-compiler](https://www.automicvault.com/pkg/brew/closure-compiler/) - Shares av.db curated category or tags: cli, developer-tools, javascript. - [cot](https://www.automicvault.com/pkg/brew/cot/) - Shares av.db curated category or tags: cli, developer-tools, web-framework. - [cppcms](https://www.automicvault.com/pkg/brew/cppcms/) - Shares av.db curated category or tags: cli, developer-tools, web-framework. - [astro](https://www.automicvault.com/pkg/npm/astro/) - Same normalized package name appears in another local ecosystem. Shared terms: astro, web. - [fastapi](https://www.automicvault.com/pkg/brew/fastapi/) - Local package facts share a topical domain. Shared terms: api, cli, developer, developer-tools, framework. - [astro](https://www.automicvault.com/pkg/npm/astro/) - Same normalized package name in another local ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/astro.yml](https://github.com/automic-vault/db/blob/main/combined/astro.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph