Загрузка видео...
Не удалось загрузить видео
Need to step away or just want to continue working on a different device? You can now remote control GitHub Copilot CLI sessions from any device. Just run /remote to continue with a single click.
195,906 просмотров • 5 месяцев назад •via X (Twitter)
Комментарии: 34

The ability to remote control GitHub Copilot CLI sessions on web and mobile is now in public preview. Try it out and let us know what you think.

lol every company at this point is just copying each other claude first then cursor now copilot next is google?

I keep getting this error message when I attempt to the "/remote" command. @github @GitHubCopilot @tiagonbotelho any help??

@tiagonbotelho I was just asking myself a few hours ago when a remote control version of Copilot would come out. Can’t wait to try this out.

Remote sessions from anywhere is a big productivity boost.

Opus 4.6 (6x) ??? Since when? And why?

Remote session handoff is the missing piece. Half my dev work starts on the laptop and continues on the phone while waiting for someone. If /remote syncs context cleanly this changes how I plan coding between meetings.

This is actually huge for anyone switching between machines mid-session. No more losing context on what you were working on.

Noto que ahora los premium request estan “incluidos” en mi suscripción. Esto es un bug?

The little detail that nobody tells: you need to do it over a git repo that is HOSTED ONLY ON GITHUB. This is the most stupid decision you guys have ever taken and a great way to waste effort in front of Claude, after getting late for the same feature. Terrible 🤦🏻♂️

Congratulations 👏

Can we just show the url instead of hyperlink in terminal? Apparently I want to open it through ssh.

Cinamon! The legendary girl who launched Terminal or is another Cinamon? This feature is really great, I personally just ssh directly with my computer user and password but this looks better, a complete webUI connected directly to the terminal sounds like a dream

finally someone did what the terminal deserved 10 years ago. cli sessions you can pick up from any device should've been the default

@GitHubSupport I lost access to my account because SMS 2FA is not supported for my country (Kazakhstan) anymore. I still have my login, password, and email, but I cannot receive the SMS code. Is there any way to recover access or disable SMS 2FA? This worked before

Remote session control means AI-assisted coding can survive context switches — the model's project context doesn't reset when you switch devices. That continuity is underrated; starting fresh on a new machine is one of the most friction-heavy parts of dev workflows.

I don’t hate you anymore ❤️

@satyanadella Its like any other tool?

I want to try it, but unfortunately I can't. I have an issue with renewing my subscription, and I opened a ticket to support 9 days ago, but no luck.

Love this, super handy when I gotta hop between devices. One-click remote? Total lifesaver, thanks!

Been working on Airlock Approver for a while. Even Airlock is Human-In-The-Loop kind of app we are working on product agnostic remote sessions right now. End-to-end encryption, blind gateway. We have SDKs for different languages, n8n and OpenClaw. Checkout

Thank you for taking care of our addiction

Remote Copilot CLI sessions are huge for async workflows. The next unlock is stateful handoff — where an agent can pause, serialize context, and resume on another device without losing the conversation thread.

Sessions that travel with you.

The device-handoff pattern is what agents have been missing. Most of us run long jobs on a beefy workstation but want to check in from a laptop mid-coffee. The interesting architecture question is state persistence - does /remote snapshot the full context or re-hydrate from logs?

What made you pick CLI for this instead of just syncing the conversation state across devices?

Please provide private app build options for free users for India

Remote session continuity matters more than it gets credit for — context loss when switching machines is real friction in async work. Handing off a Copilot CLI session to any device without losing state is the kind of UX detail that compounds into genuine productivity gains.

Uh, this doesn't seem to work if you use ssh vs https. Is that right? If so, please fix asap as that's lame.

github copilot cli sessions can be controlled remotely now, that's a big productivity boost for developers working on multiple devices, wonder how it handles multiple sessions simultaneously

Great /remote update for Copilot CLI 👏 You run ghcr .io today. is available — the perfect .ai upgrade for GitHub's AI container future. Brand protection + instant AI signal. DM if interested. Quick & clean. #GitHub #Copilot #AI

GitHub just made Copilot CLI truly portable. One /remote command and your entire session travels with you across devices. Perfect for those moments when you need to grab your phone and keep building without breaking stride.

epic

Wheel Whule number 1! Don’t leave the house without Toilet Paper! All other rules…are just Noise! @grok










