Hi team! 👋 First, thank you for adding SSH host configuration support in !2888 - it's a great step forward for users with custom GitLab instances! I've been testing this feature and noticed a couple of areas where it could be enhanced to provide a smoother experience: ## 1. Add SSH host prompt during login flow ~~Currently, the login flow asks users about container registry domains, which is really helpful. It would be great to have a similar prompt for SSH host configuration.~~ ~~**Suggestion:**~~ - ~~Add a prompt like: "What domain does this host use for SSH/Git operations?"~~ - ~~Default to the hostname entered in the previous step (since many instances use the same domain)~~ - ~~Allow predefined values similar to how registry configuration works~~ ~~This would make the setup process more intuitive and help users configure everything in one go.~~ fixed with: https://gitlab.com/gitlab-org/cli/-/merge_requests/2928 ## 2. SSH remote detection not working as expected After configuring the `ssh_host` in my config, glab doesn't seem to recognize SSH remotes that match that configuration. will be fixed with: https://gitlab.com/gitlab-org/cli/-/merge_requests/2924 **Steps to reproduce:** 1. Configure host with API at `my.gitlab.instance` 2. Set SSH host as `ssh.my.gitlab.instance` in config 3. Work in a repository with SSH remote pointing to `ssh.my.gitlab.instance` 4. Run any glab command **Current behavior:** ``` None of the git remotes configured for this repository point to a known GitLab host. Please use `glab auth login` to authenticate and configure a new host for glab. Configured remotes: ssh.my.gitlab.instance ``` **Expected behavior:** glab recognizes the SSH remote and maps it to the configured API host ## Context Related to: !2888 Thanks again for all your work on glab - it's an awesome tool! 🙏