Changelog

​

Encode your expertise into slash commands

Slash commands in Ona

• Ensure everyone follows the same PR format or review process
• Capture your best reviewer’s approach in commands like /review-like-sarah
• Automate common tasks like /pr, /fix-ci-build, or /weekly-digest

​

Track agent progress with todos

Ona todo list

• See the plan at a glance instead of reading through detailed agent output
• Quickly spot when an agent might need steering without monitoring every action
• Add, remove, or modify todos mid-task to adjust your agent’s approach

​

Ona now supports AGENTS.md

Ona supports AGENTS.md

​

Keep momentum on any device from mobile to iPad

Ona supports AGENTS.md

​

Privacy-first coding agent inference with Bedrock and Vertex

Ona supported models

​

Sandboxed AI software development with Dev Container

DevContainer support

• Complete agent isolation: Each agent runs in its own Dev Container with OS level isolation, preventing cross-contamination between source control and projects.
• Ephemeral by design: Environments are created newly for each task (e.g. issue, bug, feature) and destroyed on completion, ensuring no persistent attack surface.
• Standardized environments: Dev Containers are defined in code and pre-configured with your exact dependencies and access credentials.

​

Standardized JetBrains plugin management via devcontainer.json

• Plugin installation: Specify plugin IDs from the JetBrains Marketplace for automatic installation.
• Team consistency: Guarantee the same set of plugins across every developer environment.
• Faster onboarding: Remove the manual step of plugin setup for new contributors.

{
	"name": "My Project",
	"image": "mcr.microsoft.com/devcontainers/base:ubuntu",
	"customizations": {
		"jetbrains": {
			"plugins": ["org.intellij.plugins.hcl", "com.intellij.kubernetes"]
		}
	}
}

​

HTTPS support for environment services via port sharing

• UI integration: Select https as the protocol in the port sharing dialog
• CLI support: Use --protocol https with gitpod environment port open to expose environment service ports securely.

• Applications with HTTPS-only redirects or policies
• Streaming APIs requiring secure connections

​

Support for multiple region-aware environment classes per project

• Configure up to 30 environment classes per project, providing built-in regional redundancy
• Set a default environment class while offering alternatives for user selection
• Avoid creating multiple projects for the same repository across different regions
• Benefit from automatic fallback options when a preferred environment class is unavailable

• Enhanced Resilience: Eliminate single points of failure with multiple region support in a single project
• User Flexibility: Users can select their preferred environment class through an intuitive UI
• Intelligent Fallback: When a selected environment class is unavailable, users receive informative error messages and alternative options
• Preference Persistence: The system remembers user preferences for future project launches
• Simplified Project Management: Reduce project proliferation by consolidating multi-region support

​

Archive & Auto-delete for Environments

• Automatically archive inactive environments after 7 days of inactivity
• Configure auto-deletion policies to remove archived environments after 1, 2, or 4 weeks
• Set organization-wide retention limits to ensure consistent storage management

• Two-stage lifecycle: Environments are archived first (reversible), then auto-deleted based on your preferences
• Flexible policies: Users can set preferences within organization-defined limits
• Bulk management: Delete all archived environments at once with safety controls
• Visual indicators: Archive badge shows when you have archived environments

​

Organization Secrets support

• Configure organization-wide secrets for all Environments in the organization
• Ensure consistent access to shared credentials and API keys for all team members

• Files: Secrets can be mounted as files for complex structures e.g. JSON.
• Environment Variables: Inject secrets as environment variables.

​

VPC endpoint support for Enterprise AWS runners

• Increased security - All traffic between your runner and Gitpod stays within AWS’s network backbone
• More reliable connectivity - Eliminates dependency on internet routing and potential connectivity issues
• Compliance ready - Ideal for customers with strict security requirements that prohibit internet-bound traffic

• DNS resolution - app.gitpod.io automatically resolves to VPC endpoint IP addresses within your VPC
• AWS PrivateLink - Traffic flows through Amazon’s network infrastructure via VPC endpoints
• Seamless integration - No changes required to your existing runner configuration

1. Create an Interface VPC Endpoint in your AWS account pointing to Gitpod’s service
2. Configure the endpoint in the same VPC where your runner is deployed
3. Enable DNS names for automatic resolution

​

Enterprise AWS runner with AI agent and direct connectivity

• Ona AI Agent Integration: AI-powered assistance for automatic Dev Container generation and environment setup
• Direct Connectivity: Bypass Gitpod’s central gateway using your own Network Load Balancer with custom domain and SSL/TLS certificate
• Advanced Networking: Custom VPC configurations with flexible subnet architecture for internal-only or internet-facing deployments
• Flexible Deployment: Deploy behind corporate firewalls with future HTTP proxy support

