Managing Astro Local Env

You're running Astro CLI locally and need to start, stop, or debug your Airflow environment. This handles both Docker mode (the default containers setup) and the newer standalone mode that runs Airflow 3 directly in a venv without Docker. The standout feature is the built-in Airflow API querying with `astro api airflow`, which lets you list DAGs, trigger runs, check task states, and filter results with jq without leaving your terminal. Also covers the reverse proxy for running multiple projects simultaneously and the usual troubleshooting moves when containers won't start or your venv gets corrupted. Pairs with the authoring and testing skills once your environment is actually running.

skills.sh installs: 1.6K
GitHub stars: 459
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add astronomer/agents --skill managing-astro-local-env --agent claude-code

Installs into .claude/skills of the current project.

Files

Astro Local Environment

This skill helps you manage your local Airflow environment using the Astro CLI.

Two modes: Docker (default, uses containers) and Standalone (Docker-free, uses a local venv — requires Airflow 3 + uv).

To set up a new project, see the setting-up-astro-project skill. When Airflow is running, use MCP tools from authoring-dags and testing-dags skills.

Start / Stop / Restart (Docker)

# Start local Airflow (webserver at http://localhost:8080)
astro dev start

# Stop containers (preserves data)
astro dev stop

# Kill and remove volumes (clean slate)
astro dev kill

# Restart all containers
astro dev restart

# Restart specific component
astro dev restart --scheduler
astro dev restart --webserver

Default credentials: admin / admin

Restart after modifying: requirements.txt, packages.txt, Dockerfile