Seqera Platform Feature Requests

Will it be possible for users to host their own registry to deploy private plugins in their org?

Add support for JSON , YAML (and potentially Parquet ) formatted data.

As a user who belongs to multiple workspaces, I currently lack clear visibility into my assigned roles across different workspaces. Specifically: When added to a workspace through a team, I sometimes cannot see which team I'm a member of. This makes it hard to determine what I am allowed to do in a workspace. When viewing my workspace list, there's no indication of my role in each workspace. If I am not added via a team, I can click through and see it in the participant list, which is ok, but requires extra navigation. This is specifically for the predetermined roles Seqera Platform has. It would be great to always have visibility into which role I have, regardless of whether I was added via a team or participant, and to have this information readily available somewhere.

Users currently must create or edit sample sheets externally, and upload these files to create or edit Datasets, which is inefficient. Add an embedded spreadsheet editor within the platform to allow users to quickly and intuitively enter data and make edits directly.

Currently, Seqera Studio requires users to set a session lifespan at the time of creation, and this cannot be changed once the session is running. This limitation can lead to inefficiencies when workflows take longer than expected or finish earlier than planned. Feature Request: Add functionality to adjust the session stop time (extend or shorten) for an active session without restarting it. This would allow users to: Extend sessions when additional compute time is needed. Shorten sessions to save resources if work completes early. Benefits: Improved flexibility for dynamic workloads. Reduced resource waste and cost. Better user experience for long-running or unpredictable tasks.

I need an integration with Benchling that allows launching and monitoring pipelines directly from Benchling.

1. Dataset schema validation at launch: Nextflow workflow schema files (e.g. RNASeq) can reference specific schemas for input files. Action: Only datasets that match the input file schema could be selected and/or launched. 2. Dataset schema validation on creation: Automatic schema validation for datasets can be achieved by either building our own, or using a third-party tool. Action: Users with elevated permissions can define one or more valid schemas, and each dataset added to the workspace is first validated against the schema before being approved for upload to Seqera Platform. Additional potential milestones Integration with new Nextflow data lineage

When launching a pipeline in Seqera Platform, the data selection for Data Explorer should filter for buckets with write permissions, especially when browsing for workdir or outdir .

Currently it seems you need to append the .dump() operator to each channel you're interested in debugging, but this means debugging pipelines you've pulled in requires you chase down every channel in the source and append .dump to it to find the cause of the problem

As far as I'm aware, there is no way to specify these behaviours inside a .config file, they can be only done through the CLI flags. However the web GUI doesn't let you add custom CLI flags. There is a toggle for "Stub Run". I think there should be more toggles for these debugging features.