Add wingver command with ASCII branding (similar to neofetch)

[PXOpenSource]

Relevant area(s)

WinGet CLI

Description of the new feature / enhancement

I propose adding a new command (or an alias) like wingver that displays the current WinGet version alongside a stylish ASCII art logo of the Windows Package Manager.The concept:In many Linux environments, tools have "branded" version outputs. Instead of just a plain number like v1.8.1911, running wingver should display:An ASCII art logo of WinGet (the stylized "W" or the package icon).System info summary: OS Version, WinGet version, and CPU architecture.Example of how it could look:

Why it's cool:Branding: It gives WinGet a recognizable visual identity in the terminal.User Experience: It's much more satisfying to see a "pro" status screen than a single line of text.Ease of access: wingver is short and easy to remember for debugging and sharing environment info.

And one more idea. Add Shortcut Support (e.g., Ctrl + Alt + T)I suggest adding hotkey support for quicker interactions. For example, using Ctrl + Alt + T to quickly trigger a specific action, such as opening a "Top/Trending" packages view or instantly focusing the search bar in the terminal. This would bring a more "pro-user" desktop experience to the CLI.

Proposed technical implementation details

No response

[denelon]

We've got several folks who prefer not to have these kinds of visualizations.

I think this would be a "fun" type of thing to add to the client, but I suspect most folks would prefer just to keep it simple as it is. I could see maybe some "customization" type actions to enable something like this.

FYI. Running winget --info provides lots of context about WinGet and the environment it's running in as well. If you have sixels enabled you'll get an icon. Example snippet from the top of the output:

[PXOpenSource]

We've got several folks who prefer not to have these kinds of visualizations.

I think this would be a "fun" type of thing to add to the client, but I suspect most folks would prefer just to keep it simple as it is. I could see maybe some "customization" type actions to enable something like this.

FYI. Running winget --info provides lots of context about WinGet and the environment it's running in as well. If you have sixels enabled you'll get an icon. Example snippet from the top of the output:

Thanks for the feedback, @denelon!I completely understand the need for minimalism in a tool like WinGet. However, what if we implemented this as an optional feature toggle in settings.json?It could be a great "quality of life" addition for power users or those transitioning from Linux who are used to having a more visual environment summary (like neofetch/fastfetch). This way, the default experience remains clean and simple, but users who want that "branded" feel can easily enable it.I'd be happy to keep this open if you think an optional customization approach is worth considering! But if you still don't want to add this feature, I'll close the issue, it's not hard for me to do it.

[denelon]

Feel free to keep it open. It might be something someone would like to contribute. Maybe something like a "customize" command could walk folks through the various settings. They aren't super easy to "find" if you don't know what you're looking for. I wouldn't want a different "first run" experience though since lots of folks are already using WinGet in automation scenarios.

[PXOpenSource]

Hi @denelon,I’ve put together a small prototype to better illustrate my vision for the winget customize (or onboarding) command. I think it would be great if it looked something like this:

Key ideas behind this UI:Interactive Toggles: Users can easily switch features (like Branding, Telemetry, or the Rainbow Progress Bar) without manually editing the settings.json.Visual Branding: The ASCII logo gives the tool a professional and recognizable look, but it can be easily disabled by those who prefer a minimalist style.Discovery: It makes "hidden" experimental features more accessible for new users.I believe this "Customization Hub" approach solves the concern about minimalism while giving power users the aesthetics they enjoy. What do you think about this interactive style?

[denelon]

This might fit better with the proposed TUI scenario.

I've been contemplating what happens if the user runs winget with no arguments. Today it displays the help, but that could be a way to enter into a TUI that would provide a better experience for users who prefer a TUI.

Related to:

• Make a TUI for WinGet #6034

[PXOpenSource]

@denelon I think I'll post a screenshot of the interface at #6034