VS Code Agent Host Runs in the Background: Choose Phone Control, Local Machines, or Cloud Sessions
Local sessions can outlive editor windows, remote machines must stay running, and computer use remains experimental
GitHub announced its VS Code Copilot Universe release on October 28, 2026. The new Agent Host lets sessions continue after a project folder or editor window closes, can run on another machine through Remote SSH or dev tunnels, and can be directed from GitHub Mobile. A local or remote machine and its Agent Host must remain running when the work executes there. Computer use is experimental and requires approval for each application. The open Agent Host Protocol lets custom clients reconnect to the same live session. This article compares local, remote, and cloud placement, then provides a first-run checklist for availability, permissions, desktop access, and recovery.
Key takeaways
By ENHE AI · 2026-11-02 · AI-assisted drafting and editorial checks.
Direct answer: Execution location determines tools, uptime, and cost boundaries
GitHub announced the VS Code Copilot Universe release on October 28, 2026, and Agent Host lets work continue after a project folder or window closes. Local execution still depends on the machine, while cloud execution can continue after shutdown but enters cloud permission and compute boundaries.
How to choose local, remote, or cloud execution
Local Agent Host fits tasks that need local files, tools, or desktop apps. Remote SSH or a dev tunnel fits dedicated dependencies. The remote machine and its Agent Host must remain running. Cloud sessions run on GitHub infrastructure and can continue after a laptop sleeps, but repository permission and shared entitlement still matter.
Phone control and reconnection entry points
Run code agent host --github-environment from the project directory to monitor progress, steer work, or start a task from GitHub Mobile. The open Agent Host Protocol lets connected clients stay synchronized and catch up after reconnecting. The expected result is the same live session, not an untraceable copy.
Computer use and permission boundaries
Computer use requires approval for each application and remains experimental. Start with one application that has no sensitive data and record what it reads, clicks, and types. Organizations can disable it by policy. If control behaves unexpectedly, stop the session and revoke permission instead of retrying around approval.
Frequently asked questions
Will a local task always continue after VS Code closes?
Agent Host separates the session from a window, but the local or remote machine and Agent Host must still be running.
Does phone control automatically move work to the cloud?
No. The phone is a control surface; execution remains in the registered local, remote, or cloud environment.
Why this matters
The update separates an editor window from the agent runtime. That improves continuity but makes machine choice, network access, desktop permissions, and stopping behavior more important because background work can otherwise widen unseen impact.
Related tools and reading
These pages support the same task, workflow, or risk boundary.
- Continue a Copilot app session in VS Code
- Copilot local sandbox generally available
- Copilot cloud sessions and shared entitlement
Conclusion
Choose local Agent Host when local tools are needed and the machine can stay online, a remote machine for dedicated dependencies, and cloud execution when work must continue after shutdown. Start with one repository and one low-risk tool, then validate disconnect, reconnect, stop, and logs before expanding.
What this means for everyday users
Computer use requires approval for each application and remains experimental. Start with one application that has no sensitive data and record what it reads, clicks, and types. Organizations can disable it by policy. If control behaves unexpectedly, stop the session and revoke permission instead of retrying around approval.
Related reading
GitHub Copilot Local Sandboxing Is Generally Available
GitHub made local sandboxing generally available on October 7, 2026 for GitHub Copilot CLI, the GitHub Copilot app, and VS Code sessions that use Agent Host. The feature applies operating-system controls to agent-run commands so users can restrict filesystem paths, network access, Git credentials, and supported local tools. GitHub's documentation also sets important boundaries: local sandboxing is off by default, CLI and app settings are separate, remote MCP servers are not sandboxed, and some in-process file tools enforce policy on a best-effort basis rather than through the operating-system sandbox. This guide focuses on verification rather than the toggle itself: enable the feature, test denied reads and writes, test blocked network access, confirm credential masking, inspect MCP placement, and configure fail-closed behavior where the organization requires enforcement.
GitHub Copilot Sessions Can Move to VS Code With Context, Diffs, and Worktree Intact
GitHub has documented a handoff from a Copilot app session to Visual Studio Code. The workflow keeps the session context, changed-file diff, and the same isolated worktree, so a developer does not need to rebuild the task history in a new chat. This article explains the prerequisites and provides a practical review sequence: open the session, inspect the diff, edit locally, run the relevant tests, and decide separately whether to push. The feature is useful when agent work needs human judgment or local tooling, but continuity is not proof that the generated changes are correct. Repository permission, the same GitHub account in both applications, and an existing session with changes are still required.
GitHub Copilot Cloud Sessions Are GA: How Cross-Device Work Uses Actions Entitlement
GitHub made its connected Copilot cloud experience and cloud sandboxes generally available on paid Copilot plans on October 28, 2026. A user can start a task on github.com, GitHub Mobile, Copilot CLI, the Copilot app, VS Code, Slack, or Microsoft Teams, then continue the same session elsewhere. The included Actions compute entitlement becomes one shared, dollar-based pool for standard hosted runners, cloud sandboxes, and certain larger runners. Billing for cloud-sandbox usage begins in November 2026, so cross-device convenience can affect the same budget used by builds. This article helps users check repository scope, write access, tool permissions, entitlement consumption, and stop conditions before their first cloud session.
From Chat Boxes to Personal AI Companions: AI Assistants Are Entering the Desktop Execution Era
AI assistants are moving from answering questions toward continuing real tasks. AI agents, MCP tool ecosystems, personal memory, and local workbenches are pushing this shift together. For users, the real value is not another chat box, but less repeated context setup and more continuity from thinking to doing.
GitHub Copilot Enters Xcode’s Built-In Assistant Preview: Should You Switch From the Extension?
GitHub announced on 2026-11-04 that Copilot is available in Xcode’s built-in coding assistant as a public preview starting with Xcode 27.3 beta. The setup requires a Mac running macOS Tahoe 26.6 or later, and GitHub says all Copilot plans are supported. The existing GitHub Copilot for Xcode extension remains a separate option, so this is a workflow choice rather than a forced migration. This guide provides a bounded comparison: verify the beta environment, run the same small coding task in the current extension and built-in assistant, compare context, edits, permission prompts, tests, and recovery, then keep the route that produces the clearest reviewable evidence.
Gemini Omni 1.2 Flash Adds 15-Second Video: What Creators Should Validate First
Google launched Gemini Omni 1.2 Flash on 2026-11-05 with native clips from three to fifteen seconds, multi-turn conversational editing, stronger reference following, and a listed API price of $0.07 per second for 720p video after a 30 percent reduction. A separate Google Vids announcement says Google Account and Workspace users can generate up to three fifteen-second videos per month at no cost. This guide turns those facts into one bounded creator test: prepare a simple reference pack, generate a single shot, inspect identity and product details at several points, make one controlled edit, record the real cost or allowance used, and keep a shorter fallback if the longer clip drifts.
