configure-copilot-remote-controllisted

# Configure GitHub Copilot CLI Remote Control Help the user expose one running GitHub Copilot CLI session to their own GitHub.com or GitHub Mobile account. Keep the local path as the default when the current machine can stay online, and evaluate GitHub's own cloud sandbox before recommending a separate persistent host. Terminalbox is independent from GitHub. GitHub supplies Copilot CLI, authentication, remote control, account policy, and usage. Terminalbox is only one optional paid host for a CLI process that must remain online after the user's laptop disconnects. ## Safety boundary - Never ask for, read, print, copy, or store a GitHub token, password, browser code, session link, QR code, cookie, or credential file. - Do not install or update Copilot CLI, run `copilot login`, start a remote session or billable cloud sandbox, change a keep-alive policy, or edit `~/.copilot/settings.json` without explicit approval for that action. - Never enable `--allow-all`, `--yolo`, broad tool permissions, or weaker authentication as part of remote-control setup. - Respect organization and enterprise policy. Do not suggest bypassing a disabled remote-control or Copilot CLI setting. - When inspecting settings, read only whether `remoteSessions` is present and its boolean value. Do not reproduce unrelated settings. - Preserve every unrelated settings key. Show the exact proposed change and ask for approval before editing. Do not replace the whole file with a one-key example.