LabsThis feature is in Labs.
- Find and fix failures without switching tools. See each Deployment’s import errors and failed Dag runs in the sidebar, read the task logs in an editor tab, and hand the failure to Otto in one click.
- Work with an agent that knows Airflow. Otto reads and edits the files in your project, runs commands, and shows each file edit as a diff. By default, Otto asks for your approval before it changes anything.
Features
The extension adds an Astro view container to the activity bar, with four views, and an Otto chat that opens as an editor tab.
For Deployments and local projects that still run Airflow 2, the extension shows when support for that version ends and starts the upgrade to Airflow 3 with Otto. See Upgrade to Airflow 3.
How Astro for VS Code works with other Astronomer tools
- Otto: The chat in the editor runs the same Otto as
astro ottoin a terminal, with the same models, skills, memory, and permission rules. It doesn’t use GitHub Copilot or Cursor’s built-in models, and doesn’t require a Copilot subscription. - Astro CLI: The extension uses the Astro CLI for every action that changes state, including signing in, switching Workspaces, pushing code, and starting local Airflow. It doesn’t store credentials of its own. If you sign in with
astro loginin a terminal, the extension uses the same session, and the other way around. - Astro IDE: The Astro IDE is a browser-based workspace hosted on Astro. Astro for VS Code works in your own editor, with the files on your computer.
Requirements
- An Astro account.
- The Astro CLI.
- VS Code 1.95 or later, or Cursor.