Heroku run output removed in SSO authentication workflow

[deppy]

This project is for the Heroku CLI only and issues are reviewed as we are able. If you need more immediate assistence or help with anything not specific to the CLI itself, please use https://help.heroku.com.

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

In an unauthenticated heroku-cli session, running heroku run:detached 'command' -a $app swallows the output about the command being run and how to tail the logs. When I run the command with an expired session it sends me to the SSO flow in the browser and then when it comes back to the CLI, the output does not show me that the command was run successfully or how to tail the output of my detached run command.

I'm attaching a screenshot which shows the lack of output in the first command where the output is chopped off due to going through the auth workflow and the second which does show the output

And just to confirm it ran twice, I looked in the logs and saw that it did run 2x, and the 2nd run dyno matches the number of the 2nd command output:

Jun 15 14:11:15 ********************* app/run.9427 i like cake 
Jun 15 14:13:01 ********************* app/run.2872 i like cake 

What is the expected behavior?

I would expect the information output to the terminal to be the same in an authenticated or unauthenticated session.

Extra info:
CLI version: heroku/7.54.1 darwin-x64 node-v12.21.0
OS: MacOS 10.15.7