This message was deleted.

Seems to have been fixed by generating a new auth token and then authenticating using

gt auth --token <my_token>