Seqera Platform Feature Requests

In the Studios interface when creating a new Studio, the "YAML list of formatted packages" input field should be pre-populated with example syntax (e.g., a minimal working conda environment structure) to guide users. The placeholder should disappear once the user begins typing or pastes their own content. The YAML syntax is easy to forget, it'd be easier to have a structure in the field rather than navigating to the docs elsewhere. Having an example pre-filled (similar to a placeholder or default template) would reduce errors and improve usability.

It would be helpful to have an additional tab in the Studio detail-view that shows all the analytics of a Studio's sessions: List of workspace users that have connected to the running session (most recent first, with time since connection). Number of connected views of the session. Number of executions of the code in the session. If the Studio has been locked/unlocked If the Studio has been switched private/non-private

As the number of users in a workspace increases, shared interactive environments can incur accidental edits. This can have serious downstream consequences if an interactive environment is part of a running data analysis pipeline or ML workflow (training a model, model in production, etc). To help avoid accidental edits, workspace Maintain+ role users (or just the creator) can lock the Studio session. This could be either: A one-way action (once locked, the session can never be unlocked). A lock/unlock action. Note: The audit log should capture this action for GxP compliance.

Currently, Studios cannot be used with Fusion-enabled Kubernetes CEs (Amazon EKS and Google GKE). Adding this will allow for greater control and more direct management of CEs for compliance, scale, and cost management purposes.

Currently, real-time in-notebook collaboration is only available in Jupyter, VS Code and Xpra containers because RStudio only supports this feature with a paid Pro license. Adding support in RStudio will require the ability to attach a Posit license to a Studio session.

The current implementation of Studios requires wildcard certificates to manage the in-application URL routing. This can be a blocker for adoption at Enterprise organizations that cannot issue wildcard certificates due to security concerns.

When creating a Studio sessions, it is possible to associate key-value resource labels to the session. These resource labels are displayed in the UI as tags, but the list of Studios does not provide the ability to filter or sort the studios based on the key or value of these labels. For larger workspaces with many studios, it would be helpful to subset the available sessions to those with particular keys and/or particular values.

Trusted research environments enabling research progress without sacrificing data security - ensuring data are handled in a secure and responsible manner. The following five general items need to be adhered to: Safe Data - Confidentiality of data is maintained Safe Projects - Data owners approve the research projects Safe People - Researchers are trained to use the data safely Safe Settings - A secure computing environment prevents unauthorised data access Safe Outputs - All exported results are screened and approved

Devcontainers is a standard format developed by Microsoft to configure development environments for VSCode and GitHub codespaces . It’s also going to be supported by GitPod . It’s a JSON file that sits in the root of a repo in a directory called .devcontainer/ . It can contain VSCode extensions, etc but the key things are: Dockerfile, docker arguments, and launch run commands. Supporting these files in Studios allow users to programmatically encode settings for Studios using a well adopted standard.

It would be helpful from security and compliance perspectives to allow Enterprise installations of Seqera Platform to support custom subdomains for Studios.