Visual Studio Code logoGitHub Copilot logo

Noxgild setup guide

Connect VS Code + GitHub Copilot to Noxgild

Give GitHub Copilot access to the environment around the repo: the computer, long-running processes, signed-in browser, and native apps.

Visual Studio Code logoGitHub Copilot logoVS Code + GitHub CopilotNoxgild Files Terminal Browser Desktop

Before you start

  • • VS Code with GitHub Copilot and MCP support.

Manage your computers and account in the Noxgild dashboard.

Follow the setup

Already signed in to VS Code and GitHub Copilot? Open the Command Palette setup at Step 2: Open VS Code's MCP setup .

5 steps
  1. Install VS Code and sign in to Copilot

    • Download and open Visual Studio Code, then sign in to the GitHub account that has Copilot access.
    • Open the project you want Copilot to work with, and select Agent mode in Copilot Chat.
    Download VS Code
  2. Open VS Code's MCP setup

    • Press Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS.
    • Run the exact Command Palette action “MCP: Add Server” and choose HTTP (Streamable HTTP) as the server type.
    • If asked where to save it, choose User Configuration for all projects or Workspace Configuration for only this project.
  3. Enter and enable the Noxgild server

    • Paste this URL when asked for the remote HTTP endpoint; name the server noxgild.
    • Review the trust prompt, then enable/start noxgild from the MCP Servers list if necessary.
    • User config is in your VS Code profile; workspace config is .vscode/mcp.json.
    https://mcp.noxgild.com/mcp
  4. Authorize Noxgild

    • When VS Code prompts you to sign in, open the browser authorization and approve Noxgild.
    • Return to VS Code; make sure the server and tools are enabled in Copilot Chat's tool picker.
  5. Test Noxgild in Copilot Chat

    • In Copilot Chat, keep Agent mode selected and allow the Noxgild tool call.
    • A successful test lists your authorized computer and its current status. ONLINE means the device is available; an authorized connection alone is not a test.
    Use the connected Noxgild MCP server only. Call noxgild_devices and list my available computers and their current status.

What success looks like

Your AI should return your authorized Noxgild computer and its status. An ONLINE computer is ready for authorized tasks. Authorization alone does not verify tool access.

Troubleshooting & additional guidance

Sign in to Noxgild when the client's authorization step opens, and return to the client.

  • • If Noxgild tools do not appear, reload the VS Code window and check that the noxgild MCP server is enabled.
  • • If authorization looks stale, reconnect the Noxgild server from VS Code and authorize again.
Visual Studio Code logoGitHub Copilot logoWhat Noxgild adds

Your VS Code + GitHub Copilot workflow. The real environment.

Keep what VS Code + GitHub Copilot already does. Noxgild extends it to the computer, browser and desktop tools where the outcome must be verified.

NoxgildAuthorized layer

Explore the capabilities

Real computer

Work on an explicitly selected Windows, macOS, or Linux computer, beyond the client's own workspace.

Scoped access · Exact device · Human approvals

Real work. Real results.

See what Noxgild helps you achieve with VS Code + GitHub Copilot

Practical outcomes using Noxgild's authorized execution layer.

01

Do the work

Run this branch on my QA computer and verify the fix in the signed-in browser.

02

Check the result

Start the development server, keep it running, and inspect its output while I continue coding.

03

Finish the job

Open the native desktop build and verify the UI change.

Built for people who finish the work

DevelopersDevOpsIT supportQAAI automationPlatform teams

Ready to connect VS Code + Copilot to your actual environment?