One extra improvement here is that we can use Coders icon right next to the text. This would require creating a custom font with all the extensions logos in it so might be out of scope here 🤔

For example the Git extension adds this which gives context to what the text after it means:

--

Currently in this PR, it just shows whatever the first item is which is not intuitive for users to recognize as being related to Coder

This is just using the logo SVG:

It seems a bit big tbh, maybe theC alone or the dash can be smaller?

I prefer the no logo, or if we can make the logo smaller, such as 70% of its original size.

I prefer the no logo, or if we can make the logo smaller, such as 70% of its original size.

Agreed, the logo is a bit too big, here's how it looks if the logo is scaled down to 60% of its original size:

Ideally there should be a more "square" form of the Coder logo that would fit the VS Code environment more. Here it just means that the logo is made smaller and so there are invisible spaces around it. For example, if you point to the left of it you get the hover due to the invisible padding:

@rachelmullenax can we have a square logo for use cases like this?

I wonder if some generic icon indicating a remote resource would work better than the logo? Like a cloud icon or something.

I wonder if some generic icon indicating a remote resource would work better than the logo? Like a cloud icon or something.

I think this could work well since the VS Code codions fit well within the ecosystem.

The only worry here is that just having an icon won't give enough of an indication that this isCoder's stats but could be fine since other extensions use those so it's consistent 🤔

The only worry here is that just having an icon won't give enough of an indication that this is Coder's stats but could be fine since other extensions use those so it's consistent

True! But yeah I like the idea of consistent-looking icons in the status bar. I think mostly the logo being so thick and bold compared to the other icons is what throws me off. But I will defer to what you and@matifali think.

Let's keep using the Coder logo. We can update when@rachelmullenax gets back.

Alright, I'll keep the 70% one but I did have to write afantasticon script to generate the font from the logo. Should I push everything there and possibly make it part of the script? Or just push the font that contains the logo?. (There is no way to use custom logos in the statusbar without adding a custom font...)

The former will make sure we can easily add more icons but requires some discussion since it should be added to the build workflow, while the latter is just a singlewoff2 file that contains the scaled down logo 🤔

Alternatively, we can just use one of the default VS Code logos above (for now)

Alternatively, we can just use one of the default VS Code logos above (for now)

I am not familiar with the complexities of custom fonts, so let's use the Dashboard logo, specifically the round gauge.

Alternatively, we can just use one of the default VS Code logos above (for now)

I am not familiar with the complexities of custom fonts, so let's use the Dashboard logo, specifically the round gauge.

Alright, will do, adding a custom font is not difficult but requires some thought and makes sense to do after we have the logo

This is how it looks like when it is failing (but with an error message):

When it works it looks like this:

If there are no errors but the metadata is empty, then we simply hide the status bar item.

Looks awesome thank you!

If there is a template with nometadata block incoder_agent, how do we handle it? Do we hide it completely or show an error? If it's the latter, then we should probably look into hiding it from the status bar.

If there is a template with nometadata block incoder_agent, how do we handle it? Do we hide it completely or show an error? If it's the latter, then we should probably look into hiding it from the status bar.

Currently if themetadata is undefined (or an empty list), then nothing is shown in the tree view nor the status bar item. See this thread:#555 (comment)

Should we hide it when there's an error since it seems to cause some confusion for users, see#595 (comment)

It sounds like this led to a real bug being caught, so showing it had real value. Maybe it means we need to somehow make it clearer what the error means through better UX.

I like your idea of introducing retries, that seems like it should solve the issue of transient errors at least.