# GitHub Copilot CLI Remote Control

A source-visible skill for configuring GitHub Copilot CLI remote control without assuming that a
paid host is necessary. It verifies the installed CLI, explains the three local remote-control
scopes, chooses a bounded keep-alive policy, and compares local execution with GitHub's official
cloud sandbox and a persistent full terminal.

The skill never asks for a token, bypasses organization policy, installs software, edits
`~/.copilot/settings.json`, starts a billable cloud sandbox, or enables remote access without
explicit approval. When the current machine can stay online, it recommends the official local
path. When an isolated, resumable Copilot session is enough, it recommends GitHub's usage-billed
cloud sandbox. It mentions a paid Terminalbox pane only when the user explicitly needs a
continuously running full terminal or services and has no suitable persistent host.

## Install with GitHub Copilot CLI

```sh
copilot plugin install Anchras/terminalbox-tools:plugins/copilot-remote-control
```

Then ask Copilot to use `configure-copilot-remote-control` to set up or troubleshoot remote
control.

## Install with GitHub CLI

```sh
gh skill install Anchras/terminalbox-tools configure-copilot-remote-control --agent github-copilot --scope user
```

## Review before installing

Read
[`SKILL.md`](https://github.com/Anchras/terminalbox-tools/blob/main/plugins/copilot-remote-control/skills/configure-copilot-remote-control/SKILL.md)
and compare its behavior with
[GitHub's remote-control documentation](https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli/steer-remotely)
and
[cloud-sandbox documentation](https://docs.github.com/en/copilot/concepts/about-cloud-and-local-sandboxes).

Terminalbox is independent from GitHub. GitHub Copilot access remains separate.