What's New

Bug fixes and minor improvements

This is a patch release that includes bug fixes and minor improvements.

Personalize dev environments with dotfiles

You can now apply your personal shell and tool configuration in dev environments using dotfiles. Just provide a Git repo with your dotfiles and an install script – CodeCanvas will clone it and run the script when your environment starts. Learn more

Recover data from failed dev environments

If a dev environment fails to start, and you have unpushed changes or other data in it, you can now create a recovery dev environment. It will have the volume of the failed dev environment at /mnt/jetbrains/additional-volume, so you can access and save your work. Learn more

Custom SSH server options

You can now customize the SSH server configuration for dev environments. Use the new Override sshd server settings field in the template settings to specify your own sshd options. Learn more

Add or remove Git repositories in existing templates

You can now add or remove Git repositories in existing dev environment templates. This is useful when you want to include an additional project or script repo without creating a new template. If you update the repository list, all warm-up snapshots and standby pools are automatically invalidated to ensure consistency.

Bug fixes and minor improvements

This is a patch release that includes bug fixes and minor improvements.

Support for Cursor

You can now use the Cursor code editor in dev environments. Learn more

Support for VS Code/Cursor extenstions

You can now pre-install VS Code/Cursor extensions in dev environments by specifying the extension IDs in the dev environment template. Learn more

Concurrent usage limits

CodeCanvas now lets you control how many dev environments users can run simultaneously. Each instance type has a usage cost, and each user has a usage limit. Learn more

Support for Jupyter notebooks

Users can now run Jupyter notebooks in dev environments. Learn more

Network policies for dev environments

The CodeCanvas operator Helm chart now supports basic network policies for dev environments. By default, inbound traffic to and between dev environments is blocked to improve isolation and security. Outbound traffic remains allowed, but chart parameters can change this behavior. You can also define custom network policies. Learn more

Auto-disable warm-up and standby pool

To help reduce cloud costs, warm-up schedules and standby pools are now automatically disabled after repeated failures or inactivity. Namespace administrators can subscribe to email notifications when this happens. Learn how to configure the feature for warm-up and standby pools.

Skip scheduled warm-up if there are no Git changes

You can now configure the warm-up schedule to skip a warm-up run if there are no changes in the Git repository since the last warm-up. Learn more

Default non-root user in dev containers

Dev environments now run under a non-root user by default. The codecanvas user (UID 22222, GID 22222) replaces root in the default container image. Learn more

As a result of this change, the contents of dev environment and warm-up snapshots have also changed: instead of saving the /root directory, CodeCanvas now saves the /home directory where user data is stored.

User activity per namespace and per template

You can now track user activity statistics not only globally, but also per namespace and per dev environment template. Each namespace and template now has its own User Activity page showing daily and monthly metrics for unique active users and the number of new dev environments.

See Track user activity in a namespace and Track user activity per template for more details.

IDE plugin/extension availability check

When you specify a JetBrains IDE plugin or a VS Code/Cursor extension in a dev environment template, CodeCanvas now verifies that the plugin or extension exists in the corresponding marketplace (JetBrains Marketplace or VS Code Marketplace). Learn more about configuring plugins/extensions

Template change invalidates warm-up snapshot

If you change a dev environment template in a way that affects warm-up output (for example, by changing lifecycle scripts, environment variables, etc.), the existing warm-up snapshot becomes outdated. The UI now suggests re-running the warm-up to generate a new valid snapshot. Learn more about warm-up snapshots

Bug fixes and minor improvements

These are patch releases that include bug fixes and minor improvements.

Improved infrastructure flexibility

Now, the installation of the infrastructure responsible for running dev environments (a computing platform) has been fully decoupled from the main CodeCanvas installation.

• Jump servers can now be installed in any cluster, similar to Relay servers, enabling more flexible multi-region setups.

• The CodeCanvas operator has its own Helm chart, allowing independent deployment of dev environment clusters.

Learn how to deploy a computing platform on Amazon EKS, Azure AKS, and Google GKE.

AWS CloudFormation installation

You can now install CodeCanvas using AWS CloudFormation. This method lets you deploy CodeCanvas in minutes using a simple web-based wizard. It installs the application and all required dev environment infrastructure in a single Amazon EKS cluster — ideal for quick evaluations or small-team setups. Learn more

Free license

A free license for CodeCanvas is now available. Though the license supports all core features required for development, some enterprise-level features aren't available or limited. Learn more

Improved dev environment logs

Now, the dev environment's Timeline tab contains more detailed and informative messages about the environment lifecycle. Messages in the Logs tab are also more informative and are structured in several categories. Learn more

Usage monitoring

A new User Activity page is available in the Administration section. It lets you track daily CodeCanvas usage: the number of unique users who start dev environments and how many new environments are created. Learn more

Component status on Computing Platforms page

