Do the work
Run this branch on my QA computer and verify the fix in the signed-in browser.
Noxgild setup guide
Give GitHub Copilot access to the environment around the repo: the computer, long-running processes, signed-in browser, and native apps.
Before you start
Manage your computers and account in the Noxgild dashboard.
Already signed in to VS Code and GitHub Copilot? Open the Command Palette setup at Step 2: Open VS Code's MCP setup .
https://mcp.noxgild.com/mcpUse the connected Noxgild MCP server only. Call noxgild_devices and list my available computers and their current status.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.
Sign in to Noxgild when the client's authorization step opens, and return to the client.
Keep what VS Code + GitHub Copilot already does. Noxgild extends it to the computer, browser and desktop tools where the outcome must be verified.
Explore the capabilities
Work on an explicitly selected Windows, macOS, or Linux computer, beyond the client's own workspace.
Real work. Real results.
Practical outcomes using Noxgild's authorized execution layer.
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.
Built for people who finish the work