2025-10-24 (v5.146)
Bug Fixes
- Storage provision status breaks out of modal
You can now easily discover and insert nested workflows directly while editing your workflow YAML:
uses: marketplace/ or uses: workflow/ automatically suggests all available nested workflow names and slugs.uses: marketplace/someworkflow/, shows all version options for that nested workflow.with: (note the space), suggestions appear for four input options:
Once selected, the inputs are automatically filled in, and if applicable, a dynamic input form is generated in a section labeled after the nested workflow name.
If the YAML doesn’t already contain on.execute.inputs, it is automatically created.
Existing inputs in the YAML remain unchanged.
You can now seamlessly switch between YAML and JSON views in the editor:
Organizations can add a line of text at the very top of all pages. The color and message can be customized in the organization theme settings.
Redesigned the organization user edit page to consolidate all user settings in one place. The platform-level user edit page has been removed, everything is now managed directly from the organization user page for a streamlined experience.
You can now select any image you want when creating an instance, when typing in the dropdown there is an option to Use {image id}
The Parallel Works CLI can now be used to list public buckets on AWS, Azure, and Google Cloud Platform.
When using the Parallel Works CLI, you can now filter clusters returned with the new --owned and --status flags.
Examples
# List clusters owned by the user "Jake.Thayne"
pw cluster ls pw://Jake.Thayne
# List only clusters you own
pw cluster ls --owned
# List only provisioned clusters
pw cluster ls --status=on
You can now see the storage for your user workspace from your account page.
Now can use pw ssh --proxy-command as the ProxyCommand option for both SSH and SCP
Examples:
Run as a ProxyCommand for SSH
ssh -o ProxyCommand="pw ssh --proxy-command %h" user@pw://Jake.Thayne/my-resource
ssh -o ProxyCommand="pw ssh --proxy-command %h" user@workspace
Run as a ProxyCommand for SCP
scp -O -o ProxyCommand="pw ssh --proxy-command %h" file.txt user@pw://Jake.Thayne/my-resource:/home/user/file.txt
scp -O -o ProxyCommand="pw ssh --proxy-command %h" file.txt user@workspace:/home/user/file.txt
Note: only scp -O works at the moment (forcing scp to use sftp protocol)
The Parallel Works CLI can now copy files from public buckets even if those buckets are not managed by the ACTIVATE platform. This works on AWS, Azure, and Google Cloud Platform.
Examples
pw ssh workspace to connect to user workspacepw ssh pw://namespace/cluster to connect to cluster in a namespace (username)pw ssh pw://namespace/cluster echo hello to execute a remote command over sshYou can now target your workspace when creating sessions. Example using update-session in a workflow:
- name: Expose port
uses: parallelworks/update-session
with:
remotePort: ${{ inputs.port }}
name: ${{ sessions.sessionname }}
status: 'running'
target: 'user-workspace'
Billing now auto summarizes and archives old cost data based on platform or organization policy Archive Cost Data
pw bucket commands now support recursive copies with the -r flag.
New AWS and Azure buckets are now sessionless, meaning after provisioning a bucket, destroying it will also delete the configuration of it. AWS bucket provision statuses are also improved.
The multi-cluster job monitor is now generally available, and can be found on the sidebar.
By default, we use the language you have set in your browser to display the Parallel Works ACTIVATE application. Now, you can override the browser settings in your account to a specific language. We will then prefer this setting in all cases when displaying localized interfaces.
The cluster details page will now be available in supported languages.
Users can now attach inline disks to google cluster partitions; each node within the partition will receive the same set of disks
We recently added localization into four languages:
Initially, only the navigation components, the sidebar and the command palette, were localized. Now we've additionally added localization for the home page. We will be continuing these efforts, focusing on the highest touch areas of the ACTIVATE platform first.
Organizations can now share AI Chat Providers across their members. This allows a single provisioned provider to be reused by multiple users, reducing redundancy and cutting infrastructure costs. Once shared, team members can send messages through the same provider without needing to set up their own.
The runtime column on the home page and workflows page will now show information while the workflow is still running. The start times are now shown in relative time, i.e. "5 minutes ago." You can hover over the time to see the date and time. It will also show this information the correct language based on your browser preferences.
Workflow icons will now show on the home page workflow run widget.
We've made changes to the marketplace. The item and edit page now have an action bar, with all of the familiar actions being moved onto that bar. Additionally, the marketplace item you're editing can always be seen from the top of the page now.
The marketplace had multiple terms for the concept of favoriting. All of these have been unified under the term "favoriting." For workflows, favoriting an item will make it show up on your workflows list, under "Marketplace Workflows," so you can run it directly from that list. For other items, favoriting the item makes it available in the "Load from Marketplace" dropdowns.
compute-clusters fields do not validate required fieldsThe terminal interface is now internationalized based on your language preferences. Additionally font size and theme is customizable. The themes "light", "dark", "rose pine", and "dracula" are available.
You can now update workspace mounts while a cluster is running.
Users can now manage helm charts in kubernetes namespaces they have access to.
You can now use cmd+s or ctrl+s to save changes on the build tab when building workflows.
Users can set now set their own application theme from the account settings page.
Users can now attach inline disks to cluster partitions; each node within the partition will receive the same set of disks
Users can now customize the bucket name when provisioning a new bucket on AWS and Google Cloud Platform. This was already available on Azure.
This adds a customize page to the organization settings. On this page, you can find overviews of new user defaults, sidebar settings, and the organization theme. Clicking on one of the cards on the page will let you customize the settings.
Organizations with OIDC configured can now disable automatic account creation. We also added an option to automatically convert usernames to TitleCase.
There is now a button on clusters allow you to initiate an agent update. This will update the PW Agent and CLI to the latest version.
You can now attach inline disks to google clusters which have an automatically-selected zone
The search box on the admin panel user's page now supports filtering with email addresses in addition to usernames.
Introduced platform (admin only) and organization policies, which are rules and configurations that are applied to all users and resources at either platform or organizations level. Platform policies take precedence over organization policies.
You can delete sessions from the home page now.
We've changed the terminal tabs to a vertical view. This is in preparation for upcoming support for splitting a terminal tab into multiple terminals.
A menu bar was added to the terminal to open terminals in new tabs and to clear the terminal.
Organization admins can now set themes for organizations. This will allow you to change the color of different UI elements for users in an organization.
Users can now copy Azure snapshots to another region from within ACTIVATE.
We now autofill default values when adding a workspace mount to make it easier to understand what values to use for each input box.
You can now open the terminal in a new window that doesn't show the rest of the ACTIVATE UI frame.
You can now navigate the inbox page with your keyboard up and down arrows as well as use the backspace button for deleting messages.
Local Apps are now determined based on if the app property is found inside of the workflow YAML definition.
You can make a workflow show up on the apps list by simply adding the following to any workflow definition:
app:
Users can now copy AWS snapshots to another region from within ACTIVATE.
After capacity reservations are added or updated from the organization settings, the reservation's past cost data will also be assigned to the newly designated group.
You can now connect any OpenAI-compatible API directly to the ACTIVATE interface using your own authentication tokens.
This lets you chat with models from your chosen provider while keeping full control over your usage and data. Chat history is saved securely within our platform, so you can easily continue previous conversations or reference them later.
Workflows can now check if a value includes a string with the following syntax
${{ inputs.name includes 'foo' }}
MultiZone option has been added to partition settings when configuring an AWS cluster. This will allow provisioning compute nodes in multiple zones in the case that there is not enough capacity in one zone.
Platform admins can now impersonate users from the organization users list, in addition to the platform users list.
The cluster list home page widget has been enhanced to have four modes:
Setting clusters to my mimics the old behavior where only your own clusters are shown in the list. shared is only other user's clusters which have been shared with a group you're in. all is every cluster you have access to (both my and shared). single always shows a single cluster.
You can now use the if field at the job level to completely skip the job and all of its steps.
You can now add a kubernetes widget to your home page, listing all available kubernetes clusters.
Kubernetes workload widgets can now be added to the home page. This lets you see the workloads for a chosen cluster/namespace combination from the home page. Additionally, we've slightly adjusted the styles of the clusters widget so one cluster exactly fits a 2x1 widget.
Apps are really just workflows with some added features to make them easier to use. Before, if you wanted to see the workflow behind an app, you had to go to the apps page and look for the "Go to workflow" option. Now, we've made it easier. You can find the app's workflow right in the main workflow list, too.
You can now track the deployment progress of the kubernetes cost management plugin via the UI.
MultiZone option has been added to partition settings when configuring a cluster. This will allow creation of compute nodes across multiple zones. This can be useful if trying to use an instance with high demand or low capacity in certain zones. Note that If nodes are created across zones there will be additional data charges when transferring data between nodes in different zones.
AWS Sagemaker is now available in feature preview under the machine learning section
Organizations can now create infrastructure in eu-west-3 (France).
In workflows, environment variables can now be defined at the global, job, and step levels. Previously, they could only be set at the step level. Precedence is hierarchical: the closer the variable is defined to the step, the higher its priority.
AI Chat messages are now streamed to provide a more responsive experience.
Now you can select a configuration from the app launcher to launch an app with a predefined set of inputs.
Target tags are a new concept which correspond to the tags on computing resources, marking a compute resource as compatible with a given app configuration.
Configurations can be saved by filling out the workflow form and saving it as a configuration, or can be provided by the workflow developer as built-in configuration. This is done in the "Build" tab of a workflow by editing the yaml. These built-in configurations can be selected from dropdown and are also shown in the configurations tab, just like manually saved configurations.
Organization members can now user teams endpoint to get their group's allocation used
Can now see the helm charts deployed into the selected namespace for the Kubernetes cluster
You can now see the details for helm charts installed in your kubernetes clusters. Additionally, you can rollback helm revisions directly from the ACTIVATE interface.
Conversations with AI Chat providers are now saved, so you can continue previous chats at a later time.
This introduces a new networking mode when provisioning organizational base infrastructure. This provides compute nodes with their own public IP addresses. This is useful in cases where you want egress charges to be billed to the same group as a cluster instead of being absorbed as an organizational cost. The security group that is attached to compute nodes will block inbound access from internet but will allow traffic from other compute nodes.
k8s, kubernetes)Users can now filter instances by whether or not they have a GPU
Admin user can now subscribe to billing alerts
nvidia.com/gpu in kubernetes resource quotasOrganization administrators can now define resource quotas for GPU resources labeled with nvidia.com/gpu
On the details page for a workload, there will be a list of all the pods associated to that workload with links to the individual pod details page.
Organization admins can now provision base infrastructure in the eu-central-1 region on AWS.
Users can now monitor and download logs for actively running Kubernetes pods
You can now filter instances by architecture and networking feature on instances list when selecting an instance for a cluster.
We've found that the sharing feature had limited usefulness because previously you had to be a member of both groups to share a resource. Now, you will be able to share with any group inside of the same organization, regardless of your personal group membership.
A new Nodes tab has been added on a clusters information page. This tab will list all current pending, active, and failed nodes. Clicking on a node from the list will show details for that node.
You can now install the PW CLI on Windows.
User can now input display name in storage creation page
Cluster pages have been refreshed to provide more useful information on a details page, and make editing more user-friendly.
The platform can now track resource allocation usage (currently supporting CPU and memory) and enforce resource quotas for Kubernetes
You can now create AWS Disks that will be encrypted with a AWS managed KMS Key. Any snapshots created from the disk will also be encrypted as well as any disks created from an encrypted snapshot.
You can now attach storages from the Storage panel on a compute resource's information page while the compute resource is running. Previously, you could only attach a storage from the configuration page.
Users can now create sessions with the Kubernetes provider, supporting pods, services, and deployments
Cluster provision status can now be opened from cluster list page
You can now add the autoselect property to a dropdown field when building a workflow. This will make it so the first option is automatically selected.
Cluster automated delete request now has reason displayed
Admin users now can see Impersonated By on resource provision and destroy records
Users can now use a custom subdomain when creating a session
The command pw kube ls is now available to list available kubernetes clusters. In addition to basic listing, it also supports output format flags -o json and -o table.
You can now manually create sessions of the "link" type. Link sessions are simply links to other applications or services from within the platform. In the past, a workflow would've created these in case a session is managed outside of the ACTIVATE platform.
Added more details to cluster provision status records. You can now click on individual provision status lines to see more details.
When attempting to shut down a cluster you will now be given the option to stop the controller. While stopped, costs will be reduced to only the cluster's storage. When you try to start a stopped cluster, you will be prompted to restart the cluster.
Auto Reconnect option has been added to existing cluster options. If enabled we will try to automatically connect to the remote vm. You must first connect manually by pressing the power button.
Workflows now have a password field which can be used by workflow developers to hide text as its being entered.
If a cluster fails to provision, a red banner will be shown at the top of the page indicating that the cluster should be destroyed.
You can now cancel a workflow run and view running sessions from a workflow's Run page
We now show the required disk size you will need to use an image in the image selection dropdown.
You can now create snapshots from disks that were configured inline in the cluster configuration page. You may do so from the clusters "Sessions" page in the attached storages table.
You can now see CPU usage, Memory Usage, and Storage usage for kubernetes workloads (statefulsets, deployments, etc). These are viewable from the workload pages. These metrics show combined usage for all pods managed by that resource. We will have individual pod metrics in an upcoming release.
Platform administrators will now receive an alert whenever the platform detects that a resource deletion might not have been processed correctly.
You can now edit Kubernetes resources by modifying them directly on the YAML editor.
You can now provision and chat with OpenAI models on Azure. To enable this feature preview, use the feature preview menu.
Cloud clusters will now have CPU, Memory, and Root Disk charts at the top of the cluster details page.
In addition to keyboard-interactive, the existing cluster provider can now support older password ssh connections
Kubernetes workload pages now use a more readable format to show relevant information.
You can now receive runtime alerts for storage. You may choose to turn on/off runtime alert in storage's properties tab. This will send you a notification after your storage has been running longer than the interval specified. You can configure if you receive the notifications via the platform inbox or via email through your account settings.
Admins can now set the latest image directly from the admin panel
Users can now update cluster bootstrap script and its toggles (controller/compute) while cluster is running
Organizations can now add kubernetes clusters and share them with specific groups. Users in those groups will be able to use the pw CLI to add a context to their local kubeconfig, allowing users to run kubectl commands. Kubernetes resources are now visible in the platform for users that have access to the cluster.
You can now snapshot AWS root disks and then boot your cluster using that snapshot.
OS Snapshots are now a generally available feature. You can create a snapshot by going to your cluster, and selecting create snapshot next to the root disk. After doing so, you can choose that snapshot as the image to use when starting a cluster. This is a direct replacement for the old scripted method of creating OS images via the account settings page. We will be removing that method of creating snapshots in an upcoming release.
You can now set descriptions on Capacity Reservations
You can now manually create sessions without having to start a workflow. Try this out by clicking the Add session button on the Sessions page.
You can now specify custom NFS mounts via the cluster configuration form. This applies to cloud clusters and OpenStack clusters.
Use Load Balancer as Nat Gateway option has been added to azure infrastructures. This will make it so a load balancer is created with each cluster and all egress traffic from partitions will go through the load balancer allowing tracking of egress cost.
The Azure ML Workspace feature preview has been made publicly available. To try this feature out, enable it from the feature preview section.
Capacity reservations are now supported on Azure and Google Cloud. Organization administrators can now specify which CSP the capacity reservation is for when adding the capacity reservation. On the cluster edit form, the input field for capacity reservations has been changed to a dropdown.
We now support managing NetApp ONTAP volumes directly from the ACTIVATE platform. These volumes can also be mounted to OpenStack clusters which have network access to the NFS exports provided by the ONTAP service.
You can now see which cluster a session is targeting from the Sessions widget and from the Sessions page.
Storage items now appear in the platform search
The admin panel platform image list now shows the CSP's unique identifier for the image.
Organizations can now reset the organization-wide default sidebar settings to the platform defaults by using the radio button available on the user defaults page.
You can now search the platform and documentation via a new search bar at the top of the UI. Open this with cmd + k on Mac OS or ctrl + k on Windows.
Use Controllers as NAT Gateways option has been added on AWS/Google infrastructure configurations. Enabling this option will make it so all traffic from compute nodes are proxied through the controller. All compute nodes will share the same IP as the controller node. This will enable tracking egress costs from compute nodes.
You can now provision public IP addresses on Azure independently of other compute resources. After provisioning a public IP it can then be assigned to a compute cluster controller node.
Improved provisioning status logs shown when creating an AI Chat resource
Organizations can now define a default sidebar for new users. Users that have not customized their sidebar will automatically use the organization's default settings. If the organization does not specify a customized sidebar then all sidebar items will be visible by default.
Adds an optional DNS service to platform deployments which can resolve slurm cluster hostnames if needed
Added Cost Alert notification type and user preferences.
Added cluster cost estimation for openstack
Platform administrators can now toggle Debug Mode in cluster Advanced Settings section.
When turned on, users can ssh into the node without waiting for it to be ready using ssh root@<nodeip>. Can be done from the user workspace or user's personal computer (if public key is added in the platform). Node clean up will not happen if there is any error in provisioning.
You can now edit widget names on home page. Click Customize and you will now see an edit icon next to the widgets name.
Sessions that were created by workflows will now show the workflow icon next to the session
The resource monitor module has been removed from the front page. In order to not disturb saved layouts you will need to manually remove the module where the resource monitor was previously.
You can now edit the workflow home page widget to change which workflow type to show. The default home page widgets have been updated to include the Favorite Apps and the Sessions widgets. Users that have modified their home page will not receive the new layout, and can instead add these widgets by choosing "Customize" from the top right of the home page.
pw nfs ls command to the cli
pw cluster attach-storage command to the cli
nfs ls and cluster attach-storage commandsYou can now use the new pw nfs ls and pw cluster attach-storage commands from an authenticated cluster session.
Sessions are now available as a home page module which can be added using the customize button on the home page.
Users can now customize the items that appear on their sidebar. In a future update, organizations will also be able to customize the default sidebars for users in their organization.
Can now provision Azure OpenAI resources from within the platform and directly chat via the UI.
Apps and sessions are now generally available.
Apps provide a layer on top of workflows which make additional interfaces available for workflow developers to make interactive experiences easier. Sessions expose ports on compute resources to the browser so users can run interactive apps on their computing resources and access them directly via ACTIVATE.
Read our documentation for apps and sessions to learn more.
On a session's page, current running workflow steps will be shown while the session is pending.
We've updated the default layout of the home page. If you have not customized your home page, you will automatically be moved to the new default layout which shows:
To customize your layout, use the customize button at the top right of the home page. Note that users with a custom layout are not affected by this change.
Platform level slurm cluster images can be managed through the admin panel.
You can now set default session names on workflows:
session:
mySession:
prompt-for-name:
default: "defaultname"
Allows setting environment variables on a job level. Environment variables set at a step level will override the environment variables set at a job level.
jobs:
main:
env:
foo: "bar"
steps:
- run: echo ${foo} # bar
- run: echo ${foo} # baz
env:
foo: "baz" # will override env variable set on job level
Stopping a session will now also stop the workflow run that started the session and any sessions associated with the workflow run.
Logs and input validation for updating session has been improved.
if being falseclient_secret_basic token endpoint auth methodThere is now a dropdown on the OIDC auth method to allow choosing either client_secret_basic or client_secret_post. These auth methods are used for the platform to authenticate to the token endpoint after a successful OIDC user authentication.
Scopes can now be specified when adding or updating an OIDC auth method in organization settings.
View logs button to see the details of what happened.OIDC endpoints can now be manually provided instead of using the issuer to discover them. This makes the OIDC authentication method more flexible for cases where applications do not have a proper well-known endpoint or the well-known endpoint is behind a firewall but the other endpoints are not.
This update also has slight visual enhancements to the auth method page, with the "configure" button being changed to a link.
The new provisioning experience is live for Azure NetApp files.
Adds an input box when attaching filesystems only for Hammerspace. This input allows users to define the export path the cluster will use to mount the hammerspace file share from.
You can now specify remoteHost and slug when updating a session.
- uses: parallelworks/update-session
with:
slug: 'string' // (optional) appends this slug to the session url
remoteHost: 'string' // (optional) host to forward session to from the target, defaults to "localhost"
... other inputs
You can now also specify if the session will use TLS.
sessions:
mySession:
useTLS: true // (optional) Will use https when connecting to session, should only be turned on if the app requires https.
Changes the Hammerspace provision status UI to only show the main components getting created, Anvil, DSX, DataNodes. Also adds deletion statuses.
When a resource supports the new provisioning experience, you will now see the deletion records directly below the provisioning records in the provisioning status panel.
When provisioning Azure storage accounts, if a name was unavailable the provisioning would silently fail. You will now receive an error that the name is already in use in these cases. This update also fixes other minor issues and typographical problems with the new provisioning UI.
Failed nodes are now also returned in cluster data. This is useful for workflow that need to know nodes provision status to make decision instead of waiting for slurm to time out
The new provisioning experience is now generally available for our next-generation cloud clusters and most cloud storage options.
Next-generation cloud clusters are now generally available. With this update, previous generation clusters will be marked with the text "Legacy".
Workspace mount points now have tooltips for substitutions
Added inputs on Hammerspace configuration form that show up when selecting UltraSSD_LRS disks. These options are for configuring the IOPS and Mbps Throughput for all disks within the Hammerspace deployment.
All users can now enable the "apps" feature preview from the feature preview menu.
Adds a summary box above the workflow dependency graph
Can use PW_API_KEY environment variable with tokens to authenticate
Adds a command pw auth identify-platform to the CLI to help identify which platform host the CLI is configured to run commands against.
Make nodes provisioning more stable for azure
Introduced a new structure for the changelogs, where changes are categorized into three sections: Enhancements and Features, Bug Fixes, and Other Changes.