How to Recover When Local Agent Reports Token Invalid or Denied?
Reacquire the current account command, reset credentials if necessary, and restore affected connections.
Confirm the Terminal Actually Reports Credential Issues
Local Agent provides clear prompts when tokens are rejected by the server or account tokens have been reset, and may proactively exit. Do not attribute connection relay timeouts, insufficient system permissions, or missing tools to token invalidity. First confirm that you are running the complete command copied from the current account settings, not placeholder text from the page, old screenshots, or connection info given by another user.
Recover Using a New Command
Go to Settings → Remote Control to recopy the command and start it on the target machine. If there is a clear prompt that credentials are invalid or at risk of leakage and a reset is needed, first finish any tasks currently using the related machine. Resetting will disconnect existing connections for that account; afterward, each machine that needs to use it must restore its connection. Old commands should no longer be used, and do not repeatedly start the same invalid credentials on multiple terminals.
Verify New Connection and Protect Diagnostic Information
After seeing the ready prompt, return to Settings to verify the hostname and that "Remote Control Connected" is shown, then confirm the environment selected by the Agent. If the new command is still denied, record the error message and occurrence time, check whether you are logged into the correct account, and do not give the full command to others for testing. Remove tokens, authentication address parameters, and private information from feedback; after successful connection, also separately check task permissions and quotas.