Skip to main content
​
April 7, 2026

​
Faster startup and reliability improvements

AWS EC2 Runner · 20260407.1269Environment startup is 1-2 seconds faster. Automation trigger API calls now run in parallel instead of sequentially, and the devcontainer reconciler caches configuration reads in steady state, saving an additional ~130ms per cycle.

​
What else is in this release

  • Automation-triggered agent executions no longer get stuck in a waiting state when the agent attempts to ask for user input. The request is rejected immediately so the agent can proceed autonomously.
  • File watch self-healing now works correctly in all configurations. The discovery agent starts when watch mode is enabled, and the path denylist updates after a denylisted file is unlinked and recreated.
  • BPF watch-only mode emits WATCH_WRITE and WATCH_MMAP events correctly when untouchable mode is off.
  • Fixed a runner manager startup panic when multiple managed runners run in the same process.
  • Updated VM images for AWS runners.
  • Security dependency update: go-jose/v4 bumped to v4.1.4 (fixes GHSA-78h2-9frx-2jm8).
​
April 2, 2026

​
Warm pools now GA!

AWS EC2 Runner · 20260402.401Warm pool toggle in project prebuild settingsWarm pools keep pre-initialized EC2 instances running from the latest prebuild snapshot. When you create an environment, Ona claims an instance that is already running with the snapshot loaded instead of launching a new one. Startup drops from minutes to around 10 seconds.Enable warm pools per environment class in your project’s prebuild settings. The runner dynamically scales the pool between 0 and your configured maximum (up to 10 in the dashboard, up to 20 via the CLI) based on demand. It also handles replenishment and automatic snapshot rotation when new prebuilds complete.Requires an Enterprise plan. Currently available on EC2 runners only. See the warm pools documentation for prerequisites and setup instructions.

​
Infrastructure upgrade required

This release requires a CloudFormation stack update.
This upgrade causes approximately 10-15 minutes of downtime where environments are unreachable. Schedule it during a low-usage period.
The full update takes ~30 minutes. Your data and environments are preserved. Running environments reconnect automatically after the update completes.

​
Before you upgrade

  1. Note your Prometheus metrics settings. The upgrade resets them. You will re-enter them afterward. See Monitoring and Metrics.
  2. Internet Gateway users (no NAT gateway): You must set Assign Public IP to Fargate Tasks to true during the CloudFormation parameter review step.
  3. Templates from January 2025 or earlier: Either stop and discard existing environments before upgrading, or add port 22 to your security group first.

​
Upgrade steps

  1. Go to Settings > Runners and select your runner
  2. Open the three-dot menu and click Upgrade runner
  3. Follow the dialog to update your CloudFormation stack
  4. Re-enter your Prometheus metrics settings after the update completes
Full walkthrough: Upgrade runner infrastructure

​
What else is in this release

  • Fargate replaces EC2 instances for the runner service. No more AMI allowlisting or update bottlenecks.
  • MemoryDB persists Ona agent conversations in real time, with S3 as a durable backup. This is a new billable AWS resource in your account.
  • Runner sizing lets you choose between small and large infrastructure via a CloudFormation parameter. Select large if your organization runs many concurrent agent sessions.
  • Runner update windows let you control when your runner applies updates. Set a maintenance window to avoid disruptions during peak hours.
  • Environment startup is faster thanks to earlier Docker socket activation and optimized content initialization.
  • Runner updates no longer cause brief user disconnects. The proxy now runs as a separate service.