Use GitHub remote control locally.
Best when your computer can stay online and the task depends on its files, services, credentials, hardware, or network position.
▍ Independent guide · official docs checked
Run Copilot CLI remotely. Turn the laptop off.
GitHub’s remote control reaches a Copilot CLI process that is already running. Put that process in a persistent Terminalbox pane and your laptop stops being the server—while GitHub.com, GitHub Mobile, and the full browser terminal remain available as interfaces.
- Copilot CLI preinstalled
- Persistent tmux session
- Bring your GitHub account
The host decides what survives
Official local path
Phone or web→Your computer
Your local terminal and Copilot process must remain online.
Hosted-pane path
Any device→Terminalbox pane
The pane remains the host after your laptop disconnects.
Use the official feature—move its host
Remote control and hosting solve different problems.
Remote control gives Copilot CLI another interface. Terminalbox gives the CLI an always-on Linux machine and a full terminal. They can be used separately or together.
Run Copilot CLI in a hosted pane.
Best when the work should continue away from your computer or you need the whole shell, dev server, logs, and tmux session from another device.
Side by side
Compare the operating model, not the label.
GitHub’s current documentation says the originating machine must be online with the CLI session actively running. It explicitly supports directories outside Git and repositories hosted somewhere other than GitHub.com. Check the official remote-control guide before relying on those requirements.
| Question | Local + GitHub remote control | Terminalbox Copilot pane |
|---|---|---|
| Where does Copilot CLI run? | On the computer where you started the terminal session. | Inside a paid Terminalbox Linux pane. |
| What must stay online? | Your computer, network connection, terminal, and Copilot CLI session. | The hosted pane. Your laptop or phone is only a client. |
| What can you open remotely? | The Copilot session on GitHub.com or GitHub Mobile. | The full terminal in Terminalbox, plus optional GitHub remote control. |
| Does remote control require a GitHub repository? | No. GitHub supports directories outside Git and repositories hosted elsewhere. | No. A GitHub repository is optional here too; it adds repository-level discovery. |
| Are laptop files present automatically? | Yes. The process remains in the local working directory. | No. Clone or upload the project and configure only what the remote task needs. |
| What do you pay? | Copilot CLI is included with Copilot plans, subject to plan usage and policy. | From €6/month for the pane, plus your separate Copilot access. |
Terminalbox is independent from GitHub. “GitHub” and “Copilot” identify GitHub products; no endorsement or partnership is implied.
Hosted remote-control workflow
Make the pane the computer that stays on.
- 01
Create a GitHub Copilot CLI pane.
Choose the prepared template, enter
/login, and complete GitHub’s browser flow. - 02
Clone the repository into the persistent workspace.
Only move the code, credentials, and configuration the hosted task actually needs.
- 03
Optionally enter
/remote on.GitHub supplies a link and QR code when the account and live session meet its current remote-control requirements. A GitHub-hosted repository is optional.
- 04
Disconnect the laptop.
Return through GitHub’s session interface or reopen the complete Terminalbox terminal from any browser.
Installation and authentication follow GitHub’s official Copilot CLI documentation. Terminalbox never receives your GitHub login or Copilot credits.
Practical boundaries
Questions to answer before paying.
Can Copilot CLI remote control keep working after my laptop sleeps?
Only if Copilot CLI is running somewhere else. GitHub requires the originating machine and terminal session to stay online. A Terminalbox pane can be that always-on machine, so your laptop no longer hosts the process.
Does Terminalbox include a GitHub Copilot plan?
No. Terminalbox charges for the persistent Linux pane. Copilot access, credits, organization policy, authentication, and provider charges remain under your GitHub account.
Can I use GitHub Mobile with a Terminalbox Copilot pane?
Yes, when GitHub remote control is available to your account. Run /remote on inside Copilot CLI, then open the session through GitHub.com or GitHub Mobile with the same account. A GitHub-hosted repository is not required.
When is local remote control the better choice?
Use the official local path when the exact files, credentials, local services, or hardware on your computer matter and you can keep that computer online. Use a hosted pane when laptop independence and a persistent full shell matter more.
One persistent Copilot terminal
Keep the CLI. Replace the laptop as its host.
Base includes one paid pane with 2 vCPU, 4 GB RAM, and a 50 GB persistent workspace for €6/month. Your GitHub Copilot plan remains separate.