When Should Connection Tokens Be Reset and Which Machines Are Affected?
Reset only when credentials are indeed problematic, and arrange recovery for all affected connections.
Applicable and Non-Applicable Situations
Consider resetting the connection token only when the terminal explicitly indicates token invalidation or server rejection, or when you confirm that the full connection command has been leaked. Ordinary network disconnections, client idle exits, uninstalled tools, and file permission errors should not be handled by resetting first. Record the error type first and confirm it is a connection credential issue to avoid expanding a single machine failure that can be recovered individually into multiple connection interruptions.
Operations in Remote Control Settings
Open Settings → Remote Control. When connection settings need to be displayed, you can select "Connect to Another Machine." After copying the command, this settings area will provide an entry for "Reset Token." Before executing, finish and save tasks currently using the related computer; a success prompt will indicate that existing connections have been stopped. Do not repeatedly click reset when task status is unknown, and do not keep old commands as reliable backup access.
Recover with New Credentials and Re-Verify
Resetting will mark all existing connections under the account as disconnected, not just the currently selected CLI. The necessary machines must then re-establish connections individually; the CLI should copy and use the new command again, and the desktop should confirm its connection has been restored. After completion, check each machine’s name and current task environment. Old credentials should no longer be propagated; when troubleshooting, only submit sanitized error text and do not provide new commands as proof.