The Computing Platforms page now displays the health status of all key components: the operator, Relay server, and Jump server. This helps administrators quickly verify that platform infrastructure is running correctly.

Improved cron triggers in warm-up and standby pool

The cron triggers in warm-up and standby pool configurations now show the specified cron expression in the human-readable format. E.g., for 0 1 * * MON-FRI, the UI shows Scheduled at 01:00 every day between Monday and Friday. For warm-up, it also shows the next scheduled time. Learn more about warm-up and standby pool

JetBrains Toolbox as dev environment launcher (Beta)

JetBrains Toolbox can now be used as a launcher for connecting to dev environments, alongside JetBrains Gateway. Users can set their preferred launcher in personal settings, while administrators can configure an organization-wide default.

Improved GPU support

Now, there are more options to configure GPU support for dev environments: You can specify the number of GPUs, assign specific GPUs by their IDs, and more.

Integration with JetBrains Account

You can now buy and manage CodeCanvas licenses via JetBrains Account. Learn more

Restrict copy/paste (JetBrains IDEs only)

You can now restrict copy/paste operations in JetBrains IDEs running in dev environments. Learn more

Support for custom relay servers

You can now configure custom relay servers to relay WebSocket connections between JetBrains Gateway on user local machines and IDEs in dev environments. A relay server acts as an intermediary to enable secure communication when inbound connections to dev environments are restricted. Learn more

Auto-generate SSH keys for Git servers

When connecting a Git repository to CodeCanvas, you need to provide an SSH key pair. Now, CodeCanvas can generate these keys automatically. The private key is saved in the CodeCanvas internal storage. The public key is shown in the UI, so you can add it to your Git server. Learn more

Install IDE plugins from custom sources

You can now install IDE plugins in dev environments not only from the JetBrains Marketplace but also from custom sources. Learn more

Max session duration timeout

You can now set a maximum session duration timeout for dev environments. After this period, a dev environment is automatically stopped regardless of the user activity. By default, the session duration is 600 minutes (10 hours). Learn more

Auto-delete failed dev environments in standby pools

You can now configure CodeCanvas to automatically delete failed dev environments in standby pools. Learn more

Start run configuration on IDE startup

You can now configure dev environments to start a run configuration automatically each time the IDE starts. Learn more

Use default dev container image from previous versions

When you update CodeCanvas to a new major version, the default dev container image is also updated. If this causes issues, you can pin a specific version of the dev container image in the Helm chart values. Learn more

Troubleshooting improvements

Multiple improvements regarding logging, input validation, and error reporting that can help troubleshoot issues in templates and dev environments.

Various improvements

This release includes multiple bug fixes, performance improvements, and usability enhancements.

Multi-repository support

Now, you can specify multiple repositories for a dev environment template. Each repository is opened in a separate IDE tab on dev environment start. Learn more

Improved Visual Studio Code support

You can now use VS Code in dev environments with no additional configuration. Learn more

GPU support

You can now enable GPU support for dev environments. Learn more

Migrate users from external sources

You can now migrate and then synchronize users from external sources. To do this, use the /user-sync API endpoint. Learn more

Convert inactive volumes to snapshots

To avoid the costs of storing inactive dev environment volumes, you can convert them to snapshots stored in a cheaper object storage. Learn more

Migration from computing platform

You can now migrate instance types and templates from one computing platform (a Kubernetes cluster that runs dev environments) to another. Learn more

Improved IDE plugin installation

You can now pre-install IDE plugins to dev environments by specifying the plugin IDs in the dev environment template. Learn more

Recover dev environments

You can now recover failed dev environments. During recovery, CodeCanvas creates a new dev environment container and re-downloads the IDE. Learn more

Authenticate in Docker registries via credential helpers

If your dev environments use Docker images from private registries that require authentication, you can now authenticate in these registries via credential helpers. Currently, CodeCanvas supports credential helpers for registries hosted in AWS ECR (Amazon Elastic Container Registry) and GCR (Google Container Registry). Learn more

Run dev environments under non-root user

You can now run dev environments under a non-root user. This feature is available for dev environments that use custom Docker images.

Use warm-up snapshots built for another branch

If you create a dev environment for a custom branch that has no warm-up snapshot, CodeCanvas will now use a snapshot built for the branch specified in the dev environment template. Learn more

View template history of changes

You can now view the history of changes for a dev environment template. Learn more

Improved script support

Before: To run a warm-up or lifecycle script, you had to create a script file in the project repository and specify the script file path in the dev environment template.

Now: You can specify the script directly in the dev environment template. Learn more

Override worker pod template

You can now define a worker pod template for an instance type. This template overrides the default worker pod template set in the computing platform settings. Learn more

Multiple minor improvements

This release includes multiple bug fixes, performance improvements, and usability enhancements.

Initial release

This is the first release of the product.