@zayaan, I'm glad we could figure it out.
FYI, for everyone else - he was able to fix it by deleting the contents of his c:\users\(username)\.TRIGGERcmdData folder. Then when he ran the TRIGGERcmd Agent, it re-prompted for a token and re-created his computer in his account.
In hind-sight he should have backed up his commands.json first (oops).