Oh by the way, I think the layout of the Quicklaunch form changed since I last checked. I think both views are now even more similar to each other already.

I assume the only difference now is if pipelines are registered already (main launch form) or if you quicklaunch a potentially new pipeline, right? I think registered pipelines might be higher priority because we usually have correct compute environments set up for them and mostly want them to run in a predefined workspace (whereas quicklaunch always seems to run in the user space).

Rob Newman Oh sorry for the delay. I must have overlooked the notification email and just saw it while visiting the forum again.

Actually, I would not mind either of those solutions as long as one of them allows us to prepopulate some but not all parameters for a run (mainly of pipelines that we already registered in a workspace on Seqera Platform but they also exist as repos of course) and let's the user continue filling parameters in a nice WebUI (not as a params.yml as currently for the quicklaunch).

I think number 2. might make a little more sense since users are more familiar with the main launch page and it seems like the main launch page is the way to go for already registered pipelines.

Long-term I think both would be cool!

Does that make sense?

Decent Macaw: Can you please clarify if you are asking for two distinct feature requests (or if not both, which one specifically)?

Thanks for your help in refining the question.