Give GitHub Copilot a whole computer, not just a codebase.
Give GitHub Copilot access to the environment around the repo: the computer, long-running processes, signed-in browser, and native apps.
Your AI can leave the chat or repo and finish the job.
Noxgild adds controlled access to files, persistent terminal processes, a signed-in browser, native desktop applications, and a separate hosted Cloud Browser. The same authorized computer can be reused from other supported AI clients.
Files and terminal
Read, edit, build, test, and keep long-running work alive.
Signed-in browser
Use the authenticated session that matters for real verification.
desktop applications
Operate native software when browser and terminal are not enough.
Cloud Browser
Run browser work in a hosted session when the workstation is not the right environment.
CONNECTION STANDARD
After authorization, run the verification prompt. When your authorized computer appears, you are ready to use Noxgild.
START FREE
Connect VS Code + Copilot to a real Noxgild computer.
Free includes 10,000 normal tool calls per 30-day cycle. Upgrade only when you need higher-volume use or Cloud Browser.
SETUP
Start with the client, then connect Noxgild.
New here? Install the client first. Already have it? Skip straight to the Noxgild connection step.
FOLLOW THIS TUTORIAL
Connect VS Code + GitHub Copilot to Noxgild
Start at step 1 if you are new. If the client is already installed and signed in, jump to the step where you add Noxgild.
Download VS Code
- • Open the official VS Code download page.
- • Download and install VS Code for your operating system.
- • Open VS Code when installation finishes.
Sign in to GitHub Copilot
- • Open VS Code.
- • Sign in to GitHub and make sure GitHub Copilot is available in the account you want to use.
- • Open the project you want Copilot to work with.
Open the MCP server setup
- • Press Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS.
- • Type MCP: Add Server.
- • Choose the MCP: Add Server command.
Add Noxgild
- • Choose HTTP when VS Code asks for the server type.
- • Paste the Noxgild MCP URL.
- • When VS Code asks for a server name, enter noxgild.
https://mcp.noxgild.com/mcpAuthorize Noxgild
- • VS Code opens the Noxgild sign-in/authorization page in your browser.
- • Sign in to Noxgild and approve the connection.
- • Return to VS Code and make sure the noxgild MCP server is enabled.
Verify the connection
- • Open Copilot Chat.
- • Paste the verification prompt below and send it.
- • Do not use another computer-access tool for this test.
Use the connected Noxgild MCP server only. Call noxgild_devices and list my available computers and their current status.Confirm success
- • Setup is complete when Copilot returns your authorized Noxgild computer and shows it as ONLINE.
- • You can now ask Copilot to use Noxgild for files, terminal processes, browser work, and desktop applications.
What success looks like
Your AI returns the authorized Noxgild computer and its current status. If the computer is ONLINE, the connection is ready for real work.
VERIFICATION PROMPT
Use the connected Noxgild MCP server only. Call noxgild_devices and list my available computers and their current status.
BEFORE YOU START
- VS Code with GitHub Copilot and MCP support.
Finished the setup steps?
Open Connect AI, verify your computer appears, then run the first-task prompt from the guide.
GOOD FIRST TASKS
Ask for an outcome, not a tool demo.
Run this branch on my QA computer and verify the fix in the signed-in browser.
Start the development server, keep it running, and inspect its output while I continue coding.
Open the native desktop build and verify the UI change.
Having trouble?
- 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.
High-impact actions can require exact approval. CAPTCHA, OTP, passkeys, UAC, and other protected verification remain human-controlled.