▍ Free local generator · GitHub docs checked August 5, 2026

Copilot CLI remote control setup generator.

Build the smallest official setup for steering a running GitHub Copilot CLI session from GitHub.com or GitHub Mobile. Choose one-session or always-on remote control, then add only the keep-alive behavior you need.

Runs locally No repository required No account required

01 · Choose

Configure the host you already have.

Install or verify Copilot CLI

Remote-control behavior

Enable inside this session Enter /remote on after Copilot starts. Launch one remote session Start with copilot --remote. Enable every interactive session Generate the official remoteSessions setting.

Keep the host awake

Current GitHub behavior: the host machine and interactive terminal must stay online. A GitHub-hosted repository is not required, although GitHub repositories add the session to their Agents tab. Verify in GitHub’s documentation ↗

02 · Review

Your remote-control plan.

Shell

# 1. Install or verify GitHub Copilot CLI
npm install -g @github/copilot

# 2. Authenticate with your GitHub account
copilot login

# 3. Launch Copilot CLI
copilot

# Enter these inside the interactive Copilot CLI session
/remote on
/keep-alive busy

Remote interface GitHub.com or GitHub Mobile

Session owner Same GitHub account only

Host requirement Online terminal + Copilot process

Before you start

Four requirements, with one easy-to-miss boundary.

Eligible Copilot access

Your GitHub account needs Copilot access and any organization policy must allow CLI.

Authenticated CLI

Use copilot login and open the remote session with the same account.

Live interactive session

Remote control reaches a running process. Session sync alone remains view-only.

The host stays online

Keep-alive prevents sleep. It does not make a powered-off laptop keep running.

03 · Decide where it runs

Keep your laptop when local state matters.

The generated setup is enough when your computer can stay online and Copilot needs its files, services, hardware, or network. Do not pay Terminalbox merely to enable GitHub’s remote-control feature.

Compare local and hosted operation →

When the laptop must turn off

Move the same CLI session to an always-on pane.

Terminalbox Base provides one persistent Linux pane with Copilot CLI preinstalled, 2 vCPU, 4 GB RAM, and 50 GB storage. Your separate GitHub Copilot plan powers the agent.

Keep one Copilot shell running — €6/month

Practical answers

Know what the commands do before using them.

Does Copilot CLI remote control require a GitHub repository?

No. GitHub’s current documentation says remote control can be enabled outside a Git repository and from repositories hosted somewhere other than GitHub.com. A GitHub repository adds an Agents tab entry, but it is not a general prerequisite.

What must remain online?

The machine hosting Copilot CLI, its network connection, and the interactive terminal session must stay online. Keep-alive can prevent sleep, but it cannot keep a powered-off laptop running.

What does /keep-alive busy do?

It prevents sleep while Copilot is working or waiting for your response, then allows normal sleep after the active work is complete. Choose “on” only when the machine should remain awake for the whole session.

Does this generator upload my settings?

No. The plan is generated in your browser. Terminalbox records only bounded page-view and button-action labels, never generated commands, credentials, repository names, or settings.

When would I need a hosted pane?

Use your own machine when it can stay online and the task depends on its local files, services, hardware, or private network. A hosted pane is useful when the work must survive laptop sleep or shutdown and you want the complete terminal from another device.

Installation commands come from GitHub’s Copilot CLI installation guide. Terminalbox is independent from GitHub; no endorsement or partnership is implied.