Anjan Nath

> 1. connect to status_change channel with curl -GET -i --unix-socket /crc-http.sock "http://localhost/events?stream=status_change" > 2. start crc with crc start the events are shown only when starting via the api...

Tested locally and functionality is working as expected, LGTM. it'd be nice to have more detailed commit messages explaining the changes in each commit

Since now we have https://github.com/crc-org/crc-extension we can remove the Tray and also alter the API as needed for the extension

In the coming release (2.29.0) we'll add a Deprecation message when user switches the preset to podman using `crc config set preset podman` and in the next release (2.30.0) we'll...

If we change the crc home dir, we should also do automated migration of the config file to the new location. I think XDG base directory as the default and...

I think for the extension's use case, we are good with only adding this capability to the API, do we want a CLI interface also to see the stored pull-secret...

> We can enable it by default because it is host to vm communication, if user don't want they can use config option to set it `false`. I'd also be...

I mean crc should detect the shell correctly as `bash` or `zsh`, etc. when running in a WSL terminal and not detect is as `cmd` > that would be similar...

also the paths have to be translated for WSL, currently after adding `bash, zsh` to the supported shells list in https://github.com/crc-org/crc/blob/97705a008eda801ba291fe3b9982af464d4759e0/pkg/os/shell/shell_windows.go#L12 it gives us windows style paths: ``` annant@DESKTOP-J8H86J0:/mnt/c/Users/anath/go/bin$ ./crc.exe...

Later we could also focus on packaging it for `homebrew`, `chocolatey` and `rpms`, `debs` this'd provide better install/upgrade experience