Additional improvements
- When you add the first IP address range to your organization's IP access list, the Astro API now rejects the request with a 400 Bad Request error if your current IP address falls outside the submitted ranges, which prevents you from accidentally locking yourself out.
Also shipped Jun 17, 2026Astronomer in June 2026 →
Replit is now available in Claude
Replit is now integrated directly into Claude, allowing users to design applications in Claude and build them in Replit within a single workflow.
Kilo Code + OpenRouter: Setup, Model Routing, and Free Models
Kilo Code now supports OpenRouter, enabling users to route requests across over 300 models with provider failover.
How to Use OpenAI Codex CLI with OpenRouter
The OpenAI Codex CLI can now be configured to route requests through OpenRouter for usage tracking and provider failover.
Australia Endpoint Now Generally Available
The Deepgram Australia endpoint ( api.au.deepgram.com ) is now generally available for customers requiring data processing within Australia.
Artifacts - Manage Artifacts from the Cloudflare dashboard
You can now configure Artifacts namespaces, repos, and tokens directly from the Cloudflare dashboard. Artifacts is Git-compatible storage that lets you store repos on Cloudflare and interact with them using standard Git workflows.
AI credit usage API for Enterprise customers
Enterprise customers can now access AI credit usage data programmatically via the new AI usage credit API.
More from AstroEvery Astro release →
Review code with Otto
You can now use Otto to review your Airflow code automatically when you open a pull request or merge request. The Otto review action posts a sticky summary comment, adds inline comments where it finds issues, and offers commit suggestions where a concrete fix is available.
Investigate Dag failures with Otto
You can now use Otto to investigate Dag failures on Astro from the Astro UI, Astro alerts, or the Astro API. Each investigation produces a structured diagnosis with a root cause type, severity, suggested fix, and a checklist of Dag- and task-level checks, drawing on Airflow, Astro, and Astro Observe context.
Dag-level access control is generally available
Dag-level access control is now generally available. You can assign roles scoped to individual Dags within a Deployment to enforce least-privilege security and enable multiple teams to collaborate in a single Deployment without exposing Dags across team boundaries.
Enable Sub-Second Pipelines
You can now enable Sub-Second Pipelines on Airflow 3.2+ Deployments that use the Astro executor . Sub-Second Pipelines pair the Astro executor with a dedicated event-driven Event Scheduler that picks up and dispatches API-triggered Dag runs in under a second and sustains approximately 1,000 Dag runs per minute, where the Celery executor queues and falls...
Additional improvements
- Updated Astro infrastructure to improve reliability and performance.
New Deployment analytics experience
Astro now offers a new version of the Deployment analytics experience with expanded Airflow visibility, including API server and webserver metrics, Dag processor coverage, Kubernetes executor and KubernetesPodOperator coverage, parse time, and richer per-status and per-component breakdowns.
Test against an existing Deployment in the Astro IDE
You can now test code in the Astro IDE against an existing Astro Deployment in your Workspace, instead of only an ephemeral test Deployment. Testing against an existing Deployment reuses its configuration, connections, and resources, and skips provisioning a new environment.
Try the new Astro experience
Astro's navigation now gives you a single view across your entire Organization instead of a single Workspace. Deployments, Dags, and Astro IDE projects all appear across Workspaces in one view, with Workspace context on every row. Filter to a specific Workspace when you need to, or work from the full picture across your Organization.