Summary

When your token expires, fly set-pipeline displays a link to your concourse login page, however there is no prompt to actually enter the token. It just hangs. This forces the user to press control-c then run fly -t ci login.

Steps to reproduce

First login to concourse using fly -t ci login.
do a fly -t ci set-pipeline with your test pipeline
Don't use the fly instance and let your login token expire.
Once the token has expired attempt to do a fly -t set-pipeline again with a small change.

Expected results

I expect either fly -t ci set-pipeline to either tell you the token is expired and dump you back to the prompt or do the login flow and prompt for the token.

Actual results

fly -t ci sp -c backup.yml -p backup -v .....
could not find a valid token.
logging in to team 'main'

navigate to the following URL in your browser:

  https://ci.hnrglobal.com/login?fly_port=46557

(I attemped to paste token here)
(nothing happens - have to control-c)
$ fly -t ci login
logging in to team 'main'

navigate to the following URL in your browser:

  https://ci.hnrglobal.com/login?fly_port=36895

or enter token manually (input hidden): 
target saved

Additional context

running arch linux (btw} unsure if this is an issue on other platforms.

Triaging info

• Concourse version: 7.13.2
• Browser (if applicable):
• Did this used to work?