Accessibility Adjustments

Use these optional tools to adjust reading and display preferences. These tools cannot resolve every accessibility barrier. Please contact the website owner if you need assistance.

  • Text adjustments
  • Content scaling 100%
  • Font size 100%
  • Line height 100%
  • Letter spacing 100%
  • Colour adjustments
  • Orientation adjustments

Copilot CLI adds VS Code shortcut and searchable settings

Listen to this article

GitHub Copilot CLI 1.0.107, released November 6, brings a /code command for opening the current session in VS Code. It also adds opt-in local session management and mentions. For developers moving between a terminal and an editor, this is a useful workflow release rather than a new foundation model launch.

The other headline change is easier configuration. GitHub’s weekly announcement says /settings now brings plugins, MCP servers and other controls into one searchable dashboard. That gives developers a clearer place to inspect their setup before starting work.

Moving a session into VS Code

The new command sits alongside an existing integration. GitHub’s VS Code connection guide describes selection context, live diagnostics, visual file diffs and access to CLI transcripts. These capabilities should not all be described as new in 1.0.107.

The documented connection requires a trusted workspace. Automatic connection matches the CLI working directory to an open workspace, and /ide can change the connection. Only one IDE instance can be connected at a time. A locally running CLI cannot connect to a workspace inside a remote Codespace, although the CLI can connect when it runs inside that Codespace.

Review behavior depends on permissions. GitHub says the visual accept-or-reject diff is skipped when file editing has already been allowed without approval. Moving into an editor therefore does not, by itself, add a review checkpoint.

A sensible first trial is a small change on a disposable branch. Check that the intended repository is open, inspect the patch, run the relevant tests and confirm that the result stays within the request. This is a suggested evaluation workflow, not a ByteForward test result.

A dashboard helps you inspect the effective setup

The settings documentation describes searching setting names and descriptions, inspecting values and changing them from the interactive interface. Personal choices persist across sessions. Most changes apply immediately, while some require a restart.

Repository or organization settings can override a personal value. If two developers see different behavior, comparing only their preferred settings may miss the cause. Check the applicable repository and organization configuration before treating a difference as a model problem.

For a team, keep a short record of the configuration used for important evaluations. Include the CLI version, selected model, enabled integrations and permission mode. A repeatable setup makes it easier to separate a tool change from a prompt change.

Session access and extension sandboxing remain separate choices

The release notes limit session mentions to opted-in local sessions. They also introduce a Sandbox extensions setting for running extension processes inside the sandbox. The notes do not establish that every session becomes accessible or that extension sandboxing is enabled by default.

Those are distinct decisions. An assistant may need context from another task without needing broader execution privileges. Start with the smallest useful scope and check what is enabled before asking it to coordinate work across sessions.

GitHub’s command reference still labels CLI extensions experimental. It distinguishes Load & Augment, which allows agent management, from Load Only and Disabled. Those extension modes describe whether extensions load and how they are managed. They should not be confused with the new sandbox control.

Terra availability predates this release

Version 1.0.107 lists GPT-6.1 Terra under New models when the account has access. GitHub had already announced Terra availability on October 26 for Copilot Pro, Pro+, Max, Business and Enterprise, with a gradual rollout. Business and Enterprise administrators can control access through model policy. Usage is billed at provider list pricing.

For readers comparing direct model selection with automatic routing, our Copilot Fusion guide explains the separate routing and orchestration options. A new menu entry is not evidence that an organization has enabled that model or that its use is free.

ByteForward reviewed the official release notes and documentation for this article. We have not independently tested version 1.0.107.

Featured image: AI generated editorial illustration, not a product interface. GitHub Copilot logo from GitHub’s official brand assets, used for news reporting. No endorsement implied.

Jordan Reid
Jordan Reid

Jordan Reid is focused on AI tools, agents, developer products, and the way technology changes everyday work. Jordan approaches a launch from the user’s side of the screen. What can it actually help someone finish? The voice is practical, conversational, and skeptical of products that turn a simple job into five new settings. Coverage follows coding assistants, creative software, browser agents, and the workflows around them, with attention to pricing, permissions, setup, and the human work that remains.

Leave a Reply

Your email address will not be published. Required fields are marked *

Gravatar profile