Yeah good catch. We are using only one template for everything. So the main configuration part is done inside the startup-script but this depends havily on the configuration we are getting from a git repository (coder.yaml inside). This means you can track this only for each of the workspaces but not in summary for all of a template.

For it would much better if we can put a feedback to the UI / user in form of task x from y is done. Maybe tasks can be shown with names. This way a user knows how long / how much time / tasks has to be done.

Example given: We have made a workspace prepared to dogfooding coder. Everything inside the coder.yaml defines what we need to develop a feature for coder. This takes some time (more tahn 5 Minutes). Setup Nix-Shell, Installing yarn (by the way is not in Nix), downloading code-server and extensions. And so on... This raises the Developer Experience.

Should I open a new Issue for this?

Ah I see, kind of like GitHub actions steps

Sorry, I realized I didn't answer your question. Please do. Feel free to suggest a specific design too :)