How to Configure Windsurf SSH Approval

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up windsurf ssh approval by combining local agent permission prompts with server key rules. This stops the AI coding agent from running remote shell commands without a human check. Most teams start by turning on command confirmation inside the editor. They also load standard SSH keys into the local agent on the developer machine. If those keys grant broad root or admin rights, a single click can cause big problems. How windsurf ssh approval works in the editor On June 2, 2026, Cogniti

Approval Chains & Escalation + SSH Access Management: the complete guide

Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.

Free white paper. No spam. Unsubscribe anytime.

You set up windsurf ssh approval by combining local agent permission prompts with server key rules. This stops the AI coding agent from running remote shell commands without a human check. Most teams start by turning on command confirmation inside the editor. They also load standard SSH keys into the local agent on the developer machine. If those keys grant broad root or admin rights, a single click can cause big problems.

How windsurf ssh approval works in the editor

On June 2, 2026, Cognition renamed Windsurf to Devin Desktop. The editor keeps the same features and uses the Cascade agent to run tasks. The agent can run terminal commands on its own when the user gives permission. It opens a dedicated shell that uses zsh on macOS or bash on Linux. Because this shell loads the user profile, all local aliases and variables are ready to use.

When the agent needs to reach a remote host, it writes a standard SSH command. The editor pauses and asks the developer to review the command string before it runs. Once the developer clicks approve, the local shell uses the active SSH keys on that laptop. Teams often pair this local prompt with OpenSSH user certificates on the remote servers. A certificate authority key signs a user public key and sets allowed user or host names. OpenSSH added this certificate method in version 5.4 to offer a simpler format than X.509.

What local prompts solve and what they miss

Local editor prompts stop the agent from starting an unexpected remote session in the background. OpenSSH certificates also help by proving who the user is without scattering static public keys everywhere. Together, these steps control how the developer and the agent first log in to a host.

Still, this native setup leaves a major gap once the session starts. Local windsurf ssh approval only checks the initial shell command on the developer laptop. If the agent opens a remote script or forwards a port, the editor cannot inspect inside. Also, developers suffer from prompt fatigue when they approve dozens of terminal tasks every hour. A tired user might approve a destructive remote command by mistake. Also, standard SSH logs on the server only show that the user logged in. They do not record the exact commands the AI agent ran or the data it read. If remote output contains emails, phone numbers, card numbers, or national IDs, raw text returns directly. The local shell cannot mask those fields in results before the model reads the screen.

Approval Chains & Escalation + SSH Access Management: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Why team review matters for remote agent commands

Self-approval on a laptop is not enough for production servers. When an AI agent touches live hosts, a second person should review the request. Relying on local shell profiles means every developer laptop holds live keys at rest. If an agent reads a local file or variable, it can use those credentials right away. Moving approval and key handling off the developer machine keeps production hosts safe from bad prompts.

Add command and file guardrails to SSH access

Host firewalls and certificate principals control who opens an SSH session. Yet an allowed user or agent can still run a bad one-shot command or pull sensitive files over sftp. In practice, hoop.dev sits inline on the host as an open-source SSH server with guardrails that uses OpenSSH certificates. For every one-shot command or sftp task an agent or human runs in production, hoop.dev decides to pass, mask, block, or escalate it for review.

Using hoop.dev SSH controls, guardrails check one-shot commands, env variable names, and sftp or scp paths before they run. Port forwards default to deny unless the target is listed. Because interactive shells have no statement boundary and carry no guardrails, teams can turn them off so every command is checked and logged. Check out the MIT-licensed project on GitHub.

Frequently asked questions

Is Windsurf still the same tool as Devin Desktop?

Yes, Cognition renamed Windsurf to Devin Desktop on June 2, 2026. It keeps the same editor features and the Cascade agent for running terminal commands.

Does the Windsurf terminal use my existing SSH keys?

Yes, the agent runs in a dedicated zsh or bash shell that loads your profile. Any SSH keys or environment variables in your shell are open to the agent after approval.

Can OpenSSH certificates restrict what the agent does after login?

OpenSSH certificates verify user and host identities during login and can set basic session options. They do not inspect interactive commands in flight or mask sensitive fields like emails in output.

Save the open-source gateway.

hoop is MIT-licensed infrastructure for controlling how AI agents reach production data. Star hoophq/hoop so you can inspect it, deploy it, or share it when your team starts governing agent access.