Using Amazon Q Developer? Noxgild can move with your workflow.
Keep legacy Amazon Q Developer workflows understandable while AWS transitions agentic development toward Kiro.
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 Amazon Q 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.
Connect Noxgild to Amazon Q
- 1For a new AWS agent workflow, install Kiro and follow the Kiro setup guide.
- 2If you already use an Amazon Q path that supports remote MCP, add https://mcp.noxgild.com/mcp.
- 3Complete the provider-supported Noxgild authorization path.
- 4Send the verification prompt and confirm a protected Noxgild tool call succeeds.
VERIFICATION PROMPT
Show my Noxgild computers and verify my current development environment.
BEFORE YOU START
- Amazon Q Developer is presented as a transition path, not a newly certified primary client.
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.
Inspect my development environment and verify the current deployment.
Having trouble?
- Provider product availability can change; use the Kiro guide for the current AWS agent workflow when possible.
High-impact actions can require exact approval. CAPTCHA, OTP, passkeys, UAC, and other protected verification remain human-controlled.