Repository navigation
support separate tabs for each coder_script on the workspace page #15614
Description
Currently, we show all coder_script logs in a single UI container, which makes it challenging to debug which script has an issue.
It would help to move these to separate tabs for each coder_script starting from startup_script. It may look like this:
Here the name can be rendered from coder_script.display_name and icon from coder_script.icon
The main changes requested are:
- Split logs from each script into separate tabs.
- Each tab should have a display name set to
coder_script.display_name - Each tab should have an icon set to
coder_script.icon - Each tab should show the exit status code of the last command by a change in color.
Reacted by McKayla はな , Steven Masley, Danielle Maywood, Mathias Fredriksson, Atif Ali and djarbz
Activity
MrPeacockNLB commentedon Nov 21, 2024
Ah... I do not know if tabs are the right solution. We have more than 20 scripts currently and more to come. It may work for less than 10 scripts or so. Maybe it would be better only to show only the agent startup_script output and show the logs of the script as mentioned in #15395 . As a bonus one could see which script has an exit code greater than 0 in the build timeline.
Maybe a seperate tab for logstream-kube events makes sense...
Just my 2 ¢
MrPeacockNLB commentedon Nov 21, 2024
I nice gimick would be if one could see a count down how much scripts are not finished as an indicator...
matifali commentedon Nov 21, 2024
Thank you for the feedback.
Let's allow the output of some scripts to be hidden, by setting a parameter
hide = truefor thecoder_script. Do you think you would need the output of all 20 scripts? The download button would download logs for all of them, making them accessible when needed.I think this will be useful in the logs view, too. We can color-code the tabs based on error codes. Same for Build logs. Red if script returns a non-zero error.
This could be a separate nice-to-have feature request. As some scripts may never finish (running a process)
cc: @dannykopping, @BrunoQuaresma and @chrifro
chrifro commentedon Nov 26, 2024
Here is a draft of how it could look. Let me know what you think @matifali
default view
more than 8 apps
matifali commentedon Nov 26, 2024
This is great @chrifro.
Note
for engineers, we would also need to update the download logs flow to create the zip of files containing logs from individual
coder_scriptresources.MrPeacockNLB commentedon Nov 26, 2024
For daily usage there is no need to see logs in different tabs. This is only needed when debugging or developing a feature of the template. For enduser a.k.a. developer should be the "all" tab enough to follow progress in the build steps (if it the default tab). As already mentioned if one could open the logs via #15395 then this would be enough for debugging and developing purpose from my point of view. There may be other opinions about this. Hiding the scripts is useful as they may have never any output.
MrPeacockNLB commentedon Nov 26, 2024
@chrifro please consider also the optional logs from logstream kube. See #12929
MrPeacockNLB commentedon Nov 27, 2024
Also an indicator of last exit code should be useful. See coder/coder-logstream-kube#61 . It could be mark Logstream Kube in red when a non 0 exit code has happend.
Please feel free to move this to a better issue...
djarbz commentedon Oct 3, 2025
Personally, I would like to have the tabs even as a "developer". If this gets implemented, what is the harm in showing the tabs? The "All" stream that is shown currently can and should be the default tab, but I see no reason why we can't have more.
We could also have a setting in the template to hide for everyone or hide by role similar to how dynamic options can be hidden for non-admins.
matifali commentedon Feb 5, 2026
@chrifro do you think it's time to revisit this. I think it's a very important improvement we can make to solve the issue we see in #21946.
chrifro commentedon Feb 6, 2026
Sure I can look into it. What it the solution (shown here) missing @matifali ?
matifali commentedon Feb 6, 2026
@chrifro I think this is good enough. We just need to validate with Engineering and find out if we need any backend changes.
Also, how do we want to aggregate and show this information on the larger health banner from the individual scripts? #21946
matifali commentedon Apr 16, 2026
@chrifro @jakehwll when can we close this?
jakehwll commentedon Apr 16, 2026
Not sure why this reopened, I think its fine to close 🙂
Theres more work to be done but the tabs are implemented which this describes.