cc: @BrunoQuaresma @Emyrk @bpmct

I think we can just list the values like we do for other deployment value things. Making it very nice and designed is not necessary IMO.

95% of deployments will not use experiments, and the ones that do are inherently more technical for using them.

Reopen as it's a basic implementation. We can make it look nicer

@Emyrk I enabled all experiments on a PR deployment with CODER_EXPERIMENTS=*, but I do not see the Experiments field. Does it only appear when we enable individual experiments explicitly?

It should show, but to be honest I was not 100% sure how the typescript worked. Was just following the existing pattern.

Let me see...

Mine does show?

I'd love if we also linked to the experiments endpoint so the admin can see what can be enabled.

@sharkymark I remember you were looking for a way to see all available experiments.

@bpmct @matifali Experiments are intentionally an "advanced" feature to opt into features that are not ready for production.

Do we really want to show these to everyone, meaning people might just "opt into" these experiments without understanding the repercussions?

Right now there is the concept of All which are safer:

Ya'lls call, just feels like a very niche feature to show all these.