Agent mode in VS Code
ConnectionGitHub Copilot to Cloud Noce
Connects Copilot agent mode to Cloud Noce through VS Code's MCP configuration file. MCP retrieves current service information from Cloud Noce, so the agent can respond based on the actual state of your service.
$ gerdoo setup agent --agent copilot
→ Wired gerdoo MCP into .vscode/mcp.json
→ Installed use-gerdoo skill
✓ Ready to deploy.
Connect in three commands
Install the Gerdoo CLI and sign in first. The third command adds the MCP configuration and Gerdoo usage guide to your project.
Install the Gerdoo CLI
curl -fsSL https://get.gerdoo.cloud/install.sh | shSign in to your Gerdoo account
gerdoo loginSet up the GitHub Copilot connection
gerdoo setup agent --agent copilotThe third command saves the Cloud Noce connection in .vscode/mcp.json . IfGitHub Copilot is open, restart it after setup.
Describe the outcome, not the tool
You do not need to know an API or MCP tool name. Clearly state the project and target environment. For production changes, ask the agent to explain its plan before running it.
«Deploy this application to Cloud Noce and give me its public URL when it's ready.»
«Find the required variables in the sample file. Identify secrets and ask my permission before saving them.»
Access comes from your Gerdoo CLI session
GitHub Copilot No separate token is needed. Secret values are not displayed in tool responses. For destructive actions, the agent must identify the resource and target environment and obtain your explicit approval.