Unlocking GitHub Copilot: Terminal and Workspace Control in VS Code

The landscape of software development is constantly evolving, with AI-powered tools like GitHub Copilot leading the charge. While many developers are familiar with Copilot’s prowess in code completion, its true potential as an “agentic assistant” shines when it gains the ability to interact directly with your development environment—specifically, by running commands in the terminal and making changes across your workspace. This guide will walk you through enabling these advanced functionalities in Visual Studio Code (VS Code), transforming your Copilot experience.

Why Grant Copilot Terminal and Workspace Access?

Imagine not just getting code suggestions, but having an AI assistant that can understand your higher-level intentions and execute the necessary steps. This is the power unlocked by enabling terminal and workspace access:

• Automated Task Execution: Ask Copilot to install dependencies, run tests, lint your code, or even kick off a build process, all through natural language within your chat interface.
• Intelligent File Manipulation: Beyond simple code snippets, Copilot can refactor entire sections of your codebase, generate new files (e.g., for components or modules), or apply fixes across multiple files based on your instructions.
• Streamlined Workflow: Reduce context switching. Instead of manually navigating the terminal or opening numerous files, you can delegate these tasks to Copilot, keeping your focus on problem-solving.
• Enhanced Productivity: By automating repetitive or routine development tasks, Copilot frees up your time to concentrate on more complex logic and creative solutions.

The Key: Modifying Your VS Code settings.json

The gateway to these advanced Copilot capabilities lies within your VS Code settings.json file. This is the central configuration hub for your editor, where you can customize virtually every aspect of its behavior.

To access your settings.json file:

1. Open Visual Studio Code.
2. Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS) to open the Command Palette.
3. Type “Preferences: Open User Settings (JSON)” and select the corresponding option.

Once the settings.json file is open, you’ll need to locate or create the "github.copilot.advanced" section and add the "tools" property with editFile and terminalCommands set to true.

{
    // Other VS Code settings...

    "github.copilot.advanced": {
        "tools": {
            "editFile": true,
            "terminalCommands": true
        }
    }

    // More VS Code settings...
}

Let’s break down what each of these settings enables:

editFile: true

Setting "editFile": true empowers GitHub Copilot to directly modify and create files within your open VS Code workspace. This is a game-changer for tasks that span beyond single-line completions:

• Refactoring: Instruct Copilot to refactor a class or function, and it can intelligently apply changes across all affected files.
• Component Generation: Ask it to “create a new React component for a user profile,” and Copilot can scaffold the component file(s) with boilerplate code, including JSX, CSS modules, or even tests.
• Bug Fixing: If you describe a bug, Copilot can analyze the code, propose a fix, and then implement that fix by modifying the relevant files.

This capability moves Copilot beyond a suggestion engine to an active participant in your coding process, capable of making substantial, multi-file changes under your guidance.

terminalCommands: true

With "terminalCommands": true, GitHub Copilot gains the ability to execute commands in the integrated VS Code terminal. This means you can orchestrate development tasks directly through chat:

• Dependency Management: “Install lodash” or “Update all npm packages” can translate into Copilot running npm install lodash or npm update.
• Build and Test Automation: “Run the build script” or “Execute all unit tests” can trigger commands like npm run build or jest.
• Version Control Operations: While caution is advised, you could even ask Copilot to “commit all staged changes with message ‘Feature: Added new login form’,” which would execute git commit -m "Feature: Added new login form".

This dramatically streamlines your workflow, allowing you to stay focused on your code in the editor while Copilot manages command-line interactions in the background.

The Transformative Impact on Your Development Workflow

Once these settings are in place and your settings.json is saved, you’ll notice an immediate shift in how you interact with GitHub Copilot. Your conversations will become less about “how do I write this code” and more about “how do I accomplish this task.”

For example, a typical interaction could evolve from:

• Before: “Suggest code for a login form in React.” (Copilot provides code, you paste it and manually install dependencies).
• After: “Create a new login component with email and password fields, and install react-hook-form and firebase for authentication.” (Copilot creates the files, writes the component, and runs npm install).

This evolution empowers you to articulate your development intentions at a higher level, allowing Copilot to manage the granular details, saving you time and reducing mental overhead. It turns Copilot into a true collaborative agent, enhancing your efficiency and making your coding experience more fluid and intuitive. Embrace these advanced settings to unlock the full potential of your AI pair programmer.