• HTTP Proxy Support: Custom HTTP proxy configuration for environments behind corporate firewalls
• Custom CA Certificate Support: Integration with enterprise certificate authorities and custom certificate chains

​

Introducing our AI powered Development Environment setup workflow

1. Open an environment in Gitpod without an existing Dev Container configuration
2. Gitpod offers to run our Ona powered setup agent automatically
3. Ona generates devcontainer.json and automations.yaml based on detected dependencies and best practices
4. Review and commit configurations for your team
5. All subsequent environment launches use the optimized configuration

​

Gitpod now supports Windsurf editor

​

Faster development environment start times for AWS with Dev Container build caching

• Faster startup times from minutes to seconds for environments with identical Dev Container configurations
• Reclaimed developer time: Convert 5 minute development environment startup delays into 30-second starts
• Automatically optimized start times performance without any configuration changes required

• All subsequent starts using the same project will benefit from significantly faster startup times.
• Images are cached for 30 days before automatically expiring to manage storage costs.
• The cache is restricted to users of the project and can be disabled in runner settings if needed.

1. Update your CloudFormation stack to the latest version that supports the cache
2. Go to Settings → Runners in your Gitpod organization
3. Select your AWS runner and toggle Dev Container image cache to enabled

​

Analyze your organization’s Gitpod usage with Insights

Ona Insights dashboard

• Analyze environment usage across your entire organization
• Optimize cloud costs by identifying opportunities to right-size resources
• Monitor adoption by tracking active users and environment metrics

• Active Users: Track weekly active users and engagement patterns
• Environment Usage: Monitor total environments and runtime hours
• Resource Distribution: View usage by projects, users, and environment classes

​

Create development environments from scratch without a Git repository

• Start with a clean slate using your organization’s default environment image
• Start an environment without requiring a git provider configured on a runner
• Begin development immediately without needing to clone an existing repository

1. Click the Create Environment button
2. Select Create Environment From Scratch
3. Choose your preferred environment class
4. Click Create to start your new environment

​

Organization policies to manage cost, security and developer experience

• Enhance security - Restrict development environments to only run in the cloud (e.g. not locally) and control which editors developers can use to access your code
• Standardize experience - Create a consistent “golden path” by defining allowed editors and default container images
• Control costs - Set environment timeout limits and maximum environment counts to prevent unexpected resource usage
• Enforce governance - Require environments to be created only from approved projects
• Manage resources - Limit concurrent running environments per user for optimized resource allocation

​

Gitpod now supports VS Code in the Browser

• Drive down your developer onboarding times by eliminating all manual setup for your development teams.
• Empower developers to review code easily by launching new development environments running in their browser tab.
• Drive down incident response times with SREs able to do on-the-go incident response direct from their mobiles.
• For secure enterprises, Gitpod paired with a secure browser (like Island) is a secure and performant alternative to traditional VDI.

​

Getting started

​

Gitpod now supports JetBrains Toolbox App

• Use the familiar Toolbox App interface to manage your IDEs in Gitpod
• Connect to Gitpod environments from your desktop
• Install and update JetBrains IDEs in your remote environment

​

User Secrets support

• Configure personal secrets for all of your Environments
• Integrate against 3rd party systems which use Personal Access Tokens to authenticate seamlessly, and even use atuin to have persistent terminal history in your Environments.

• Files: Secrets can be mounted as files for complex structures e.g. JSON.
• Environment Variables: Inject secrets as environment variables.

​

AWS ECR private registry support

• Securely access private ECR repositories without manually managing credentials
• Simplify authentication workflows using EC2 runner’s IAM role
• Seamlessly work with private container images in your development environment

• You’re using AWS EC2 runners for your environments
• Your ECR registry and EC2 runners are in the same AWS account (or have appropriate cross-account access)

​

Linux Host-based Runner

• Accelerate evaluation: Go from zero to fully operational CDE in minutes without AWS credentials or specialized hardware
• Control infrastructure costs: Replace unpredictable cloud spending with fixed, predictable costs using your existing hardware
• Maintain flexibility: Easily scale by adding additional runners or transition to cloud-based solutions as your needs evolve

​

Domain Verification for SSO

​

Private container registry support

• Pull Dev Container images from private registries
• Authenticate with container registries during your development workflow
• Work with private images in your Flex environment without exposing credentials

• Docker Hub
• GitHub Container Registry
• GitLab Container Registry
• Azure Container Registry

​

Dotfiles Support for Gitpod

​

Introducing Gitpod SSO

​

Introducing Gitpod secrets & environment variables

• Environment Variables: Inject secrets as environment variables.
• Files: Secrets can be mounted as files for complex structures e.g. JSON.

​

Migrate from .gitpod.yml to devcontainer.json

gitpod env migrate